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 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.
1.1. http://www.ritzcarlton.com/en/prm/BOSRT/Properties/Request/Default.htm [name of an arbitrarily supplied request parameter]next
Summary
Severity:
High
Confidence:
Firm
Host:
http://www.ritzcarlton.com
Path:
/en/prm/BOSRT/Properties/Request/Default.htm
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 43290"%3b3520bf059aa was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 43290";3520bf059aa in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. 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.
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.
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 /en/prm/BOSRT/Properties/Request/Default.htm?43290"%3b3520bf059aa=1 HTTP/1.1 Host: www.ritzcarlton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response (redirected)
HTTP/1.1 200 OK Connection: close Date: Tue, 26 Oct 2010 04:02:55 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: public, max-age=3600 Expires: Tue, 26 Oct 2010 05:02:54 GMT Last-Modified: Tue, 26 Oct 2010 04:02:54 GMT Vary: * Content-Type: text/html; charset=utf-8 Content-Length: 108348
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html lang="en"> <head> <script language='javascript' type='text/javascript'> <!-- try{if(window.location.protocol!="http:"){window.location.replace("http://www.ritzcarlton.com/en/Properties/BostonCommon/Default.htm?43290";3520bf059aa=1");}}catch(rerr){} //--> ...[SNIP]...
1.2. http://www.ritzcarlton.com/en/prm/BOSRT/Meetings/Request/Default.htm [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
Information
Confidence:
Firm
Host:
http://www.ritzcarlton.com
Path:
/en/prm/BOSRT/Meetings/Request/Default.htm
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 53a17'%3b1d7996f2a38 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 53a17';1d7996f2a38 in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. 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.
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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. 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.
Request
GET /en/prm/BOSRT/Meetings/Request/Default.htm?53a17'%3b1d7996f2a38=1 HTTP/1.1 Host: www.ritzcarlton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response (redirected)
HTTP/1.1 302 Found Connection: close Date: Tue, 26 Oct 2010 04:06:07 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Location: https://www.ritzcarlton.com/en/Properties/BostonCommon/Meetings/Request/Default.htm?53a17';1d7996f2a38=1 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 414
<html><head><title>Object moved</title></head><body> <h2>Object moved to <a href="https://www.ritzcarlton.com/en/Properties/BostonCommon/Meetings/Request/Default.htm?53a17';1d7996f2a38=1">here</a>.</ ...[SNIP]... <script language='javascript' type='text/javascript'>window.location.replace('https://www.ritzcarlton.com/en/Properties/BostonCommon/Meetings/Request/Default.htm?53a17';1d7996f2a38=1';</script>
1.3. http://www.ritzcarlton.com/en/prm/BOSRT/Reservations/Default.htm [name of an arbitrarily supplied request parameter]previous
Summary
Severity:
Information
Confidence:
Firm
Host:
http://www.ritzcarlton.com
Path:
/en/prm/BOSRT/Reservations/Default.htm
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 e2516'%3bc842e40fb71 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as e2516';c842e40fb71 in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. 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.
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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. 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.
Request
GET /en/prm/BOSRT/Reservations/Default.htm?e2516'%3bc842e40fb71=1 HTTP/1.1 Host: www.ritzcarlton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response (redirected)
HTTP/1.1 302 Found Connection: close Date: Tue, 26 Oct 2010 04:05:53 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Location: https://www.ritzcarlton.com/en/Properties/BostonCommon/Reservations/Default.htm?e2516';c842e40fb71=1 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 406
<html><head><title>Object moved</title></head><body> <h2>Object moved to <a href="https://www.ritzcarlton.com/en/Properties/BostonCommon/Reservations/Default.htm?e2516';c842e40fb71=1">here</a>.</h2> ...[SNIP]... <script language='javascript' type='text/javascript'>window.location.replace('https://www.ritzcarlton.com/en/Properties/BostonCommon/Reservations/Default.htm?e2516';c842e40fb71=1';</script>
Report generated by XSS.CX at Sat Nov 13 20:06:31 CST 2010.