The value of the Referer HTTP header is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload b3a98"><script>alert(1)</script>ff110ca5099 was submitted in the Referer HTTP header. 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 request header, the application's behaviour is not trivial to exploit in an attack against another user. In the past, methods have existed of using client-side technologies such as Flash to cause another user to make a request containing an arbitrary HTTP header. If you can use such a technique, you can probably leverage it to exploit the XSS flaw. This limitation partially mitigates the impact of the vulnerability.
Issue background
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.
Issue remediation
In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of defenses:
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.
Request
GET /en_GX/webadmin/forms/contactUs.jhtml HTTP/1.1 Host: www.pwc.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: PWC_WOD=id=173.193.214.243-2605364368.30126492:lv=1294760111214:ss=1294760084820; __utmz=257467274.1294756485.1.1.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=price%20waterhouse; __utma=257467274.728746398.1294756485.1294756485.1294756485.1; __utmc=257467274; __utmb=257467274.1.10.1294756485; LD.previous.visitor.us.pwc.com=true; Referer: http://www.google.com/search?hl=en&q=b3a98"><script>alert(1)</script>ff110ca5099
Response
HTTP/1.1 200 OK Server: IBM_HTTP_Server P3P: policyref="http://www.pwc.com/w3c/p3p.xml", CP="CAO DSP COR CURa ADMa DEVa TAIa PSAa PSDa IVAi IVDi CONi OUR SAMi PUBi IND PHY ONL UNI PUR COM NAV INT DEM CNT STA" Content-Type: text/html; charset=utf-8 Content-Language: en-US Date: Tue, 11 Jan 2011 14:35:30 GMT Content-Length: 28240 Connection: close
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-gx" lang="en-gx"> <h ...[SNIP]... <input type="hidden" name="SourceLink" value="http://www.google.com/search?hl=en&q=b3a98"><script>alert(1)</script>ff110ca5099" /> ...[SNIP]...
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.
Request
GET /us/en/issues/cloud-computing/index.jhtml?WT.ac=vt-us-cloud HTTP/1.1 Host: www.pwc.com Proxy-Connection: keep-alive Referer: http://www.pwc.com/us/en/technology/index.jhtml Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: LD.previous.visitor.us.pwc.com=true; __utmz=257467274.1294756485.1.1.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=price%20waterhouse; __utma=257467274.728746398.1294756485.1294756485.1294756485.1; __utmc=257467274; __utmb=257467274.1.10.1294756485; PWC_WOD=id=173.193.214.243-2605364368.30126492:lv=1294760107159:ss=1294760084820
Response
HTTP/1.1 200 OK Server: IBM_HTTP_Server Vary: Accept-Encoding P3P: policyref="http://www.pwc.com/w3c/p3p.xml", CP="CAO DSP COR CURa ADMa DEVa TAIa PSAa PSDa IVAi IVDi CONi OUR SAMi PUBi IND PHY ONL UNI PUR COM NAV INT DEM CNT STA" Content-Type: text/html; charset=utf-8 Content-Language: en-US Date: Tue, 11 Jan 2011 14:34:34 GMT Connection: close Content-Length: 21267
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.
The response dynamically includes the following script from another domain:
http://code.jquery.com/jquery-1.4.2.min.js
Request
GET /en_GX/webadmin/forms/contactUs.jhtml HTTP/1.1 Host: www.pwc.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: PWC_WOD=id=173.193.214.243-2605364368.30126492:lv=1294760111214:ss=1294760084820; __utmz=257467274.1294756485.1.1.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=price%20waterhouse; __utma=257467274.728746398.1294756485.1294756485.1294756485.1; __utmc=257467274; __utmb=257467274.1.10.1294756485; LD.previous.visitor.us.pwc.com=true;
Response
HTTP/1.1 200 OK Server: IBM_HTTP_Server P3P: policyref="http://www.pwc.com/w3c/p3p.xml", CP="CAO DSP COR CURa ADMa DEVa TAIa PSAa PSDa IVAi IVDi CONi OUR SAMi PUBi IND PHY ONL UNI PUR COM NAV INT DEM CNT STA" Content-Type: text/html; charset=utf-8 Content-Language: en-US Date: Tue, 11 Jan 2011 14:34:59 GMT Content-Length: 28160 Connection: close
The response dynamically includes the following script from another domain:
http://code.jquery.com/jquery-1.4.2.min.js
Request
GET /en_GX/webadmin/forms/email_a_colleague.jhtml HTTP/1.1 Host: www.pwc.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: PWC_WOD=id=173.193.214.243-2605364368.30126492:lv=1294760111214:ss=1294760084820; __utmz=257467274.1294756485.1.1.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=price%20waterhouse; __utma=257467274.728746398.1294756485.1294756485.1294756485.1; __utmc=257467274; __utmb=257467274.1.10.1294756485; LD.previous.visitor.us.pwc.com=true;
Response
HTTP/1.1 200 OK Server: IBM_HTTP_Server P3P: policyref="http://www.pwc.com/w3c/p3p.xml", CP="CAO DSP COR CURa ADMa DEVa TAIa PSAa PSDa IVAi IVDi CONi OUR SAMi PUBi IND PHY ONL UNI PUR COM NAV INT DEM CNT STA" Content-Type: text/html; charset=utf-8 Content-Language: en-US Date: Tue, 11 Jan 2011 14:34:59 GMT Content-Length: 13960 Connection: close
The response dynamically includes the following script from another domain:
http://code.jquery.com/jquery-1.4.2.min.js
Request
GET /gx/en/annual-review HTTP/1.1 Host: www.pwc.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: PWC_WOD=id=173.193.214.243-2605364368.30126492:lv=1294760111214:ss=1294760084820; __utmz=257467274.1294756485.1.1.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=price%20waterhouse; __utma=257467274.728746398.1294756485.1294756485.1294756485.1; __utmc=257467274; __utmb=257467274.1.10.1294756485; LD.previous.visitor.us.pwc.com=true;
Response
HTTP/1.1 200 OK Server: IBM_HTTP_Server P3P: policyref="http://www.pwc.com/w3c/p3p.xml", CP="CAO DSP COR CURa ADMa DEVa TAIa PSAa PSDa IVAi IVDi CONi OUR SAMi PUBi IND PHY ONL UNI PUR COM NAV INT DEM CNT STA" Content-Type: text/html; charset=utf-8 Content-Language: en-US Date: Tue, 11 Jan 2011 14:34:59 GMT Content-Length: 17548 Connection: close
The response dynamically includes the following script from another domain:
http://code.jquery.com/jquery-1.4.2.min.js
Request
GET /gx/en/annual-review/facts-figures-2010.jhtml HTTP/1.1 Host: www.pwc.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: PWC_WOD=id=173.193.214.243-2605364368.30126492:lv=1294760111214:ss=1294760084820; __utmz=257467274.1294756485.1.1.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=price%20waterhouse; __utma=257467274.728746398.1294756485.1294756485.1294756485.1; __utmc=257467274; __utmb=257467274.1.10.1294756485; LD.previous.visitor.us.pwc.com=true;
Response
HTTP/1.1 200 OK Server: IBM_HTTP_Server P3P: policyref="http://www.pwc.com/w3c/p3p.xml", CP="CAO DSP COR CURa ADMa DEVa TAIa PSAa PSDa IVAi IVDi CONi OUR SAMi PUBi IND PHY ONL UNI PUR COM NAV INT DEM CNT STA" Content-Type: text/html; charset=utf-8 Content-Language: en-US Date: Tue, 11 Jan 2011 14:35:00 GMT Content-Length: 32216 Connection: close
The response dynamically includes the following script from another domain:
http://code.jquery.com/jquery-1.4.2.min.js
Request
GET /gx/en/index.jhtml HTTP/1.1 Host: www.pwc.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: PWC_WOD=id=173.193.214.243-2605364368.30126492:lv=1294760111214:ss=1294760084820; __utmz=257467274.1294756485.1.1.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=price%20waterhouse; __utma=257467274.728746398.1294756485.1294756485.1294756485.1; __utmc=257467274; __utmb=257467274.1.10.1294756485; LD.previous.visitor.us.pwc.com=true;
Response
HTTP/1.1 200 OK Server: IBM_HTTP_Server P3P: policyref="http://www.pwc.com/w3c/p3p.xml", CP="CAO DSP COR CURa ADMa DEVa TAIa PSAa PSDa IVAi IVDi CONi OUR SAMi PUBi IND PHY ONL UNI PUR COM NAV INT DEM CNT STA" Content-Type: text/html; charset=utf-8 Content-Language: en-US Date: Tue, 11 Jan 2011 14:34:59 GMT Connection: close Connection: Transfer-Encoding Content-Length: 35088
The response dynamically includes the following script from another domain:
http://code.jquery.com/jquery-1.4.2.min.js
Request
GET /us/en/10minutes/cloud-computing.jhtml HTTP/1.1 Host: www.pwc.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: PWC_WOD=id=173.193.214.243-2605364368.30126492:lv=1294760111214:ss=1294760084820; __utmz=257467274.1294756485.1.1.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=price%20waterhouse; __utma=257467274.728746398.1294756485.1294756485.1294756485.1; __utmc=257467274; __utmb=257467274.1.10.1294756485; LD.previous.visitor.us.pwc.com=true;
Response
HTTP/1.1 200 OK Server: IBM_HTTP_Server P3P: policyref="http://www.pwc.com/w3c/p3p.xml", CP="CAO DSP COR CURa ADMa DEVa TAIa PSAa PSDa IVAi IVDi CONi OUR SAMi PUBi IND PHY ONL UNI PUR COM NAV INT DEM CNT STA" Content-Type: text/html; charset=utf-8 Content-Language: en-US Date: Tue, 11 Jan 2011 14:34:58 GMT Content-Length: 19995 Connection: close
The response dynamically includes the following scripts from other domains:
http://code.jquery.com/jquery-1.4.2.min.js
http://widgets.twimg.com/j/2/widget.js
Request
GET /us/en/index.jhtml HTTP/1.1 Host: www.pwc.com Proxy-Connection: keep-alive Referer: http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=price+waterhouse Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: LD.previous.visitor.us.pwc.com=true
Response
HTTP/1.1 200 OK Server: IBM_HTTP_Server Vary: Accept-Encoding P3P: policyref="http://www.pwc.com/w3c/p3p.xml", CP="CAO DSP COR CURa ADMa DEVa TAIa PSAa PSDa IVAi IVDi CONi OUR SAMi PUBi IND PHY ONL UNI PUR COM NAV INT DEM CNT STA" Content-Type: text/html; charset=utf-8 Content-Language: en-US Date: Tue, 11 Jan 2011 14:34:06 GMT Connection: close Content-Length: 39880
The response dynamically includes the following script from another domain:
http://code.jquery.com/jquery-1.4.2.min.js
Request
GET /us/en/industry/index.jhtml HTTP/1.1 Host: www.pwc.com Proxy-Connection: keep-alive Referer: http://www.pwc.com/us/en/services/index.jhtml Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: LD.previous.visitor.us.pwc.com=true; __utmz=257467274.1294756485.1.1.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=price%20waterhouse; __utma=257467274.728746398.1294756485.1294756485.1294756485.1; __utmc=257467274; __utmb=257467274.1.10.1294756485; PWC_WOD=id=173.193.214.243-2605364368.30126492:lv=1294760101352:ss=1294760084820
Response
HTTP/1.1 200 OK Server: IBM_HTTP_Server Vary: Accept-Encoding P3P: policyref="http://www.pwc.com/w3c/p3p.xml", CP="CAO DSP COR CURa ADMa DEVa TAIa PSAa PSDa IVAi IVDi CONi OUR SAMi PUBi IND PHY ONL UNI PUR COM NAV INT DEM CNT STA" Content-Type: text/html; charset=utf-8 Content-Language: en-US Date: Tue, 11 Jan 2011 14:34:26 GMT Connection: close Content-Length: 17769
GET /us/en/issues/cloud-computing/index.jhtml?WT.ac=vt-us-cloud HTTP/1.1 Host: www.pwc.com Proxy-Connection: keep-alive Referer: http://www.pwc.com/us/en/technology/index.jhtml Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: LD.previous.visitor.us.pwc.com=true; __utmz=257467274.1294756485.1.1.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=price%20waterhouse; __utma=257467274.728746398.1294756485.1294756485.1294756485.1; __utmc=257467274; __utmb=257467274.1.10.1294756485; PWC_WOD=id=173.193.214.243-2605364368.30126492:lv=1294760107159:ss=1294760084820
Response
HTTP/1.1 200 OK Server: IBM_HTTP_Server Vary: Accept-Encoding P3P: policyref="http://www.pwc.com/w3c/p3p.xml", CP="CAO DSP COR CURa ADMa DEVa TAIa PSAa PSDa IVAi IVDi CONi OUR SAMi PUBi IND PHY ONL UNI PUR COM NAV INT DEM CNT STA" Content-Type: text/html; charset=utf-8 Content-Language: en-US Date: Tue, 11 Jan 2011 14:34:34 GMT Connection: close Content-Length: 21267
The response dynamically includes the following script from another domain:
http://code.jquery.com/jquery-1.4.2.min.js
Request
GET /us/en/issues/current-issues.jhtml HTTP/1.1 Host: www.pwc.com Proxy-Connection: keep-alive Referer: http://www.pwc.com/us/en/index.jhtml Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: LD.previous.visitor.us.pwc.com=true; __utmz=257467274.1294756485.1.1.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=price%20waterhouse; __utma=257467274.728746398.1294756485.1294756485.1294756485.1; __utmc=257467274; __utmb=257467274.1.10.1294756485; PWC_WOD=id=173.193.214.243-2605364368.30126492:lv=1294760084820:ss=1294760084820
Response
HTTP/1.1 200 OK Server: IBM_HTTP_Server Vary: Accept-Encoding P3P: policyref="http://www.pwc.com/w3c/p3p.xml", CP="CAO DSP COR CURa ADMa DEVa TAIa PSAa PSDa IVAi IVDi CONi OUR SAMi PUBi IND PHY ONL UNI PUR COM NAV INT DEM CNT STA" Content-Type: text/html; charset=utf-8 Content-Language: en-US Date: Tue, 11 Jan 2011 14:34:23 GMT Connection: close Content-Length: 22738
The response dynamically includes the following script from another domain:
http://code.jquery.com/jquery-1.4.2.min.js
Request
GET /us/en/services/index.jhtml HTTP/1.1 Host: www.pwc.com Proxy-Connection: keep-alive Referer: http://www.pwc.com/us/en/issues/current-issues.jhtml Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: LD.previous.visitor.us.pwc.com=true; __utmz=257467274.1294756485.1.1.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=price%20waterhouse; __utma=257467274.728746398.1294756485.1294756485.1294756485.1; __utmc=257467274; __utmb=257467274.1.10.1294756485; PWC_WOD=id=173.193.214.243-2605364368.30126492:lv=1294760099737:ss=1294760084820
Response
HTTP/1.1 200 OK Server: IBM_HTTP_Server Vary: Accept-Encoding P3P: policyref="http://www.pwc.com/w3c/p3p.xml", CP="CAO DSP COR CURa ADMa DEVa TAIa PSAa PSDa IVAi IVDi CONi OUR SAMi PUBi IND PHY ONL UNI PUR COM NAV INT DEM CNT STA" Content-Type: text/html; charset=utf-8 Content-Language: en-US Date: Tue, 11 Jan 2011 14:34:25 GMT Connection: close Content-Length: 22377
The response dynamically includes the following script from another domain:
http://code.jquery.com/jquery-1.4.2.min.js
Request
GET /us/en/technology/index.jhtml HTTP/1.1 Host: www.pwc.com Proxy-Connection: keep-alive Referer: http://www.pwc.com/us/en/industry/index.jhtml Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: LD.previous.visitor.us.pwc.com=true; __utmz=257467274.1294756485.1.1.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=price%20waterhouse; __utma=257467274.728746398.1294756485.1294756485.1294756485.1; __utmc=257467274; __utmb=257467274.1.10.1294756485; PWC_WOD=id=173.193.214.243-2605364368.30126492:lv=1294760102599:ss=1294760084820
Response
HTTP/1.1 200 OK Server: IBM_HTTP_Server Vary: Accept-Encoding P3P: policyref="http://www.pwc.com/w3c/p3p.xml", CP="CAO DSP COR CURa ADMa DEVa TAIa PSAa PSDa IVAi IVDi CONi OUR SAMi PUBi IND PHY ONL UNI PUR COM NAV INT DEM CNT STA" Content-Type: text/html; charset=utf-8 Content-Language: en-US Date: Tue, 11 Jan 2011 14:34:31 GMT Connection: close Content-Length: 22282
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).
The following email address was disclosed in the response:
webmaster@pwc.com
Request
GET /WTS/WebTrendsServlet.js?id=gx&locale=en_GX HTTP/1.1 Host: www.pwc.com Proxy-Connection: keep-alive Referer: http://www.pwc.com/en_GX/webadmin/forms/contactUs.jhtml Accept: */* User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: LD.previous.visitor.us.pwc.com=true; __utmz=257467274.1294756485.1.1.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=price%20waterhouse; __utma=257467274.728746398.1294756485.1294756485.1294756485.1; __utmc=257467274; PWC_WOD=id=173.193.214.243-2605364368.30126492:lv=1294760111214:ss=1294760084820
Response
HTTP/1.1 200 OK Server: IBM_HTTP_Server Vary: Accept-Encoding P3P: policyref="http://www.pwc.com/w3c/p3p.xml", CP="CAO DSP COR CURa ADMa DEVa TAIa PSAa PSDa IVAi IVDi CONi OUR SAMi PUBi IND PHY ONL UNI PUR COM NAV INT DEM CNT STA" Content-Type: text/html Content-Language: en-US Date: Wed, 12 Jan 2011 03:26:01 GMT Connection: close Content-Length: 14503
function domainValidation(){ var thisServer = "submit.pwc.com"; var isValidDomain = "true"; var isStagingDomain = "false"; if (isValidDomain == "true"){ return "approved"; } if (isStagi ...[SNIP]... name == ""){docLocation = "[Local]"} alert("Unauthorised Usage. \n\nThe domain " + docLocation + " is not authorised to access or \nexecute some code within this page. \n\nIf you wish, please notify webmaster@pwc.com of the page you are trying to \naccess so that we may investigate further.\n\nApologies for any inconvenience this may cause."); return ""; } var willDo = domainValidation();
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.pwc.com
Response
HTTP/1.0 200 OK Server: IBM_HTTP_Server Last-Modified: Sat, 20 Mar 2010 00:09:16 GMT ETag: "20-18b-464fe4bd" P3P: policyref="http://www.pwc.com/w3c/p3p.xml", CP="CAO DSP COR CURa ADMa DEVa TAIa PSAa PSDa IVAi IVDi CONi OUR SAMi PUBi IND PHY ONL UNI PUR COM NAV INT DEM CNT STA" Content-Type: text/plain Date: Tue, 11 Jan 2011 14:34:58 GMT Content-Length: 395 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.
Request
GET /WTS/WebTrendsServlet.js?id=us&locale=en_US HTTP/1.1 Host: www.pwc.com Proxy-Connection: keep-alive Referer: http://www.pwc.com/us/en/index.jhtml Accept: */* User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: LD.previous.visitor.us.pwc.com=true
Response
HTTP/1.1 200 OK Server: IBM_HTTP_Server Vary: Accept-Encoding P3P: policyref="http://www.pwc.com/w3c/p3p.xml", CP="CAO DSP COR CURa ADMa DEVa TAIa PSAa PSDa IVAi IVDi CONi OUR SAMi PUBi IND PHY ONL UNI PUR COM NAV INT DEM CNT STA" Content-Type: text/html Content-Language: en-US Date: Tue, 11 Jan 2011 14:34:08 GMT Connection: close Content-Length: 39810
// WebTrends SmartSource Data Collector Tag // Version: 8.6.0 // Tag Builder Version: 2.1.0 // Created: 11/17/2008 2:28:01 PM // Modified 10/14/2010 // v2.6
The response contains the following Content-type statement:
Content-Type: text/html
The response states that it contains HTML. However, it actually appears to contain script.
Issue background
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.
Request
GET /WTS/WebTrendsServlet.js?id=us&locale=en_US HTTP/1.1 Host: www.pwc.com Proxy-Connection: keep-alive Referer: http://www.pwc.com/us/en/index.jhtml Accept: */* User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: LD.previous.visitor.us.pwc.com=true
Response
HTTP/1.1 200 OK Server: IBM_HTTP_Server Vary: Accept-Encoding P3P: policyref="http://www.pwc.com/w3c/p3p.xml", CP="CAO DSP COR CURa ADMa DEVa TAIa PSAa PSDa IVAi IVDi CONi OUR SAMi PUBi IND PHY ONL UNI PUR COM NAV INT DEM CNT STA" Content-Type: text/html Content-Language: en-US Date: Tue, 11 Jan 2011 14:34:08 GMT Connection: close Content-Length: 39810
// WebTrends SmartSource Data Collector Tag // Version: 8.6.0 // Tag Builder Version: 2.1.0 // Created: 11/17/2008 2:28:01 PM // Modified 10/14/2010 // v2.6