Reflected cross-site scripting vulnerabilities arise when data is copied from a request and echoed into the application's immediate response in an unsafe way. An attacker can use the vulnerability to construct a request which, if issued by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application.
The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes.
Users can be induced to issue the attacker's crafted request in various ways. For example, the attacker can send a victim a link containing a malicious URL in an email or instant message. They can submit the link to popular web sites that allow content authoring, for example in blog comments. And they can create an innocuous looking web site which causes anyone viewing it to make arbitrary cross-domain requests to the vulnerable application (using either the GET or the POST method).
The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality which it contains, and the other applications which belong to the same domain and organisation. If the application is used only to display non-sensitive public content, with no authentication or access control functionality, then a cross-site scripting flaw may be considered low risk. However, if the same application resides on a domain which can access cookies for other more security-critical applications, then the vulnerability could be used to attack those other applications, and so may be considered high risk. Similarly, if the organisation which owns the application is a likely target for phishing attacks, then the vulnerability could be leveraged to lend credibility to such attacks, by injecting Trojan functionality into the vulnerable application, and exploiting users' trust in the organisation in order to capture credentials for other applications which it owns. In many kinds of application, such as those providing online banking functionality, cross-site scripting should always be considered high risk.
Remediation background
In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of defences:
Input should be validated as strictly as possible on arrival, given the kind of content which it is expected to contain. For example, personal names should consist of alphabetical and a small range of typographical characters, and be relatively short; a year of birth should consist of exactly four numerals; email addresses should match a well-defined regular expression. Input which fails the validation should be rejected, not sanitised.
User input should be HTML-encoded at any point where it is copied into application responses. All HTML metacharacters, including < > " ' and =, should be replaced with the corresponding HTML entities (< > etc).
In cases where the application's functionality allows users to author content using a restricted subset of HTML tags and attributes (for example, blog comments which allow limited formatting and linking), it is necessary to parse the supplied HTML to validate that it does not use any dangerous syntax; this is a non-trivial task.
The value of the source request parameter is copied into the HTML document as plain text between tags. The payload %00d8321<script>alert(1)</script>d3a2c64e822 was submitted in the source parameter. This input was echoed as d8321<script>alert(1)</script>d3a2c64e822 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.
Remediation detail
NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.
The value of the source request parameter is copied into the value of an HTML tag attribute which is not encapsulated in any quotation marks. The payload 5c90e><script>alert(1)</script>d2d6d807fd7c85b07 was submitted in the source parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.
The value of the source request parameter is copied into the value of an HTML tag attribute which is not encapsulated in any quotation marks. The payload 67765><script>alert(1)</script>c64b17441a6 was submitted in the source parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /cell-phone-service/go-phones/index.jsp?wtSlotClick=1-005Y6F-0-3&bfdcode=ATT&source=EC4425000000004067765><script>alert(1)</script>c64b17441a6 HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The value of the B2CSESSIONID cookie is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 99453'-alert(1)-'45e716f72c6 was submitted in the B2CSESSIONID cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Sensitive information within URLs may be logged in various locations, including the user's browser, the web server, and any forward or reverse proxy servers between the two endpoints. URLs may also be displayed on-screen, bookmarked or emailed around by users. They may be disclosed to third parties via the Referer header when any off-site links are followed. Placing session tokens into the URL increases the risk that they will be captured by an attacker.
Issue remediation
The application should use an alternative mechanism for transmitting session tokens, such as HTTP cookies or hidden fields in forms that are submitted using the POST method.
GET /cell-phone-service/accessories/index.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
GET /cell-phone-service/cell-phone-plans/data-connect-plans.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
GET /cell-phone-service/cell-phone-plans/family-cell-phone-plans.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
GET /cell-phone-service/cell-phone-plans/index.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
GET /cell-phone-service/cell-phone-plans/individual-cell-phone-plans.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
GET /cell-phone-service/cell-phones/ HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
GET /cell-phone-service/cell-phones/cell-phones.jsp?wtSlotClick=1-005Y6F-0-1&feacondition=allphones&feaavailable=allphones&feafree=free&feapaytype=standard&startFilter=false&allTypes=on&allManus=on HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
GET /cell-phone-service/cell-phones/index.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
GET /cell-phone-service/cell-phones/pda-phones-smartphones.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
GET /cell-phone-service/go-phones/index.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
GET /cell-phone-service/packages/index.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
GET /cell-phone-service/services/index.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
GET /cell-phone-service/transfer-your-number/ HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The application publishes a Flash cross-domain policy which uses a wildcard to specify allowed domains, and allows access from specific other domains.
Using a wildcard to specify allowed domains means that any domain matching the wildcard expression can perform two-way interaction with this application. You should only use this policy if you fully trust every possible web site that may reside on a domain which matches the wildcard expression.
Allowing access from specific domains means that web sites on those domains can perform two-way interaction with this application. You should only use this policy if you fully trust the specific domains allowed by the policy.
Issue background
The Flash cross-domain policy controls whether Flash client components running on other domains can perform two-way interaction with the domain which publishes the policy. If another domain is allowed by the policy, then that domain can potentially attack users of the application. If a user is logged in to the application, and visits a domain allowed by the policy, then any malicious content running on that domain can potentially gain full access to the application within the security context of the logged in user.
Even if an allowed domain is not overtly malicious in itself, security vulnerabilities within that domain could potentially be leveraged by a third-party attacker to exploit the trust relationship and attack the application which allows access.
Issue remediation
You should review the domains which are allowed by the Flash cross-domain policy and determine whether it is appropriate for the application to fully trust both the intentions and security posture of those domains.
Request
GET /crossdomain.xml HTTP/1.0 Host: www.wireless.att.com
Response
HTTP/1.0 200 OK Server: Apache Last-Modified: Tue, 05 Oct 2010 20:19:38 GMT ETag: "19b-491e4614f4a80" Accept-Ranges: bytes Content-Length: 411 Content-Type: application/xml Date: Tue, 06 Sep 2011 11:04:22 GMT Connection: close
A cookie's domain attribute determines which domains can access the cookie. Browsers will automatically submit the cookie in requests to in-scope domains, and those domains will also be able to access the cookie via JavaScript. If a cookie is scoped to a parent domain, then that cookie will be accessible by the parent domain and also by any other subdomains of the parent domain. If the cookie contains sensitive data (such as a session token) then this data may be accessible by less trusted or less secure applications residing at those domains, leading to a security compromise.
Issue remediation
By default, cookies are scoped to the issuing domain and all subdomains. If you remove the explicit domain attribute from your Set-cookie directive, then the cookie will have this default scope, which is safe and appropriate in most situations. If you particularly need a cookie to be accessible by a parent domain, then you should thoroughly review the security of the applications residing on that domain and its subdomains, and confirm that you are willing to trust the people and systems which support those applications.
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /cell-phone-service/accessories/index.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /cell-phone-service/cell-phone-plans/data-connect-plans.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /cell-phone-service/cell-phone-plans/family-cell-phone-plans.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /cell-phone-service/cell-phone-plans/index.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /cell-phone-service/cell-phone-plans/individual-cell-phone-plans.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /cell-phone-service/cell-phone-plans/pyg-cell-phone-plans.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /cell-phone-service/cell-phones/ HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /cell-phone-service/cell-phones/cell-phones.jsp?wtSlotClick=1-005Y6F-0-1&feacondition=allphones&feaavailable=allphones&feafree=free&feapaytype=standard&startFilter=false&allTypes=on&allManus=on HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /cell-phone-service/cell-phones/index.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /cell-phone-service/cell-phones/pda-phones-smartphones.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /cell-phone-service/go-phones/index.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /cell-phone-service/packages/index.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /cell-phone-service/ringtones_media/index.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /cell-phone-service/services/index.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /cell-phone-service/specials/netbooks.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /cell-phone-service/transfer-your-number/ HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /coverageviewer/ HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>301 Moved Permanently</title> </head><body> <h1>Moved Permanently</h1> <p>The document has moved <a href="http://www.att.com/stor ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /learn/international/ HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Server: Apache P3P: policyref=""/w3c/p3p.xml"", CP="CAO DSP COR LAW CURa ADMa DEVa TAIa PSAa PSDa OUR DELa BUS IND PHY ONL UNI PUR COM NAV DEM STA GOV" X-Powered-By: Servlet/2.5 JSP/2.1 Content-Type: text/html; charset=UTF-8 Expires: Tue, 06 Sep 2011 11:06:20 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Date: Tue, 06 Sep 2011 11:06:20 GMT Connection: close Connection: Transfer-Encoding Set-Cookie: TLTHID=3FD1F714D87810D8547984A4C33E7EED; Path=/; Domain=.att.com Set-Cookie: ECOM_GTM=owbth_NA_NA_NA_ostdbth; domain=.att.com; expires=Wednesday, 05-Sep-2012 11:06:20 GMT; path=/ Content-Length: 61536
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en"> <head> <title>International calling rates and packages - ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /learn/ringtones-downloads/myatt-mobile.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Server: Apache P3P: policyref=""/w3c/p3p.xml"", CP="CAO DSP COR LAW CURa ADMa DEVa TAIa PSAa PSDa OUR DELa BUS IND PHY ONL UNI PUR COM NAV DEM STA GOV" X-Powered-By: Servlet/2.5 JSP/2.1 Content-Type: text/html; charset=UTF-8 Expires: Tue, 06 Sep 2011 11:06:20 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Date: Tue, 06 Sep 2011 11:06:20 GMT Connection: close Connection: Transfer-Encoding Set-Cookie: TLTHID=3FF116BCD87810D85528BCD4C2B001A1; Path=/; Domain=.att.com Set-Cookie: ECOM_GTM=owbth_NA_NA_NA_ostdbth; domain=.att.com; expires=Wednesday, 05-Sep-2012 11:06:20 GMT; path=/ Content-Length: 54761
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en"> <head> <title>Account Management App - myAT&T Mobile - W ...[SNIP]...
5. Cross-domain Referer leakagepreviousnext There are 6 instances of this issue:
When a web browser makes a request for a resource, it typically adds an HTTP header, called the "Referer" header, indicating the URL of the resource from which the request originated. This occurs in numerous situations, for example when a web page loads an image or script, or when a user clicks on a link or submits a form.
If the resource being requested resides on a different domain, then the Referer header is still generally included in the cross-domain request. If the originating URL contains any sensitive information within its query string, such as a session token, then this information will be transmitted to the other domain. If the other domain is not fully trusted by the application, then this may lead to a security compromise.
You should review the contents of the information being transmitted to other domains, and also determine whether those domains are fully trusted by the originating application.
Today's browsers may withhold the Referer header in some situations (for example, when loading a non-HTTPS resource from a page that was loaded over HTTPS, or when a Refresh directive is issued), but this behaviour should not be relied upon to protect the originating URL from disclosure.
Note also that if users can author content within the application then an attacker may be able to inject links referring to a domain they control in order to capture data from URLs used within the application.
Issue remediation
The application should never transmit any sensitive information within the URL query string. In addition to being leaked in the Referer header, such information may be logged in various locations and may be visible on-screen to untrusted parties.
GET /cell-phone-service/cell-phones/cell-phones.jsp?wtSlotClick=1-005Y6F-0-1&feacondition=allphones&feaavailable=allphones&feafree=free&feapaytype=standard&startFilter=false&allTypes=on&allManus=on HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<a target="_blank" href="http://www.ctia.org/"><img title="The first nationwide carrier to be awarded the Seal of Wireless Quality. For details, visit www.ctia.org." alt="The first nationwide carrier to be awarded the Seal of Wireless Quality. For ...[SNIP]... </a>
<a target="_blank" href="https://www.bbb.org/online/consumer/cks.aspx?id=110020911221"><img title="Click to verify BBB accreditation and to see a BBB report." alt="Click to verify BBB accreditation and to see a BBB report." src="//www.att.com/media/att/2011/global/nav/en_US/logoBBB.png"></a>
<a target="_blank" href="http://clicktoverify.truste.com/pvr.php?page=validate&companyName=AT%26T&sealid=101"><img title="This site is certified by TRUSTe" alt="This site is certified by TRUSTe" src="//www.att.com/media/att/2011/global/nav/en_US/logoTRUSTe.png"></a>
GET /cell-phone-service/cell-phones/index.jsp?wtSlotClick=1-005Y6F-0-5 HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<a target="_blank" href="http://www.ctia.org/"><img title="The first nationwide carrier to be awarded the Seal of Wireless Quality. For details, visit www.ctia.org." alt="The first nationwide carrier to be awarded the Seal of Wireless Quality. For ...[SNIP]... </a>
<a target="_blank" href="https://www.bbb.org/online/consumer/cks.aspx?id=110020911221"><img title="Click to verify BBB accreditation and to see a BBB report." alt="Click to verify BBB accreditation and to see a BBB report." src="//www.att.com/media/att/2011/global/nav/en_US/logoBBB.png"></a>
<a target="_blank" href="http://clicktoverify.truste.com/pvr.php?page=validate&companyName=AT%26T&sealid=101"><img title="This site is certified by TRUSTe" alt="This site is certified by TRUSTe" src="//www.att.com/media/att/2011/global/nav/en_US/logoTRUSTe.png"></a>
<a target="_blank" href="http://www.realpageslive.com/"><img title="Digital White and Yellow Pages" alt="Digital White and Yellow Pages" src="//www.att.com/media/att/2011/global/nav/en_US/logoDigitalWhiteYellowPages.png"> ...[SNIP]... </script>
GET /cell-phone-service/cell-phones/pda-phones-smartphones.jsp?wtSlotClick=1-005Y6F-0-2 HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<a target="_blank" href="http://www.ctia.org/"><img title="The first nationwide carrier to be awarded the Seal of Wireless Quality. For details, visit www.ctia.org." alt="The first nationwide carrier to be awarded the Seal of Wireless Quality. For ...[SNIP]... </a>
<a target="_blank" href="https://www.bbb.org/online/consumer/cks.aspx?id=110020911221"><img title="Click to verify BBB accreditation and to see a BBB report." alt="Click to verify BBB accreditation and to see a BBB report." src="//www.att.com/media/att/2011/global/nav/en_US/logoBBB.png"></a>
<a target="_blank" href="http://clicktoverify.truste.com/pvr.php?page=validate&companyName=AT%26T&sealid=101"><img title="This site is certified by TRUSTe" alt="This site is certified by TRUSTe" src="//www.att.com/media/att/2011/global/nav/en_US/logoTRUSTe.png"></a>
GET /cell-phone-service/go-phones/index.jsp?wtSlotClick=1-005Y6F-0-3&bfdcode=ATT&source=EC44250000000040 HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<script type="text/javascript" src="https://sales.liveperson.net/hcp/html/DynamicButtonScript2.js"></script> ...[SNIP]... <p style="margin-top:0px;"><a href="https://www.myprepaidrefill.com/ATT/default.aspx?wtSlotClick=1-0014FG-0-1&WT.svl=calltoaction" onclick="" rel="nofollow"><img src="/global/images/btn_arrow_box_white.gif" style="vertical-align:text-top;margin-right:3px;" /></a><a href="https://www.myprepaidrefill.com/ATT/default.aspx?wtSlotClick=1-0014FG-0-1&WT.svl=calltoaction" onclick="" rel="nofollow">Add minutes now</a> ...[SNIP]... <li class="arrow-icon"><a href="https://www.selfincharge.com/webhsc/index.jsp?wtSlotClick=1-0050TO-0-1&WT.svl=calltoaction" onclick=" ; javascript:dotComPopUp(this.href,800,600);return false;">Pick Your Plan Log in</a> ...[SNIP]... <li class="arrow-icon"><a href="https://www.paygonline.com/websc/index.jsp?wtSlotClick=1-0050TO-0-2&WT.svl=calltoaction" onclick=" ; javascript:dotComPopUp(this.href,800,600);return false;">Pay As You Go Log in</a> ...[SNIP]... <div class="logoBlock">
<a target="_blank" href="http://www.ctia.org/"><img title="The first nationwide carrier to be awarded the Seal of Wireless Quality. For details, visit www.ctia.org." alt="The first nationwide carrier to be awarded the Seal of Wireless Quality. For ...[SNIP]... </a>
<a target="_blank" href="https://www.bbb.org/online/consumer/cks.aspx?id=110020911221"><img title="Click to verify BBB accreditation and to see a BBB report." alt="Click to verify BBB accreditation and to see a BBB report." src="//www.att.com/media/att/2011/global/nav/en_US/logoBBB.png"></a>
<a target="_blank" href="http://clicktoverify.truste.com/pvr.php?page=validate&companyName=AT%26T&sealid=101"><img title="This site is certified by TRUSTe" alt="This site is certified by TRUSTe" src="//www.att.com/media/att/2011/global/nav/en_US/logoTRUSTe.png"></a>
GET /cell-phone-service/specials/netbooks.jsp?wtSlotClick=1-005Y6F-0-4 HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<a target="_blank" href="http://www.ctia.org/"><img title="The first nationwide carrier to be awarded the Seal of Wireless Quality. For details, visit www.ctia.org." alt="The first nationwide carrier to be awarded the Seal of Wireless Quality. For ...[SNIP]... </a>
<a target="_blank" href="https://www.bbb.org/online/consumer/cks.aspx?id=110020911221"><img title="Click to verify BBB accreditation and to see a BBB report." alt="Click to verify BBB accreditation and to see a BBB report." src="//www.att.com/media/att/2011/global/nav/en_US/logoBBB.png"></a>
<a target="_blank" href="http://clicktoverify.truste.com/pvr.php?page=validate&companyName=AT%26T&sealid=101"><img title="This site is certified by TRUSTe" alt="This site is certified by TRUSTe" src="//www.att.com/media/att/2011/global/nav/en_US/logoTRUSTe.png"></a>
<a target="_blank" href="http://www.realpageslive.com/"><img title="Digital White and Yellow Pages" alt="Digital White and Yellow Pages" src="//www.att.com/media/att/2011/global/nav/en_US/logoDigitalWhiteYellowPages.png"> ...[SNIP]...
GET /coverageviewer/?type=voice HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
When an application includes a script from an external domain, this script is executed by the browser within the security context of the invoking application. The script can therefore do anything that the application's own scripts can do, such as accessing application data and performing actions within the context of the current user.
If you include a script from an external domain, then you are trusting that domain with the data and functionality of your application, and you are trusting the domain's own security to prevent an attacker from modifying the script to perform malicious actions within your application.
Issue remediation
Scripts should not be included from untrusted domains. If you have a requirement which a third-party script appears to fulfil, then you should ideally copy the contents of that script onto your own domain and include it from there. If that is not possible (e.g. for licensing reasons) then you should consider reimplementing the script's functionality within your own code.
GET /cell-phone-service/accessories/index.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
GET /cell-phone-service/cell-phone-plans/data-connect-plans.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
GET /cell-phone-service/cell-phone-plans/family-cell-phone-plans.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
GET /cell-phone-service/cell-phone-plans/index.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
GET /cell-phone-service/cell-phone-plans/individual-cell-phone-plans.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
GET /cell-phone-service/cell-phones/ HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
GET /cell-phone-service/cell-phones/cell-phones.jsp?wtSlotClick=1-005Y6F-0-1&feacondition=allphones&feaavailable=allphones&feafree=free&feapaytype=standard&startFilter=false&allTypes=on&allManus=on HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
GET /cell-phone-service/cell-phones/index.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
GET /cell-phone-service/cell-phones/pda-phones-smartphones.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
GET /cell-phone-service/go-phones/index.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
GET /cell-phone-service/packages/index.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
GET /cell-phone-service/services/index.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
GET /cell-phone-service/specials/netbooks.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
GET /cell-phone-service/transfer-your-number/ HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
GET /coverageviewer/ HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The response dynamically includes the following script from another domain:
http://static.meteorsolutions.com/metsol.js
Request
GET /learn/ringtones-downloads/myatt-mobile.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Server: Apache P3P: policyref=""/w3c/p3p.xml"", CP="CAO DSP COR LAW CURa ADMa DEVa TAIa PSAa PSDa OUR DELa BUS IND PHY ONL UNI PUR COM NAV DEM STA GOV" X-Powered-By: Servlet/2.5 JSP/2.1 Content-Type: text/html; charset=UTF-8 Expires: Tue, 06 Sep 2011 11:06:20 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Date: Tue, 06 Sep 2011 11:06:20 GMT Connection: close Connection: Transfer-Encoding Set-Cookie: TLTHID=3FF116BCD87810D85528BCD4C2B001A1; Path=/; Domain=.att.com Set-Cookie: ECOM_GTM=owbth_NA_NA_NA_ostdbth; domain=.att.com; expires=Wednesday, 05-Sep-2012 11:06:20 GMT; path=/ Content-Length: 54761
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en"> <head> <title>Account Management App - myAT&T Mobile - W ...[SNIP]... </script>
If the HttpOnly attribute is set on a cookie, then the cookie's value cannot be read or set by client-side JavaScript. This measure can prevent certain client-side attacks, such as cross-site scripting, from trivially capturing the cookie's value via an injected script.
Issue remediation
There is usually no good reason not to set the HttpOnly flag on all cookies. Unless you specifically require legitimate client-side scripts within your application to read or set a cookie's value, you should set the HttpOnly flag by including this attribute within the relevant Set-cookie directive.
You should be aware that the restrictions imposed by the HttpOnly flag can potentially be circumvented in some circumstances, and that numerous other serious attacks can be delivered by client-side script injection, aside from simple cookie stealing.
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /cell-phone-service/accessories/index.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /cell-phone-service/cell-phone-plans/data-connect-plans.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /cell-phone-service/cell-phone-plans/family-cell-phone-plans.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /cell-phone-service/cell-phone-plans/index.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /cell-phone-service/cell-phone-plans/individual-cell-phone-plans.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /cell-phone-service/cell-phone-plans/pyg-cell-phone-plans.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /cell-phone-service/cell-phones/ HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /cell-phone-service/cell-phones/cell-phones.jsp?wtSlotClick=1-005Y6F-0-1&feacondition=allphones&feaavailable=allphones&feafree=free&feapaytype=standard&startFilter=false&allTypes=on&allManus=on HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /cell-phone-service/cell-phones/index.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /cell-phone-service/cell-phones/pda-phones-smartphones.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /cell-phone-service/go-phones/index.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /cell-phone-service/packages/index.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /cell-phone-service/ringtones_media/index.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /cell-phone-service/services/index.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /cell-phone-service/specials/netbooks.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /cell-phone-service/transfer-your-number/ HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /coverageviewer/ HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>301 Moved Permanently</title> </head><body> <h1>Moved Permanently</h1> <p>The document has moved <a href="http://www.att.com/stor ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /learn/international/ HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Server: Apache P3P: policyref=""/w3c/p3p.xml"", CP="CAO DSP COR LAW CURa ADMa DEVa TAIa PSAa PSDa OUR DELa BUS IND PHY ONL UNI PUR COM NAV DEM STA GOV" X-Powered-By: Servlet/2.5 JSP/2.1 Content-Type: text/html; charset=UTF-8 Expires: Tue, 06 Sep 2011 11:06:20 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Date: Tue, 06 Sep 2011 11:06:20 GMT Connection: close Connection: Transfer-Encoding Set-Cookie: TLTHID=3FD1F714D87810D8547984A4C33E7EED; Path=/; Domain=.att.com Set-Cookie: ECOM_GTM=owbth_NA_NA_NA_ostdbth; domain=.att.com; expires=Wednesday, 05-Sep-2012 11:06:20 GMT; path=/ Content-Length: 61536
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en"> <head> <title>International calling rates and packages - ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /learn/ringtones-downloads/myatt-mobile.jsp HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Server: Apache P3P: policyref=""/w3c/p3p.xml"", CP="CAO DSP COR LAW CURa ADMa DEVa TAIa PSAa PSDa OUR DELa BUS IND PHY ONL UNI PUR COM NAV DEM STA GOV" X-Powered-By: Servlet/2.5 JSP/2.1 Content-Type: text/html; charset=UTF-8 Expires: Tue, 06 Sep 2011 11:06:20 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Date: Tue, 06 Sep 2011 11:06:20 GMT Connection: close Connection: Transfer-Encoding Set-Cookie: TLTHID=3FF116BCD87810D85528BCD4C2B001A1; Path=/; Domain=.att.com Set-Cookie: ECOM_GTM=owbth_NA_NA_NA_ostdbth; domain=.att.com; expires=Wednesday, 05-Sep-2012 11:06:20 GMT; path=/ Content-Length: 54761
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en"> <head> <title>Account Management App - myAT&T Mobile - W ...[SNIP]...
The following email address was disclosed in the response:
carl@criticalmass.com
Issue background
The presence of email addresses within application responses does not necessarily constitute a security vulnerability. Email addresses may appear intentionally within contact information, and many applications (such as web mail) include arbitrary third-party email addresses within their core content.
However, email addresses of developers and other individuals (whether appearing on-screen or hidden within page source) may disclose information that is useful to an attacker; for example, they may represent usernames that can be used at the application's login, and they may be used in social engineering attacks against the organisation's personnel. Unnecessary or excessive disclosure of email addresses may also lead to an increase in the volume of spam email received.
Issue remediation
You should review the email addresses being disclosed by the application, and consider removing any that are unnecessary, or replacing personal addresses with anonymous mailbox addresses (such as helpdesk@example.com).
/* carl@criticalmass.com */ function BaseLibrary(){ var t = this; var v = navigator.appVersion.toLowerCase(), u = navigator.userAgent.toLowerCase(), n = navigator.appName; var d = document; t.ua = new Object(); t.u ...[SNIP]...
The file robots.txt is used to give instructions to web robots, such as search engine crawlers, about locations within the web site which robots are allowed, or not allowed, to crawl and index.
The presence of the robots.txt does not in itself present any kind of security vulnerability. However, it is often used to identify restricted or private areas of a site's contents. The information in the file may therefore help an attacker to map out the site's contents, especially if some of the locations identified are not linked from elsewhere in the site. If the application relies on robots.txt to protect access to these areas, and does not enforce proper access control over them, then this presents a serious vulnerability.
Issue remediation
The robots.txt file is not itself a security threat, and its correct use can represent good practice for non-security reasons. You should not assume that all web robots will honour the file's instructions. Rather, assume that attackers will pay close attention to any locations identified in the file. Do not rely on robots.txt to provide any kind of protection over unauthorised access.
Request
GET /robots.txt HTTP/1.0 Host: www.wireless.att.com
Response
HTTP/1.0 200 OK Server: Apache Last-Modified: Mon, 20 Jun 2011 17:19:29 GMT ETag: "be-4a627f019ca40" Accept-Ranges: bytes Content-Length: 190 Content-Type: text/plain Date: Tue, 06 Sep 2011 11:04:23 GMT Connection: close
If a web response states that it contains HTML content but does not specify a character set, then the browser may analyse the HTML and attempt to determine which character set it appears to be using. Even if the majority of the HTML actually employs a standard character set such as UTF-8, the presence of non-standard characters anywhere in the response may cause the browser to interpret the content using a different character set. This can have unexpected results, and can lead to cross-site scripting vulnerabilities in which non-standard encodings like UTF-7 can be used to bypass the application's defensive filters.
In most cases, the absence of a charset directive does not constitute a security flaw, particularly if the response contains static content. You should review the contents of the response and the context in which it appears to determine whether any vulnerability exists.
Issue remediation
For every response containing HTML content, the application should include within the Content-type header a directive specifying a standard recognised character set, for example charset=ISO-8859-1.
If a web response specifies an incorrect content type, then browsers may process the response in unexpected ways. If the specified content type is a renderable text-based format, then the browser will usually attempt to parse and render the response in that format. If the specified type is an image format, then the browser will usually detect the anomaly and will analyse the actual content and attempt to determine its MIME type. Either case can lead to unexpected results, and if the content contains any user-controllable data may lead to cross-site scripting or other client-side vulnerabilities.
In most cases, the presence of an incorrect content type statement does not constitute a security flaw, particularly if the response contains static content. You should review the contents of the response and the context in which it appears to determine whether any vulnerability exists.
Issue remediation
For every response containing a message body, the application should include a single Content-type header which correctly and unambiguously states the MIME type of the content in the response body.
// Provide a default path to dwr.engine if (dwr == null) var dwr = {}; if (dwr.engine == null) dwr.engine = {}; if (DWREngine == null) var DWREngine = dwr.engine;
The response contains the following Content-type statement:
Content-Type: text/html; charset=iso-8859-1
The response states that it contains HTML. However, it actually appears to contain plain text.
Request
GET /home/video_progressive/gvp/mp4/ HTTP/1.1 Host: www.wireless.att.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
