Report generated by XSS.CX at Mon Nov 08 09:37:46 CST 2010.

Cross Site Scripting Reports | Hoyt LLC Research

1. Cross-site scripting (reflected)

1.1. http://boston30.autochooser.com/results.asp [name of an arbitrarily supplied request parameter]

1.2. http://boston30.autochooser.com/results.asp [pagename parameter]

1.3. http://boston30.autochooser.com/results.asp [postto parameter]

2. Cookie without HttpOnly flag set

3. Cross-domain Referer leakage

4. Cross-domain script include

5. Email addresses disclosed

6. HTML does not specify charset

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

/results.asp [name of an arbitrarily supplied request parameter]
/results.asp [pagename parameter]
/results.asp [postto 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. http://boston30.autochooser.com/results.asp [name of an arbitrarily supplied request parameter] next

Summary

Severity:	High
Confidence:	Certain
Host:	http://boston30.autochooser.com
Path:	/results.asp

Issue detail

The name of an arbitrarily supplied request parameter is copied into a JavaScript expression which is not encapsulated in any quotation marks. The payload 5f3d4%3balert(1)//a14fd98b734 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 5f3d4;alert(1)//a14fd98b734 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 /results.asp?gid=0&pagename=dealersearch.asp&resulttype=2&postto=results.asp&5f3d4%3balert(1)//a14fd98b734=1 HTTP/1.1
Host: boston30.autochooser.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: Mon, 08 Nov 2010 07:11:25 GMT
Server: Microsoft-IIS/6.0
P3P: CP="NON DSP COR CURa ADMa DEVa TAIa OUR SAMa IND", POLICYREF="URI"
Content-Type: text/html
Expires: Sun, 07 Nov 2010 07:10:24 GMT
Set-Cookie: cid=4340546; expires=Tue, 25-Dec-2012 05:00:00 GMT; path=/
Set-Cookie: ASPSESSIONIDCCBTSBBD=BJLBOFDCOGEEEJMKKEADHGCE; path=/
Cache-control: private
Content-Length: 76429

<HTML>
<HEAD>
<TITLE>Quick Search</TITLE>
<META NAME="ROBOTS" CONTENT="NOFOLLOW">
<script language="JavaScript">

...[SNIP]...

1.2. http://boston30.autochooser.com/results.asp [pagename parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://boston30.autochooser.com
Path:	/results.asp

Issue detail

The value of the pagename request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 34353'%3balert(1)//1b8759b2bca was submitted in the pagename parameter. This input was echoed as 34353';alert(1)//1b8759b2bca 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 /results.asp?gid=0&pagename=dealersearch.asp34353'%3balert(1)//1b8759b2bca&resulttype=2&postto=results.asp HTTP/1.1
Host: boston30.autochooser.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: Mon, 08 Nov 2010 07:10:21 GMT
Server: Microsoft-IIS/6.0
P3P: CP="NON DSP COR CURa ADMa DEVa TAIa OUR SAMa IND", POLICYREF="URI"
Content-Type: text/html
Expires: Sun, 07 Nov 2010 07:09:20 GMT
Set-Cookie: cid=4340409; expires=Tue, 25-Dec-2012 05:00:00 GMT; path=/
Set-Cookie: ASPSESSIONIDCCBTSBBD=JALBOFDCDIKJGLPNBNKLILCE; path=/
Cache-control: private
Content-Length: 76012

<HTML>
<HEAD>
<TITLE>Quick Search</TITLE>
<META NAME="ROBOTS" CONTENT="NOFOLLOW">
<script language="JavaScript">

...[SNIP]...

1.3. http://boston30.autochooser.com/results.asp [postto parameter] previous

Summary

Severity:	High
Confidence:	Certain
Host:	http://boston30.autochooser.com
Path:	/results.asp

Issue detail

The value of the postto request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload c2bff'%3balert(1)//c33d976c4f0 was submitted in the postto parameter. This input was echoed as c2bff';alert(1)//c33d976c4f0 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 /results.asp?gid=0&pagename=dealersearch.asp&resulttype=2&postto=results.aspc2bff'%3balert(1)//c33d976c4f0 HTTP/1.1
Host: boston30.autochooser.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: Mon, 08 Nov 2010 07:10:59 GMT
Server: Microsoft-IIS/6.0
P3P: CP="NON DSP COR CURa ADMa DEVa TAIa OUR SAMa IND", POLICYREF="URI"
Content-Type: text/html
Expires: Sun, 07 Nov 2010 07:09:59 GMT
Set-Cookie: cid=4340496; expires=Tue, 25-Dec-2012 05:00:00 GMT; path=/
Set-Cookie: ASPSESSIONIDCCBTSBBD=AGLBOFDCPDAMDONMBIPOONLO; path=/
Cache-control: private
Content-Length: 76012

<HTML>
<HEAD>
<TITLE>Quick Search</TITLE>
<META NAME="ROBOTS" CONTENT="NOFOLLOW">
<script language="JavaScript">

...[SNIP]...

2. Cookie without HttpOnly flag set previous next

Summary

Severity:	Low
Confidence:	Firm
Host:	http://boston30.autochooser.com
Path:	/results.asp

Issue detail

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

ASPSESSIONIDCCBTSBBD=GMKBOFDCFJPGPHGCEPILBDHP; path=/
cid=4340341; expires=Tue, 25-Dec-2012 05:00:00 GMT; path=/

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.

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 /results.asp?gid=0&pagename=dealersearch.asp&resulttype=2&postto=results.asp HTTP/1.1
Host: boston30.autochooser.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

3. Cross-domain Referer leakage previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://boston30.autochooser.com
Path:	/results.asp

Issue detail

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

http://boston30.autochooser.com/results.asp?gid=0&pagename=dealersearch.asp&resulttype=2&postto=results.asp

The response contains the following links to other domains:

http://www.bostonherald.com/images/1x1.gif
http://www.bostonherald.com/navigation/hiasysMJX.js
http://www.carfind.com/
http://www.carfind.com/dealerSearch/dealerRequest.bg
http://www.carfind.com/dealerSpecials/
http://www.carfind.com/images/gas120x120.gif
http://www.carfind.com/images/top1.gif
http://www.carfind.com/images/top2.gif
http://www.carfind.com/images/top3.gif
http://www.carfind.com/images/top4.gif
http://www.carfind.com/navigation/style.css
http://www.carfind.com/news/
http://www.carfind.com/searchOther.bg
http://www.carfind.com/sellCar.bg
http://www.google-analytics.com/urchin.js
http://www.hiasys.com/
http://www.hiasys.com/pc.html
http://www.homefind.com/
http://www.homefind.com/include/bgNavEng2.js
http://www.jobfind.com/

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: Mon, 08 Nov 2010 07:09:43 GMT
Server: Microsoft-IIS/6.0
P3P: CP="NON DSP COR CURa ADMa DEVa TAIa OUR SAMa IND", POLICYREF="URI"
Content-Type: text/html
Expires: Sun, 07 Nov 2010 07:08:42 GMT
Set-Cookie: cid=4340341; expires=Tue, 25-Dec-2012 05:00:00 GMT; path=/
Set-Cookie: ASPSESSIONIDCCBTSBBD=GMKBOFDCFJPGPHGCEPILBDHP; path=/
Cache-control: private
Content-Length: 74164

<HTML>
<HEAD>
<TITLE>Quick Search</TITLE>
<META NAME="ROBOTS" CONTENT="NOFOLLOW">
<script language="JavaScript">
<!--

   function saveFavorites() {
       if (document.results) {
           document.resu
...[SNIP]...
</SCRIPT>

<link rel=stylesheet type="text/css" href="http://www.carfind.com/navigation/style.css">

<script src="http://www.bostonherald.com/navigation/hiasysMJX.js" LANGUAGE="JavaScript1.1" TYPE="text/javascript"></script>
...[SNIP]...
</style>
<script src="http://www.homefind.com/include/bgNavEng2.js" language="JavaScript1.1" type="text/javascript" ></script>
...[SNIP]...
<td><a href=http://www.carfind.com><img border="0" src="http://www.carfind.com/images/top1.gif" width="269" height="77"></a>
...[SNIP]...
<td colspan="2" bgcolor="#996633"><img border="0" src="http://www.carfind.com/images/top2.gif" width="269" height="19"></td></tr><tr>
<td colspan="2" bgcolor="#FFFFFF"><img border="0" src="http://www.carfind.com/images/top3.gif" width="268" height="1"></td>
...[SNIP]...
<td width="48"><img border="0" src="http://www.carfind.com/images/top4.gif" width="48" height="20"></td>
...[SNIP]...
<td class=whiteCell width=1><img src=http://www.bostonherald.com/images/1x1.gif width="1" height="1"></td>
...[SNIP]...
<td align=center bgcolor="#EA8C00" onMouseOver="mOverNav(this,'sell a car','ho')" onMouseOut="mOutNav(this,'','ho')"><a href=http://www.carfind.com/sellCar.bg target=_top><font class=button2font color=#FFFFFF>
...[SNIP]...
<td align=center bgcolor="#EA8C00" onMouseOver="mOverNav(this,'other','hf')" onMouseOut="mOutNav(this,'','so')"><a href=http://www.carfind.com/searchOther.bg target=_top><font class=button2font color=#FFFFFF>
...[SNIP]...
<td align=center bgcolor="#EA8C00" onMouseOver="mOverNav(this,'news & reviews','hf')" onMouseOut="mOutNav(this,'','sr')"><a href=http://www.carfind.com/news/ target=_top><font class=button2font color=#FFFFFF>
...[SNIP]...
<td align=center bgcolor="#EA8C00" onMouseOver="mOverNav(this,'dealer specials','hf')" onMouseOut="mOutNav(this,'','sr')"><a href=http://www.carfind.com/dealerSpecials/ target=_top><font class=button2font color=#FFFFFF>
...[SNIP]...
<td align=center bgcolor="#C5AF7D" onMouseOver="mOverNav2(this,'for dealers','hf')" onMouseOut="mOutNav2(this,'','sk')"><a href=http://www.carfind.com/dealerSearch/dealerRequest.bg target=_top><font class=button2font color=#FFFFFF>
...[SNIP]...
<br>
<a href=http://www.carfind.com/dealerSpecials/><img src=http://www.carfind.com/images/gas120x120.gif border=0></a>
...[SNIP]...
<b><a href=http://www.carfind.com/dealerSearch/dealerRequest.bg><font color=#CC6600>
...[SNIP]...
</font><a href="http://www.carfind.com/"><font color="#CC6600">
...[SNIP]...
</font><a href="http://www.carfind.com/sellCar.bg"><font color="#CC6600">
...[SNIP]...
</font><a href="http://www.carfind.com"><font color="#CC6600">
...[SNIP]...
</font><a href="http://www.jobfind.com" target="_new"><font color="#CC6600">
...[SNIP]...
</font><a href="http://www.homefind.com"><font color="#CC6600">
...[SNIP]...
<font class="storyFont"><a href="http://www.hiasys.com" target="_blank"><font color="#c0c0c0">
...[SNIP]...
<font class="storyFont"><a href="http://www.hiasys.com/pc.html"><font color="#c0c0c0">
...[SNIP]...
</table>

<script src="http://www.google-analytics.com/urchin.js" type="text/javascript">
</script>
...[SNIP]...

4. Cross-domain script include previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://boston30.autochooser.com
Path:	/results.asp

Issue detail

The response dynamically includes the following scripts from other domains:

http://www.bostonherald.com/navigation/hiasysMJX.js
http://www.google-analytics.com/urchin.js
http://www.homefind.com/include/bgNavEng2.js

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

Response

5. Email addresses disclosed previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://boston30.autochooser.com
Path:	/results.asp

Issue detail

The following email address was disclosed in the response:

carfind@carfind.com

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

Request

Response

6. HTML does not specify charset previous

Summary

Severity:	Information
Confidence:	Certain
Host:	http://boston30.autochooser.com
Path:	/results.asp

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

Report generated by XSS.CX at Mon Nov 08 09:37:46 CST 2010.