The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload b7cb2<img%20src%3da%20onerror%3dalert(1)>47441f6f55e was submitted in the REST URL parameter 2. This input was echoed as b7cb2<img src=a onerror=alert(1)>47441f6f55e 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.
Issue background
Reflected cross-site scripting vulnerabilities arise when data is copied from a request and echoed into the application's immediate response in an unsafe way. An attacker can use the vulnerability to construct a request which, if issued by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application.
The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes.
Users can be induced to issue the attacker's crafted request in various ways. For example, the attacker can send a victim a link containing a malicious URL in an email or instant message. They can submit the link to popular web sites that allow content authoring, for example in blog comments. And they can create an innocuous looking web site which causes anyone viewing it to make arbitrary cross-domain requests to the vulnerable application (using either the GET or the POST method).
The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality which it contains, and the other applications which belong to the same domain and organisation. If the application is used only to display non-sensitive public content, with no authentication or access control functionality, then a cross-site scripting flaw may be considered low risk. However, if the same application resides on a domain which can access cookies for other more security-critical applications, then the vulnerability could be used to attack those other applications, and so may be considered high risk. Similarly, if the organisation which owns the application is a likely target for phishing attacks, then the vulnerability could be leveraged to lend credibility to such attacks, by injecting Trojan functionality into the vulnerable application, and exploiting users' trust in the organisation in order to capture credentials for other applications which it owns. In many kinds of application, such as those providing online banking functionality, cross-site scripting should always be considered high risk.
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 defenses:
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.
Request
GET /click-to-verify/www.removeyourcontent.comb7cb2<img%20src%3da%20onerror%3dalert(1)>47441f6f55e HTTP/1.1 Host: privacy-policy.truste.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=165058976.1293269944.4.4.utmcsr=burp|utmccn=(referral)|utmcmd=referral|utmcct=/show/0; __utma=165058976.735451753.1291511057.1292174012.1293269944.4;
Response
HTTP/1.1 200 OK Cache-Control: must-revalidate, no-cache, no-store Content-Type: text/html Date: Thu, 30 Dec 2010 07:03:23 GMT Server: TRUSTe Set-Cookie: JSESSIONID=A6FC2FDC45E1483DCE61479B14D4E012; Path=/ Content-Length: 2979 Connection: close
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>Verification ...[SNIP]... <div style="font-size: 14px; color: #333; margin-top: 22px">Site www.removeyourcontent.comb7cb2<img src=a onerror=alert(1)>47441f6f55e is either not participating in or is not in compliance with the requirements of TRUSTe verification services. </div> ...[SNIP]...
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.
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 /click-to-verify/a HTTP/1.1 Host: privacy-policy.truste.com Proxy-Connection: keep-alive Referer: http://privacy-policy.truste.com/click-to-verify/www.removeyourcontent.comb7cb2%3Cimg%20src%3da%20onerror%3dalert(document.cookie)%3E47441f6f55e Accept: */* User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10 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=165058976.1293269944.4.4.utmcsr=burp|utmccn=(referral)|utmcmd=referral|utmcct=/show/0; __utma=165058976.735451753.1291511057.1293269944.1293727620.5; __utmc=165058976; __utmb=165058976.5.10.1293727620; JSESSIONID=D7206DA8C5C36EF46F557856A8ECADC2
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).
The following email address was disclosed in the response:
tss-sales@truste.com
Request
GET /click-to-verify/www.removeyourcontent.com HTTP/1.1 Host: privacy-policy.truste.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=165058976.1293269944.4.4.utmcsr=burp|utmccn=(referral)|utmcmd=referral|utmcct=/show/0; __utma=165058976.735451753.1291511057.1292174012.1293269944.4;
Response
HTTP/1.1 200 OK Accept-Ranges: bytes Cache-Control: must-revalidate, no-cache, no-store Content-Type: text/html Date: Thu, 30 Dec 2010 07:03:20 GMT Last-Modified: Thu, 30 Dec 2010 06:44:09 GMT Server: ECAcc (dfw/5660) X-Cache: HIT Content-Length: 10923 Connection: close
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.
GET /click-to-verify/www.removeyourcontent.com HTTP/1.1 Host: privacy-policy.truste.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmz=165058976.1293269944.4.4.utmcsr=burp|utmccn=(referral)|utmcmd=referral|utmcct=/show/0; __utma=165058976.735451753.1291511057.1292174012.1293269944.4;
Response
HTTP/1.1 200 OK Accept-Ranges: bytes Cache-Control: must-revalidate, no-cache, no-store Content-Type: text/html Date: Thu, 30 Dec 2010 07:03:20 GMT Last-Modified: Thu, 30 Dec 2010 06:44:09 GMT Server: ECAcc (dfw/5660) X-Cache: HIT Content-Length: 10923 Connection: close
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>Verificat ...[SNIP]...
Report generated by XSS.CX at Thu Dec 30 19:28:07 CST 2010.