XSS, Reflected Cross Site Scripting, CWE-79, CAPEC-86, shopping.billmelater.com

The value of the url request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload f1d88"%3balert(1)//e5c8cd4c537 was submitted in the url parameter. This input was echoed as f1d88";alert(1)//e5c8cd4c537 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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.

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:

Input should be validated as strictly as possible on arrival, given the kind of content which it is expected to contain. For example, personal names should consist of alphabetical and a small range of typographical characters, and be relatively short; a year of birth should consist of exactly four numerals; email addresses should match a well-defined regular expression. Input which fails the validation should be rejected, not sanitised.
User input should be HTML-encoded at any point where it is copied into application responses. All HTML metacharacters, including < > " ' and =, should be replaced with the corresponding HTML entities (< > etc).

In cases where the application's functionality allows users to author content using a restricted subset of HTML tags and attributes (for example, blog comments which allow limited formatting and linking), it is necessary to parse the supplied HTML to validate that it does not use any dangerous syntax; this is a non-trivial task.

Request

GET /link?source=thefind&page=air+purifiers&aff=3&store=48&url=http%3A%2F%2Fclick.linksynergy.com%2Ffs-bin%2Fclick%3Fid%3DxPME9IDb*eY%26offerid%3D101744.4315245%26type%3D15%26subid%3D0f1d88"%3balert(1)//e5c8cd4c537 HTTP/1.1
Host: shopping.billmelater.com
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Referer: http://wwwb.search.billmelater.com/qq-air-purifiers
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: __qca=P0-531746133-1318542886845; JSESSIONID=21C0DCAD0723F198CED734EC1C126A45.node5; PSP_T3021=-2e887a2ffe7d3aef8f63a7437861c621db9f6277876d55168f3cfe7247713b39; c_event18=event18; gpv_p23=Shop%3Ahtml%3Acommon%3Aredirect.xhtml; s_cc=true; s_sq=i4billmelaterdev2%3D%2526pid%253DCons%25253AHome%2526pidt%253D1%2526oid%253Dhttps%25253A//www.billmelater.com/images/button-Search_rect.png%2526ot%253DIMAGE

Response

HTTP/1.1 200 OK
Date: Fri, 14 Oct 2011 17:58:37 GMT
Content-Type: text/html;charset=UTF-8
Set-Cookie: PSP_T3021=-2e887a2ffe7d3aef8f63a7437861c621db9f6277876d55168f3cfe7247713b39; Expires=Sat, 13-Oct-2012 17:58:38 GMT; Path=/
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Length: 9984

<!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>
<link class="component
...[SNIP]...
<![CDATA[
var urlRedirect = encodeURI("http://click.linksynergy.com/fs-bin/click?id=xPME9IDb*eY&offerid=101744.4315245&type=15&subid=0f1d88";alert(1)//e5c8cd4c537&u1=-2fe9b968845ef04c358cca18e8f1ac84");
setTimeout('window.location = urlRedirect', 1000);
//]]>
...[SNIP]...

2. Password field with autocomplete enabled previous next
There are 2 instances of this issue:

/favicon.ico
/offers/onlineshoes/207825

Issue background

Most browsers have a facility to remember user credentials that are entered into HTML forms. This function can be configured by the user and also by applications which employ user credentials. If the function is enabled, then credentials entered by the user are stored on their local computer and retrieved by the browser on future visits to the same application.

The stored credentials can be captured by an attacker who gains access to the computer, either locally or through some remote compromise. Further, methods have existed whereby a malicious web site can retrieve the stored credentials for other applications, by exploiting browser vulnerabilities or through application-level cross-domain attacks.

Issue remediation

To prevent browsers from storing credentials entered into HTML forms, you should include the attribute autocomplete="off" within the FORM tag (to protect all form fields) or within the relevant INPUT tags (to protect specific individual fields).

2.1. https://shopping.billmelater.com/favicon.ico next

Summary

Severity:	Low
Confidence:	Certain
Host:	https://shopping.billmelater.com
Path:	/favicon.ico

Issue detail

The page contains a form with the following action URL:

https://shopping.billmelater.com/javascript:A4J.AJAX.SubmitForm('_viewRoot','loginForm',{'similarityGroupingId':'loginForm','parameters':{'loginForm':'loginForm'}%20,'actionUrl':'/html/pagenotfound.seam'}%20)

The form contains the following password field with autocomplete enabled:

loginForm:password

Request

GET /favicon.ico HTTP/1.1
Host: shopping.billmelater.com
Connection: keep-alive
Accept: */*
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1
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: __qca=P0-531746133-1318542886845; JSESSIONID=21C0DCAD0723F198CED734EC1C126A45.node5; PSP_T3021=-2e887a2ffe7d3aef8f63a7437861c621db9f6277876d55168f3cfe7247713b39; c_event18=event18; gpv_p23=Shop%3Ahtml%3Acommon%3Aredirect.xhtml; s_cc=true; s_sq=i4billmelaterdev2%3D%2526pid%253DCons%25253AHome%2526pidt%253D1%2526oid%253Dhttps%25253A//www.billmelater.com/images/button-Search_rect.png%2526ot%253DIMAGE

Response

HTTP/1.1 404 Not Found
Date: Fri, 14 Oct 2011 17:57:56 GMT
Content-Type: text/html;charset=UTF-8
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Length: 31710

<!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-equiv="Cont
...[SNIP]...
</form><form id="loginForm" name="loginForm" method="post" action="javascript:A4J.AJAX.SubmitForm('_viewRoot','loginForm',{'similarityGroupingId':'loginForm','parameters':{'loginForm':'loginForm'} ,'actionUrl':'/html/pagenotfound.seam'} )"><div id="loginForm:j_id15" class="loginDialogHeader">
...[SNIP]...
<td><input id="loginForm:password" type="password" name="loginForm:password" value="" class="loginInput" /></td>
...[SNIP]...

2.2. https://shopping.billmelater.com/offers/onlineshoes/207825 previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	https://shopping.billmelater.com
Path:	/offers/onlineshoes/207825

Issue detail

The page contains a form with the following action URL:

https://shopping.billmelater.com/offers/onlineshoes/javascript:A4J.AJAX.SubmitForm('_viewRoot','loginForm',{'similarityGroupingId':'loginForm','parameters':{'loginForm':'loginForm'}%20,'actionUrl':'/offer/x2Ddetail'}%20)

The form contains the following password field with autocomplete enabled:

loginForm:password

Request

GET /offers/onlineshoes/207825?source=billmelater HTTP/1.1
Host: shopping.billmelater.com
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
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: __qca=P0-531746133-1318542886845; PSP_T3021=-2e887a2ffe7d3aef8f63a7437861c621db9f6277876d55168f3cfe7247713b39; gpv_p23=Cons%3AHome; s_cc=true; s_sq=%5B%5BB%5D%5D

Response

HTTP/1.1 200 OK
Date: Fri, 14 Oct 2011 17:57:41 GMT
Content-Type: text/html;charset=UTF-8
Set-Cookie: PSP_T3021=-2e887a2ffe7d3aef8f63a7437861c621db9f6277876d55168f3cfe7247713b39; Expires=Sat, 13-Oct-2012 17:57:41 GMT; Path=/
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Length: 46226

<!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>
<link class="component
...[SNIP]...
</form><form id="loginForm" name="loginForm" method="post" action="javascript:A4J.AJAX.SubmitForm('_viewRoot','loginForm',{'similarityGroupingId':'loginForm','parameters':{'loginForm':'loginForm'} ,'actionUrl':'/offer\x2Ddetail'} )"><div id="loginForm:j_id15" class="loginDialogHeader">
...[SNIP]...
<td><input id="loginForm:password" type="password" name="loginForm:password" value="" class="loginInput" /></td>
...[SNIP]...

3. SSL cookie without secure flag set previous next
There are 3 instances of this issue:

/html/common/redirect.xhtml
/link
/offers/onlineshoes/207825

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.

3.1. https://shopping.billmelater.com/html/common/redirect.xhtml previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://shopping.billmelater.com
Path:	/html/common/redirect.xhtml

Issue detail

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

PSP_T3021=-2e887a2ffe7d3aef8f63a7437861c621db9f6277876d55168f3cfe7247713b39; Expires=Sat, 13-Oct-2012 17:57:56 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.

Request

GET /html/common/redirect.xhtml?query=xss%20sqli%20httpi%2088%20777%20666%2055555%20 HTTP/1.1
Host: shopping.billmelater.com
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
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: __qca=P0-531746133-1318542886845; JSESSIONID=21C0DCAD0723F198CED734EC1C126A45.node5; PSP_T3021=-2e887a2ffe7d3aef8f63a7437861c621db9f6277876d55168f3cfe7247713b39; c_event18=event18; gpv_p23=Shop%3Aoffers%3Aonlineshoes%3A207825; s_cc=true; s_sq=i4bmlglobalprod%2Ci4billmelaterdev2%3D%2526pid%253DCons%25253AHome%2526pidt%253D1%2526oid%253Dhttps%25253A//www.billmelater.com/images/button-Search_rect.png%2526ot%253DIMAGE

Response

HTTP/1.1 200 OK
Date: Fri, 14 Oct 2011 17:57:56 GMT
Content-Type: text/html;charset=UTF-8
Set-Cookie: PSP_T3021=-2e887a2ffe7d3aef8f63a7437861c621db9f6277876d55168f3cfe7247713b39; Expires=Sat, 13-Oct-2012 17:57:56 GMT; Path=/
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Length: 9907

<!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>
<link class="component
...[SNIP]...

3.2. https://shopping.billmelater.com/link previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://shopping.billmelater.com
Path:	/link

Issue detail

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

PSP_T3021=-2e887a2ffe7d3aef8f63a7437861c621db9f6277876d55168f3cfe7247713b39; Expires=Sat, 13-Oct-2012 17:58:12 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.

Request

GET /link?source=thefind&page=air+purifiers&aff=3&store=48&url=http%3A%2F%2Fclick.linksynergy.com%2Ffs-bin%2Fclick%3Fid%3DxPME9IDb*eY%26offerid%3D101744.4315245%26type%3D15%26subid%3D0 HTTP/1.1
Host: shopping.billmelater.com
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Referer: http://wwwb.search.billmelater.com/qq-air-purifiers
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: __qca=P0-531746133-1318542886845; JSESSIONID=21C0DCAD0723F198CED734EC1C126A45.node5; PSP_T3021=-2e887a2ffe7d3aef8f63a7437861c621db9f6277876d55168f3cfe7247713b39; c_event18=event18; gpv_p23=Shop%3Ahtml%3Acommon%3Aredirect.xhtml; s_cc=true; s_sq=i4billmelaterdev2%3D%2526pid%253DCons%25253AHome%2526pidt%253D1%2526oid%253Dhttps%25253A//www.billmelater.com/images/button-Search_rect.png%2526ot%253DIMAGE

Response

HTTP/1.1 200 OK
Date: Fri, 14 Oct 2011 17:58:12 GMT
Content-Type: text/html;charset=UTF-8
Set-Cookie: PSP_T3021=-2e887a2ffe7d3aef8f63a7437861c621db9f6277876d55168f3cfe7247713b39; Expires=Sat, 13-Oct-2012 17:58:12 GMT; Path=/
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Length: 9956

<!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>
<link class="component
...[SNIP]...

3.3. https://shopping.billmelater.com/offers/onlineshoes/207825 previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://shopping.billmelater.com
Path:	/offers/onlineshoes/207825

Issue detail

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

PSP_T3021=-2e887a2ffe7d3aef8f63a7437861c621db9f6277876d55168f3cfe7247713b39; Expires=Sat, 13-Oct-2012 17:57:41 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.

Request

Response

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

/html/common/redirect.xhtml
/link
/offers/onlineshoes/207825

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.

4.1. https://shopping.billmelater.com/html/common/redirect.xhtml previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://shopping.billmelater.com
Path:	/html/common/redirect.xhtml

Issue detail

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

PSP_T3021=-2e887a2ffe7d3aef8f63a7437861c621db9f6277876d55168f3cfe7247713b39; Expires=Sat, 13-Oct-2012 17:57:56 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.

Request

Response

4.2. https://shopping.billmelater.com/link previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://shopping.billmelater.com
Path:	/link

Issue detail

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

PSP_T3021=-2e887a2ffe7d3aef8f63a7437861c621db9f6277876d55168f3cfe7247713b39; Expires=Sat, 13-Oct-2012 17:58:12 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.

Request

GET /link?source=thefind&page=air+purifiers&aff=3&store=48&url=http%3A%2F%2Fclick.linksynergy.com%2Ffs-bin%2Fclick%3Fid%3DxPME9IDb*eY%26offerid%3D101744.4315245%26type%3D15%26subid%3D0 HTTP/1.1
Host: shopping.billmelater.com
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Referer: http://wwwb.search.billmelater.com/qq-air-purifiers
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: __qca=P0-531746133-1318542886845; JSESSIONID=21C0DCAD0723F198CED734EC1C126A45.node5; PSP_T3021=-2e887a2ffe7d3aef8f63a7437861c621db9f6277876d55168f3cfe7247713b39; c_event18=event18; gpv_p23=Shop%3Ahtml%3Acommon%3Aredirect.xhtml; s_cc=true; s_sq=i4billmelaterdev2%3D%2526pid%253DCons%25253AHome%2526pidt%253D1%2526oid%253Dhttps%25253A//www.billmelater.com/images/button-Search_rect.png%2526ot%253DIMAGE

Response

4.3. https://shopping.billmelater.com/offers/onlineshoes/207825 previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://shopping.billmelater.com
Path:	/offers/onlineshoes/207825

Issue detail

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

PSP_T3021=-2e887a2ffe7d3aef8f63a7437861c621db9f6277876d55168f3cfe7247713b39; Expires=Sat, 13-Oct-2012 17:57:41 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.

Request

Response

5. Email addresses disclosed previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://shopping.billmelater.com
Path:	/js/jquery.hoverIntent.minified.js

Issue detail

The following email address was disclosed in the response:

brian@cherne.net

Issue background

The presence of email addresses within application responses does not necessarily constitute a security vulnerability. Email addresses may appear intentionally within contact information, and many applications (such as web mail) include arbitrary third-party email addresses within their core content.

However, email addresses of developers and other individuals (whether appearing on-screen or hidden within page source) may disclose information that is useful to an attacker; for example, they may represent usernames that can be used at the application's login, and they may be used in social engineering attacks against the organisation's personnel. Unnecessary or excessive disclosure of email addresses may also lead to an increase in the volume of spam email received.

Issue remediation

You should review the email addresses being disclosed by the application, and consider removing any that are unnecessary, or replacing personal addresses with anonymous mailbox addresses (such as helpdesk@example.com).

Request

GET /js/jquery.hoverIntent.minified.js HTTP/1.1
Host: shopping.billmelater.com
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1
Accept: */*
Referer: https://shopping.billmelater.com/offers/onlineshoes/207825?source=billmelater
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: __qca=P0-531746133-1318542886845; gpv_p23=Cons%3AHome; s_cc=true; s_sq=%5B%5BB%5D%5D; JSESSIONID=21C0DCAD0723F198CED734EC1C126A45.node5; PSP_T3021=-2e887a2ffe7d3aef8f63a7437861c621db9f6277876d55168f3cfe7247713b39

Response

HTTP/1.1 200 OK
Date: Fri, 14 Oct 2011 17:57:42 GMT
Accept-Ranges: bytes
ETag: W/"1609-1318266576000"
Last-Modified: Mon, 10 Oct 2011 17:09:36 GMT
Content-Type: text/javascript
Content-Length: 1609
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive

???/**
* hoverIntent r5 // 2007.03.27 // jQuery 1.1.2+
* <http://cherne.net/brian/resources/jquery.hoverIntent.html>
*
* @param f onMouseOver function || An object with configuration options
* @par
...[SNIP]...
<brian@cherne.net>
...[SNIP]...

6. Cacheable HTTPS response previous
There are 4 instances of this issue:

/html/common/redirect.xhtml
/image
/link
/offers/onlineshoes/207825

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:

Cache-control: no-store
Pragma: no-cache

6.1. https://shopping.billmelater.com/html/common/redirect.xhtml previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://shopping.billmelater.com
Path:	/html/common/redirect.xhtml

Request

Response

6.2. https://shopping.billmelater.com/image previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://shopping.billmelater.com
Path:	/image

Request

GET /image?id=27 HTTP/1.1
Host: shopping.billmelater.com
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1
Accept: */*
Referer: https://shopping.billmelater.com/offers/onlineshoes/207825?source=billmelater
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: __qca=P0-531746133-1318542886845; JSESSIONID=21C0DCAD0723F198CED734EC1C126A45.node5; PSP_T3021=-2e887a2ffe7d3aef8f63a7437861c621db9f6277876d55168f3cfe7247713b39; c_event18=event18; gpv_p23=Shop%3Aoffers%3Aonlineshoes%3A207825; s_cc=true; s_sq=%5B%5BB%5D%5D

Response

HTTP/1.1 200 OK
Date: Fri, 14 Oct 2011 17:57:47 GMT
Content-Type: application/octet-stream
Content-Length: 3536
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive

GIF89a.(...............=.m
.....i.....:..m........T.j.....t..]...........v..l..n..p..............j......e..U..P....n...-..F....................v.d..h...^..y.w...n...........r.......f...c....{"..N.c..
...[SNIP]...

6.3. https://shopping.billmelater.com/link previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://shopping.billmelater.com
Path:	/link

Request

GET /link?source=thefind&page=air+purifiers&aff=3&store=48&url=http%3A%2F%2Fclick.linksynergy.com%2Ffs-bin%2Fclick%3Fid%3DxPME9IDb*eY%26offerid%3D101744.4315245%26type%3D15%26subid%3D0 HTTP/1.1
Host: shopping.billmelater.com
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Referer: http://wwwb.search.billmelater.com/qq-air-purifiers
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: __qca=P0-531746133-1318542886845; JSESSIONID=21C0DCAD0723F198CED734EC1C126A45.node5; PSP_T3021=-2e887a2ffe7d3aef8f63a7437861c621db9f6277876d55168f3cfe7247713b39; c_event18=event18; gpv_p23=Shop%3Ahtml%3Acommon%3Aredirect.xhtml; s_cc=true; s_sq=i4billmelaterdev2%3D%2526pid%253DCons%25253AHome%2526pidt%253D1%2526oid%253Dhttps%25253A//www.billmelater.com/images/button-Search_rect.png%2526ot%253DIMAGE

Response

6.4. https://shopping.billmelater.com/offers/onlineshoes/207825 previous

Summary

Severity:	Information
Confidence:	Certain
Host:	https://shopping.billmelater.com
Path:	/offers/onlineshoes/207825

Request

Response

Report generated by XSS.CX at Fri Oct 14 13:00:27 CDT 2011.