checkout_type request parameter, Cross Site Scripting, XSS, CWE-79, CAPEC-86

The value of the checkout_type request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 71213'%3balert(1)//9c120c89b71eabeaf was submitted in the checkout_type parameter. This input was echoed as 71213';alert(1)//9c120c89b71eabeaf 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 original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.

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 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.

Request

GET /cart/enter_ordering_info?checkout_type=171213'%3balert(1)//9c120c89b71eabeaf&submit=Check+out+without+registering+%C2%BB HTTP/1.1
Host: www.bagsbuy.com
Connection: keep-alive
Referer: https://www.bagsbuy.com/cust/landing
Cache-Control: max-age=0
Origin: https://www.bagsbuy.com
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.94 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: sb2=AAAAgU1VR1MAAEdpAyzrAg==; NSC_1-26STU9-qh10.101.208.19=ffffffff096da87a45525d5f4f58455e445a4a423660; cmTPSet=Y; CoreID6=73463312010912974344844&ci=90220420; JSESSIONID=vtpob19hv2; id=173_193_214_243Z2239212974346; amcus=; amcd=35637d80dbe614847c9f1f39fe8db953%2C01%2C1%2C1%2C4%2C6S5s%2C6%2C6c@@%7C@%7C%7C%7C@; 90220420_clogin=l=1297434484&v=1&e=1297436564994; 90220420_clogin=l=1297434484&v=1&e=1297436571309; sbcrt=1; uid=CmW2a01VSIUAAEdnAy4jAg==; Bagsbuy.com_sess=588dd3b832c65899943c474eda4e26cf; cmRS=&t1=1297434764988&t2=1297434767096&t3=1297434790843&t4=1297434763368&fti=1297434771307&fn=page_form%3A0%3B&ac=0:S&fd=0%3A0%3ASWC_46812227%3B&uer=&fu=/cart/update&pi=cart&ho=data.coremetrics.com/cm%3F&ci=90220420&cjen=1

Response

HTTP/1.1 200 OK
Date: Fri, 11 Feb 2011 14:41:06 GMT
Server: Apache
Edge-control: no-store, max-age=0, downstream-ttl=0
Content-Type: text/html
Set-Cookie: Bagsbuy.com_sess=588dd3b832c65899943c474eda4e26cf; path=/; expires=Fri, 18-Feb-2011 14:41:07 GMT
Connection: close
Content-Length: 24529

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8">
<title>Ch
...[SNIP]...
<!--
   var amPid = '384';
   var amParams = 'checkout_type=171213';alert(1)//9c120c89b71eabeaf';
   var amHost = (("https:" == document.location.protocol) ? "https://secure-" : "http://");
   document.write("<scr"+"ipt type='text/javascript' src='" + amHost + "cache.amadesa.com/static/client_js/eng
...[SNIP]...

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

/cart/enter_ordering_info
/cust/landing

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.

2.1. https://www.bagsbuy.com/cart/enter_ordering_info next

Summary

Severity:	Medium
Confidence:	Firm
Host:	https://www.bagsbuy.com
Path:	/cart/enter_ordering_info

Issue detail

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

Bagsbuy.com_sess=588dd3b832c65899943c474eda4e26cf; path=/; expires=Fri, 18-Feb-2011 14:36:20 GMT

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

Request

POST /cart/enter_ordering_info HTTP/1.1
Host: www.bagsbuy.com
Connection: keep-alive
Referer: https://www.bagsbuy.com/cust/landing
Cache-Control: max-age=0
Origin: https://www.bagsbuy.com
Content-Type: application/x-www-form-urlencoded
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.94 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: sb2=AAAAgU1VR1MAAEdpAyzrAg==; NSC_1-26STU9-qh10.101.208.19=ffffffff096da87a45525d5f4f58455e445a4a423660; cmTPSet=Y; CoreID6=73463312010912974344844&ci=90220420; JSESSIONID=vtpob19hv2; id=173_193_214_243Z2239212974346; amcus=; amcd=35637d80dbe614847c9f1f39fe8db953%2C01%2C1%2C1%2C4%2C6S5s%2C6%2C6c@@%7C@%7C%7C%7C@; 90220420_clogin=l=1297434484&v=1&e=1297436564994; 90220420_clogin=l=1297434484&v=1&e=1297436571309; sbcrt=1; uid=CmW2a01VSIUAAEdnAy4jAg==; Bagsbuy.com_sess=588dd3b832c65899943c474eda4e26cf; cmRS=&t1=1297434764988&t2=1297434767096&t3=1297434790843&t4=1297434763368&fti=1297434771307&fn=page_form%3A0%3B&ac=0:S&fd=0%3A0%3ASWC_46812227%3B&uer=&fu=/cart/update&pi=cart&ho=data.coremetrics.com/cm%3F&ci=90220420&cjen=1
Content-Length: 59

checkout_type=1&submit=Check+out+without+registering+%C2%BB

Response

HTTP/1.1 200 OK
Date: Fri, 11 Feb 2011 14:36:19 GMT
Server: Apache
Edge-control: no-store, max-age=0, downstream-ttl=0
Content-Type: text/html
Set-Cookie: Bagsbuy.com_sess=588dd3b832c65899943c474eda4e26cf; path=/; expires=Fri, 18-Feb-2011 14:36:20 GMT
Connection: close
Content-Length: 33036

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8">
<title>Ch
...[SNIP]...

2.2. https://www.bagsbuy.com/cust/landing previous next

Summary

Severity:	Medium
Confidence:	Firm
Host:	https://www.bagsbuy.com
Path:	/cust/landing

Issue detail

The following cookies were issued by the application and do not have the secure flag set:

Bagsbuy.com_sess=588dd3b832c65899943c474eda4e26cf; path=/; expires=Fri, 18-Feb-2011 14:35:16 GMT
uid=CmW2a01VSSMAAC1aAy/KAg==; path=/; expires=Thu, 11-Feb-21 02:35:15 GMT

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.

Request

GET /cust/landing HTTP/1.1
Host: www.bagsbuy.com
Connection: keep-alive
Referer: http://www.bagsbuy.com/cart/update
Cache-Control: max-age=0
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.94 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: sb2=AAAAgU1VR1MAAEdpAyzrAg==; NSC_1-26STU9-qh10.101.208.19=ffffffff096da87a45525d5f4f58455e445a4a423660; cmTPSet=Y; CoreID6=73463312010912974344844&ci=90220420; JSESSIONID=vtpob19hv2; id=173_193_214_243Z2239212974346; amcus=; amcd=35637d80dbe614847c9f1f39fe8db953%2C01%2C1%2C1%2C4%2C6S5s%2C6%2C6c@@%7C@%7C%7C%7C@; 90220420_clogin=l=1297434484&v=1&e=1297436564994; 90220420_clogin=l=1297434484&v=1&e=1297436571309; cmRS=&t1=1297434764988&t2=1297434767096&t3=-1&t4=1297434763368&fti=1297434771307&fn=page_form%3A0%3B&ac=0:S&fd=0%3A0%3ASWC_46812227%3B&uer=&fu=/cart/update&pi=cart&ho=data.coremetrics.com/cm%3F&ci=90220420&cjen=1; Bagsbuy.com_sess=588dd3b832c65899943c474eda4e26cf; sbcrt=1

Response

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

/cart/enter_ordering_info
/cust/landing

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. https://www.bagsbuy.com/cart/enter_ordering_info previous next

Summary

Severity:	Low
Confidence:	Firm
Host:	https://www.bagsbuy.com
Path:	/cart/enter_ordering_info

Issue detail

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

Bagsbuy.com_sess=588dd3b832c65899943c474eda4e26cf; path=/; expires=Fri, 18-Feb-2011 14:36:20 GMT

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

Request

Response

3.2. https://www.bagsbuy.com/cust/landing previous next

Summary

Severity:	Low
Confidence:	Firm
Host:	https://www.bagsbuy.com
Path:	/cust/landing

Issue detail

The following cookies were issued by the application and do not have the HttpOnly flag set:

Bagsbuy.com_sess=588dd3b832c65899943c474eda4e26cf; path=/; expires=Fri, 18-Feb-2011 14:35:16 GMT
uid=CmW2a01VSSMAAC1aAy/KAg==; path=/; expires=Thu, 11-Feb-21 02:35:15 GMT

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.

Request

Response

4. Password field with autocomplete enabled previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	https://www.bagsbuy.com
Path:	/cust/landing

Issue detail

The page contains a form with the following action URL:

https://www.bagsbuy.com/cart/enter_ordering_info

The form contains the following password field with autocomplete enabled:

Password

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).

Request

Response

HTTP/1.1 200 OK
Date: Fri, 11 Feb 2011 14:35:15 GMT
Server: Apache
Edge-control: no-store, max-age=0, downstream-ttl=0
Content-Type: text/html
Set-Cookie: uid=CmW2a01VSSMAAC1aAy/KAg==; path=/; expires=Thu, 11-Feb-21 02:35:15 GMT
Set-Cookie: Bagsbuy.com_sess=588dd3b832c65899943c474eda4e26cf; path=/; expires=Fri, 18-Feb-2011 14:35:16 GMT
Connection: close
Content-Length: 8819

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8">
<title>Car
...[SNIP]...
</p>

<form method="post" action="/cart/enter_ordering_info" onsubmit="return login_submitted();">
<input type="hidden" name="preclass" value="Cust">
...[SNIP]...
<td><input class="textbox" type="password" id="Password" name="Password" class="textbox" size="35" maxlength="30" /></td>
...[SNIP]...

5. Cross-domain script include previous next
There are 2 instances of this issue:

/cart/enter_ordering_info
/cust/landing

Issue background

When an application includes a script from an external domain, this script is executed by the browser within the security context of the invoking application. The script can therefore do anything that the application's own scripts can do, such as accessing application data and performing actions within the context of the current user.

If you include a script from an external domain, then you are trusting that domain with the data and functionality of your application, and you are trusting the domain's own security to prevent an attacker from modifying the script to perform malicious actions within your application.

Issue remediation

Scripts should not be included from untrusted domains. If you have a requirement which a third-party script appears to fulfil, then you should ideally copy the contents of that script onto your own domain and include it from there. If that is not possible (e.g. for licensing reasons) then you should consider reimplementing the script's functionality within your own code.

5.1. https://www.bagsbuy.com/cart/enter_ordering_info previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://www.bagsbuy.com
Path:	/cart/enter_ordering_info

Issue detail

The response dynamically includes the following script from another domain:

https://libs.coremetrics.com/eluminate.js

Request

Response

5.2. https://www.bagsbuy.com/cust/landing previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://www.bagsbuy.com
Path:	/cust/landing

Issue detail

The response dynamically includes the following script from another domain:

https://libs.coremetrics.com/eluminate.js

Request

Response

HTTP/1.1 200 OK
Date: Fri, 11 Feb 2011 14:35:15 GMT
Server: Apache
Edge-control: no-store, max-age=0, downstream-ttl=0
Content-Type: text/html
Set-Cookie: uid=CmW2a01VSSMAAC1aAy/KAg==; path=/; expires=Thu, 11-Feb-21 02:35:15 GMT
Set-Cookie: Bagsbuy.com_sess=588dd3b832c65899943c474eda4e26cf; path=/; expires=Fri, 18-Feb-2011 14:35:16 GMT
Connection: close
Content-Length: 8819

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8">
<title>Car
...[SNIP]...


<script type="text/javascript" src="//libs.coremetrics.com/eluminate.js"></script>
...[SNIP]...

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

/cart/enter_ordering_info
/cust/landing

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://www.bagsbuy.com/cart/enter_ordering_info previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://www.bagsbuy.com
Path:	/cart/enter_ordering_info

Request

Response

6.2. https://www.bagsbuy.com/cust/landing previous

Summary

Severity:	Information
Confidence:	Certain
Host:	https://www.bagsbuy.com
Path:	/cust/landing

Request

Response

7. SSL certificate previous

Summary

Severity:	Information
Confidence:	Certain
Host:	https://www.bagsbuy.com
Path:	/

Issue detail

The server presented a valid, trusted SSL certificate. This issue is purely informational.

The server presented the following certificates:

Server certificate

Issued to:	www.bagsbuy.com
Issued by:	VeriSign Class 3 Extended Validation SSL CA
Valid from:	Tue Oct 20 19:00:00 CDT 2009
Valid to:	Wed Oct 19 18:59:59 CDT 2011

Certificate chain #1

Issued to:	VeriSign Class 3 Extended Validation SSL CA
Issued by:	VeriSign Class 3 Public Primary Certification Authority - G5
Valid from:	Tue Nov 07 18:00:00 CST 2006
Valid to:	Mon Nov 07 17:59:59 CST 2016

Certificate chain #2

Issued to:	VeriSign Class 3 Public Primary Certification Authority - G5
Issued by:	Class 3 Public Primary Certification Authority
Valid from:	Tue Nov 07 18:00:00 CST 2006
Valid to:	Sun Nov 07 17:59:59 CST 2021

Certificate chain #3

Issued to:	Class 3 Public Primary Certification Authority
Issued by:	Class 3 Public Primary Certification Authority
Valid from:	Sun Jan 28 18:00:00 CST 1996
Valid to:	Wed Aug 02 18:59:59 CDT 2028

Issue background

SSL helps to protect the confidentiality and integrity of information in transit between the browser and server, and to provide authentication of the server's identity. To serve this purpose, the server must present an SSL certificate which is valid for the server's hostname, is issued by a trusted authority and is valid for the current date. If any one of these requirements is not met, SSL connections to the server will not provide the full protection for which SSL is designed.

It should be noted that various attacks exist against SSL in general, and in the context of HTTPS web connections. It may be possible for a determined and suitably-positioned attacker to compromise SSL connections without user detection even when a valid SSL certificate is used.

Report generated by CloudScan Vulnerability Crawler at Fri Feb 11 08:45:47 CST 2011.