Report generated by XSS.CX at Sat Nov 20 14:24:45 CST 2010.

Cross Site Scripting Reports | Hoyt LLC Research

Loading

1. Cross-site scripting (reflected)

2. Cross-domain script include

3. Cookie without HttpOnly flag set


1. Cross-site scripting (reflected)  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://nationalpost.shoplocal.com
Path:   /

Issue detail

The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload ae686'-alert(1)-'a67a5a821ec 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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.

Issue background

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

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

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

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

Remediation background

In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of defenses: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 /?ae686'-alert(1)-'a67a5a821ec=1 HTTP/1.1
Host: nationalpost.shoplocal.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
Cache-Control: private
Content-Type: text/html; charset=utf-8
Server: Microsoft-IIS/7.0
Set-Cookie: ASP.NET_SessionId=xfcsle45ec55zu55hmhiod24; path=/; HttpOnly
X-AspNet-Version: 2.0.50727
Set-Cookie: SLHCookie=City=Toronto&State=ON&CountryID=2&ZipCode5=M4W 1A7&Sniff=50&DMA=0&DMAName=&CLat=0.762199910205056&CLong=-1.38551924198665&NLat=0.770047699506353&SLat=0.754352120903759&WLong=-1.39336703128795&ELong=-1.37767145268535&UseMiles=False&SessionID=0; expires=Tue, 20-Nov-2035 05:05:56 GMT; path=/
Set-Cookie: Prefs=SLHPageCounter=1&SessionCookiesSet=true; path=/
P3P: CP="NON DSP TAIa PSAa PSDa OUR NOR IND ONL UNI COM NAV INT"
X-Powered-By: ASP.NET
Date: Sat, 20 Nov 2010 05:05:55 GMT
Connection: close
Content-Length: 36195


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


<html xmlns="http://www.w3.org/1999/xhtml" >
<head>

   
   
...[SNIP]...
<script language="javascript">
var pt = new Image();
pt.src = 'http://pt.crossmediaservices.com/pt/default.aspx?ae686'-alert(1)-'a67a5a821ec=1&action=home&referrer=&random=1303580955&siteid=869&City=Toronto&State=ON&CountryID=2&ZipCode5=M4W%20%201A7&Sniff=50&DMA=0&DMAName=&CLat=0.762199910205056&CLong=-1.38551924198665&NLat=0.7700476995063
...[SNIP]...
2. Cross-domain script include  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://nationalpost.shoplocal.com
Path:   /

Issue detail

The response dynamically includes the following scripts from other domains:

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.

Request

GET / HTTP/1.1
Host: nationalpost.shoplocal.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
Cache-Control: private
Content-Type: text/html; charset=utf-8
Server: Microsoft-IIS/7.0
Set-Cookie: ASP.NET_SessionId=0w4u042jwucm5j45la3sbd55; path=/; HttpOnly
X-AspNet-Version: 2.0.50727
Set-Cookie: SLHCookie=City=Toronto&State=ON&CountryID=2&ZipCode5=M4W 1A7&Sniff=50&DMA=0&DMAName=&CLat=0.762199910205056&CLong=-1.38551924198665&NLat=0.770047699506353&SLat=0.754352120903759&WLong=-1.39336703128795&ELong=-1.37767145268535&UseMiles=False&SessionID=0; expires=Tue, 20-Nov-2035 05:05:50 GMT; path=/
Set-Cookie: Prefs=SLHPageCounter=1&SessionCookiesSet=true; path=/
P3P: CP="NON DSP TAIa PSAa PSDa OUR NOR IND ONL UNI COM NAV INT"
X-Powered-By: ASP.NET
Date: Sat, 20 Nov 2010 05:05:50 GMT
Connection: close
Content-Length: 35949


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


<html xmlns="http://www.w3.org/1999/xhtml" >
<head>

   
   
...[SNIP]...
</script>
<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/prototype/1.6.0.2/prototype.js"></script>
<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/scriptaculous/1.8.1/scriptaculous.js?load=effects"></script>
...[SNIP]...
</script>
<script language="javascript1.1" src="http://www.canada.com/js/thirdpartyads/canwest_default_variables.js"></script>
<script language="javascript1.1" src="http://www.canada.com/js/thirdpartyads/shoplocal_variables.js"></script>
...[SNIP]...
<!-- SiteCatalyst code version: H.2.
Copyright 1997-2005 Omniture, Inc. More info available at
http://www.omniture.com -->
<script language="JavaScript" src="http://www.canada.com/js/canshopping_s_code.js"></script>
...[SNIP]...
<div style="position:relative;z-index:5000;">

<script type="text/javascript" src="http://www.nationalpost.com/scripts/include.aspx?file=/_assets/include/thirdparty/shoplocal/header.asp"></script>
...[SNIP]...
</div>

<script type="text/javascript" src="http://www.nationalpost.com/scripts/include.aspx?file=/_assets/include/thirdparty/shoplocal/footer.asp"></script>
...[SNIP]...
3. Cookie without HttpOnly flag set  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   http://nationalpost.shoplocal.com
Path:   /

Issue detail

The following cookies were issued by the application and do not have the HttpOnly flag set: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.

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: nationalpost.shoplocal.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
Cache-Control: private
Content-Type: text/html; charset=utf-8
Server: Microsoft-IIS/7.0
Set-Cookie: ASP.NET_SessionId=0w4u042jwucm5j45la3sbd55; path=/; HttpOnly
X-AspNet-Version: 2.0.50727
Set-Cookie: SLHCookie=City=Toronto&State=ON&CountryID=2&ZipCode5=M4W 1A7&Sniff=50&DMA=0&DMAName=&CLat=0.762199910205056&CLong=-1.38551924198665&NLat=0.770047699506353&SLat=0.754352120903759&WLong=-1.39336703128795&ELong=-1.37767145268535&UseMiles=False&SessionID=0; expires=Tue, 20-Nov-2035 05:05:50 GMT; path=/
Set-Cookie: Prefs=SLHPageCounter=1&SessionCookiesSet=true; path=/
P3P: CP="NON DSP TAIa PSAa PSDa OUR NOR IND ONL UNI COM NAV INT"
X-Powered-By: ASP.NET
Date: Sat, 20 Nov 2010 05:05:50 GMT
Connection: close
Content-Length: 35949


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


<html xmlns="http://www.w3.org/1999/xhtml" >
<head>

   
   
...[SNIP]...
Report generated by XSS.CX at Sat Nov 20 14:24:45 CST 2010.

<