The value of the url request parameter is copied into the HTML document as plain text between tags. The payload 9ee5e<script>alert(1)</script>a73b3542d36 was submitted in the url parameter. This input was echoed unmodified in the application's response.
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.
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.
HTTP/1.1 200 OK Date: Sun, 20 Mar 2011 17:29:34 GMT Server: Apache Vary: Accept-Encoding Content-Type: text/html Content-Length: 1155
<html> <head> <title>Check PageRank For Your Website</title> <meta name="description" content="Checks PageRank for any given website or URL. This PageRank Checker is part of Techie Buzz tool ...[SNIP]... <b style="font-family:Verdana;font-size:11px">Page Rank for http://xss.cx/9ee5e<script>alert(1)</script>a73b3542d36 is 0 <img src="http://pagerank.techie-buzz.com/images/page-rank-0.gif" border="0" /> ...[SNIP]...
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.
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.
GET /pagerankfetcher.php?url=http%3A//techie-buzz.com/softwares/how-to-check-pagerank-in-google-chrome.html HTTP/1.1 Host: pagerank.techie-buzz.com Proxy-Connection: keep-alive Referer: http://techie-buzz.com/softwares/how-to-check-pagerank-in-google-chrome.html User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 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: __utmz=116550147.1300641665.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __gads=ID=2091f9732c90cb51:T=1300641645:S=ALNI_MaM2hAe-lnXOkhykaiFrDAf_1V6kg; __qca=P0-671913769-1300641673847; __utma=116550147.26217198.1300641665.1300641665.1300641665.1; __utmc=116550147; __utmb=11655018.104.22.1680641675933
HTTP/1.1 200 OK Date: Sun, 20 Mar 2011 17:25:56 GMT Server: Apache Vary: Accept-Encoding Content-Type: text/html Content-Length: 1050
<html> <head> <title>Check PageRank For Your Website</title> <meta name="description" content="Checks PageRank for any given website or URL. This PageRank Checker is part of Techie Buzz tool ...[SNIP]...
Report generated by XSS.CX at Sun Mar 20 15:09:07 CDT 2011.