secure.hilton.com, XSS, CAPEC-86, CWE-79, Cross Site Scripting

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. https://secure.hilton.com/en/hi/res/choose_dates.jhtml [jsessionid parameter] next

Summary

Severity:	High
Confidence:	Certain
Host:	https://secure.hilton.com
Path:	/en/hi/res/choose_dates.jhtml

Issue detail

The value of the jsessionid request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload a1e40'-alert(1)-'d825ace36f8 was submitted in the jsessionid 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.

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/hi/res/choose_dates.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?_requestid=285735a1e40'-alert(1)-'d825ace36f8 HTTP/1.1
Host: secure.hilton.com
Connection: keep-alive
Referer: http://www1.hilton.com/en_US/hi/hotel/BOSFDHF-Hilton-Boston-Financial-District-Massachusetts/index.do;jsessionid=0ABC42E492304CBBBCE5486E110ECEB6.etc32?brand_id=HI&brand_directory=/en/hi/&xch=826093977,Q3LJIA5WFPFVGCSGBI1MVCQ
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.94 Safari/534.13
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: K3R7=3LJJ3QmEbCVHlmRdtFSbSwjmojI708sDnghZi0w-UFdVcbdJvAs_yWQ; ClrOSSID=1297389156812-9086; ClrSCD=1297389156812; JSESSIONID=Q3LJIA5WFPFVGCSGBI1MVCQ; cross-sell=hi; ClrCSTO=T; mmcore.tst=0.451; mmid=1891688497%7CBQAAAAqUFIqT3gUAAA%3D%3D; mmcore.pd=1891688497%7CBQAAAAqUFIqT3gUAAA%3D%3D; mmcore.srv=cg1.use; ClrSSID=1297389156812-9086; WT_FPC=id=173.193.214.243-2605364368.30126492:lv=1297382461468:ss=1297381960185

Response

1.2. https://secure.hilton.com/en/hi/res/choose_dates.jhtml [jsessionid parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	https://secure.hilton.com
Path:	/en/hi/res/choose_dates.jhtml

Issue detail

The value of the jsessionid request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload fb8c8"><script>alert(1)</script>0fc3a537c4d was submitted in the jsessionid 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 /en/hi/res/choose_dates.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?_requestid=285735fb8c8"><script>alert(1)</script>0fc3a537c4d HTTP/1.1
Host: secure.hilton.com
Connection: keep-alive
Referer: http://www1.hilton.com/en_US/hi/hotel/BOSFDHF-Hilton-Boston-Financial-District-Massachusetts/index.do;jsessionid=0ABC42E492304CBBBCE5486E110ECEB6.etc32?brand_id=HI&brand_directory=/en/hi/&xch=826093977,Q3LJIA5WFPFVGCSGBI1MVCQ
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.94 Safari/534.13
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: K3R7=3LJJ3QmEbCVHlmRdtFSbSwjmojI708sDnghZi0w-UFdVcbdJvAs_yWQ; ClrOSSID=1297389156812-9086; ClrSCD=1297389156812; JSESSIONID=Q3LJIA5WFPFVGCSGBI1MVCQ; cross-sell=hi; ClrCSTO=T; mmcore.tst=0.451; mmid=1891688497%7CBQAAAAqUFIqT3gUAAA%3D%3D; mmcore.pd=1891688497%7CBQAAAAqUFIqT3gUAAA%3D%3D; mmcore.srv=cg1.use; ClrSSID=1297389156812-9086; WT_FPC=id=173.193.214.243-2605364368.30126492:lv=1297382461468:ss=1297381960185

Response

1.3. https://secure.hilton.com/en/hi/res/choose_dates.jhtml [name of an arbitrarily supplied request parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	https://secure.hilton.com
Path:	/en/hi/res/choose_dates.jhtml

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 13627'-alert(1)-'f3fc660993d 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.

Remediation detail

Request

GET /en/hi/res/choose_dates.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?_requestid=285735&13627'-alert(1)-'f3fc660993d=1 HTTP/1.1
Host: secure.hilton.com
Connection: keep-alive
Referer: http://www1.hilton.com/en_US/hi/hotel/BOSFDHF-Hilton-Boston-Financial-District-Massachusetts/index.do;jsessionid=0ABC42E492304CBBBCE5486E110ECEB6.etc32?brand_id=HI&brand_directory=/en/hi/&xch=826093977,Q3LJIA5WFPFVGCSGBI1MVCQ
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.94 Safari/534.13
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: K3R7=3LJJ3QmEbCVHlmRdtFSbSwjmojI708sDnghZi0w-UFdVcbdJvAs_yWQ; ClrOSSID=1297389156812-9086; ClrSCD=1297389156812; JSESSIONID=Q3LJIA5WFPFVGCSGBI1MVCQ; cross-sell=hi; ClrCSTO=T; mmcore.tst=0.451; mmid=1891688497%7CBQAAAAqUFIqT3gUAAA%3D%3D; mmcore.pd=1891688497%7CBQAAAAqUFIqT3gUAAA%3D%3D; mmcore.srv=cg1.use; ClrSSID=1297389156812-9086; WT_FPC=id=173.193.214.243-2605364368.30126492:lv=1297382461468:ss=1297381960185

Response

1.4. https://secure.hilton.com/en/hi/res/choose_dates.jhtml [name of an arbitrarily supplied request parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	https://secure.hilton.com
Path:	/en/hi/res/choose_dates.jhtml

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 86abc"><script>alert(1)</script>125a40cedac 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 /en/hi/res/choose_dates.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?_requestid=285735&86abc"><script>alert(1)</script>125a40cedac=1 HTTP/1.1
Host: secure.hilton.com
Connection: keep-alive
Referer: http://www1.hilton.com/en_US/hi/hotel/BOSFDHF-Hilton-Boston-Financial-District-Massachusetts/index.do;jsessionid=0ABC42E492304CBBBCE5486E110ECEB6.etc32?brand_id=HI&brand_directory=/en/hi/&xch=826093977,Q3LJIA5WFPFVGCSGBI1MVCQ
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.94 Safari/534.13
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: K3R7=3LJJ3QmEbCVHlmRdtFSbSwjmojI708sDnghZi0w-UFdVcbdJvAs_yWQ; ClrOSSID=1297389156812-9086; ClrSCD=1297389156812; JSESSIONID=Q3LJIA5WFPFVGCSGBI1MVCQ; cross-sell=hi; ClrCSTO=T; mmcore.tst=0.451; mmid=1891688497%7CBQAAAAqUFIqT3gUAAA%3D%3D; mmcore.pd=1891688497%7CBQAAAAqUFIqT3gUAAA%3D%3D; mmcore.srv=cg1.use; ClrSSID=1297389156812-9086; WT_FPC=id=173.193.214.243-2605364368.30126492:lv=1297382461468:ss=1297381960185

Response

2. SSL cookie without secure flag set previous next

Summary

Severity:	Medium
Confidence:	Firm
Host:	https://secure.hilton.com
Path:	/en/hi/signup/create_account.jhtml

Issue detail

The following cookie was issued by the application and does not have the secure flag set:

JSESSIONID=Q3LJIA5WFPFVGCSGBI1MVCQ; path=/

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 secure flag is set on a cookie, then browsers will not submit the cookie in any requests that use an unencrypted HTTP connection, thereby preventing the cookie from being trivially intercepted by an attacker monitoring network traffic. If the secure flag is not set, then the cookie will be transmitted in clear-text if the user visits any HTTP URLs within the cookie's scope. An attacker may be able to induce this event by feeding a user suitable links, either directly or via another web site. Even if the domain which issued the cookie does not host any content that is accessed over HTTP, an attacker may be able to use links of the form http://example.com:443/ to perform the same attack.

Issue remediation

The secure flag should be set on all cookies that are used for transmitting sensitive data when accessing content over HTTPS. If cookies are used to transmit session tokens, then areas of the application that are accessed over HTTPS should employ their own session handling mechanism, and the session tokens used should never be transmitted over unencrypted communications.

Request

GET /en/hi/signup/create_account.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ HTTP/1.1
Host: secure.hilton.com
Connection: keep-alive
Referer: http://www1.hilton.com/en_US/hi/index.do
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.94 Safari/534.13
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: cross-sell=hi; mmcore.tst=0.532; K3R7=3LJJ3QmEbCVHlmRdtFSbSwjmojI708sDnghZi0w-UFdVcbdJvAs_yWQ; mmid=1193586808%7CAQAAAAqUFIqT3gUAAA%3D%3D; mmcore.pd=1193586808%7CAQAAAAqUFIqT3gUAAA%3D%3D; mmcore.srv=cg1.use; ClrCSTO=T; ClrSSID=1297389156812-9086; ClrOSSID=1297389156812-9086; ClrSCD=1297389156812; WT_FPC=id=173.193.214.243-2605364368.30126492:lv=1297381960185:ss=1297381960185

Response

3. Session token in URL previous next
There are 17 instances of this issue:

/en/common/js/cart.js
/en/common/js/common.js
/en/common/js/footer.js
/en/common/js/popup.js
/en/common/webtrends/wtbaseHilton.js
/en/common/webtrends/wtinit.js
/en/hi/login/reward_login.jhtml
/en/hi/login/reward_login.jhtml
/en/hi/res/choose_dates.jhtml
/en/hi/res/choose_dates.jhtml
/en/hi/res/choose_rates.jhtml
/en/hi/res/choose_rates.jhtml
/en/hi/res/your_information.jhtml
/en/hi/signup/create_account.jhtml
/en/hi/signup/create_account.jhtml
/en/hi/signup/reservation_profile.jhtml
/en/hi/signup/reservation_profile.jhtml

Issue background

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.

3.1. https://secure.hilton.com/en/common/js/cart.js previous next

Summary

Severity:	Medium
Confidence:	Firm
Host:	https://secure.hilton.com
Path:	/en/common/js/cart.js

Issue detail

The URL in the request appears to contain a session token within the query string:

https://secure.hilton.com/en/common/js/cart.js;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ

Request

GET /en/common/js/cart.js;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ HTTP/1.1
Host: secure.hilton.com
Connection: keep-alive
Referer: https://secure.hilton.com/en/hi/signup/create_account.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.94 Safari/534.13
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: cross-sell=hi; mmcore.tst=0.532; K3R7=3LJJ3QmEbCVHlmRdtFSbSwjmojI708sDnghZi0w-UFdVcbdJvAs_yWQ; mmid=1193586808%7CAQAAAAqUFIqT3gUAAA%3D%3D; mmcore.pd=1193586808%7CAQAAAAqUFIqT3gUAAA%3D%3D; mmcore.srv=cg1.use; ClrCSTO=T; ClrSSID=1297389156812-9086; ClrOSSID=1297389156812-9086; ClrSCD=1297389156812; WT_FPC=id=173.193.214.243-2605364368.30126492:lv=1297381960185:ss=1297381960185; JSESSIONID=Q3LJIA5WFPFVGCSGBI1MVCQ

Response

HTTP/1.1 200 OK
Server: Netscape-Enterprise/6.0
Content-Length: 6482
Content-Type: application/x-javascript
ETag: "9eb7dd67-1-0-1952"
Last-Modified: Wed, 11 Oct 2006 19:30:20 GMT
Accept-Ranges: bytes
Cache-Control: max-age=604777
Expires: Fri, 18 Feb 2011 01:51:07 GMT
Date: Fri, 11 Feb 2011 01:51:30 GMT
Connection: keep-alive

// preload images
var cart_icon_0 = new Image();
var cart_icon_1 = new Image();
cart_icon_0.src = "/en/common/media/images/icons/icon_cart_off.gif";
cart_icon_1.src = "/en/common/media/images/icons/ic
...[SNIP]...

3.2. https://secure.hilton.com/en/common/js/common.js previous next

Summary

Severity:	Medium
Confidence:	Firm
Host:	https://secure.hilton.com
Path:	/en/common/js/common.js

Issue detail

The URL in the request appears to contain a session token within the query string:

https://secure.hilton.com/en/common/js/common.js;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ

Request

GET /en/common/js/common.js;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ HTTP/1.1
Host: secure.hilton.com
Connection: keep-alive
Referer: https://secure.hilton.com/en/hi/signup/create_account.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.94 Safari/534.13
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: cross-sell=hi; mmcore.tst=0.532; K3R7=3LJJ3QmEbCVHlmRdtFSbSwjmojI708sDnghZi0w-UFdVcbdJvAs_yWQ; mmid=1193586808%7CAQAAAAqUFIqT3gUAAA%3D%3D; mmcore.pd=1193586808%7CAQAAAAqUFIqT3gUAAA%3D%3D; mmcore.srv=cg1.use; ClrCSTO=T; ClrSSID=1297389156812-9086; ClrOSSID=1297389156812-9086; ClrSCD=1297389156812; WT_FPC=id=173.193.214.243-2605364368.30126492:lv=1297381960185:ss=1297381960185; JSESSIONID=Q3LJIA5WFPFVGCSGBI1MVCQ

Response

HTTP/1.1 200 OK
Server: Netscape-Enterprise/6.0
Content-Length: 678
Content-Type: application/x-javascript
ETag: "8b207e26-1-0-2a6"
Last-Modified: Mon, 28 Jun 2010 05:29:59 GMT
Accept-Ranges: bytes
Cache-Control: max-age=604759
Expires: Fri, 18 Feb 2011 01:50:49 GMT
Date: Fri, 11 Feb 2011 01:51:30 GMT
Connection: keep-alive

// globals #######################################
ie = document.all ? true : false;
dom = document.getElementById ? true : false;
ns = document.layers ? true : false;
// #############################
...[SNIP]...

3.3. https://secure.hilton.com/en/common/js/footer.js previous next

Summary

Severity:	Medium
Confidence:	Firm
Host:	https://secure.hilton.com
Path:	/en/common/js/footer.js

Issue detail

The URL in the request appears to contain a session token within the query string:

https://secure.hilton.com/en/common/js/footer.js;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ

Request

GET /en/common/js/footer.js;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ HTTP/1.1
Host: secure.hilton.com
Connection: keep-alive
Referer: https://secure.hilton.com/en/hi/signup/create_account.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.94 Safari/534.13
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: cross-sell=hi; mmcore.tst=0.532; K3R7=3LJJ3QmEbCVHlmRdtFSbSwjmojI708sDnghZi0w-UFdVcbdJvAs_yWQ; mmid=1193586808%7CAQAAAAqUFIqT3gUAAA%3D%3D; mmcore.pd=1193586808%7CAQAAAAqUFIqT3gUAAA%3D%3D; mmcore.srv=cg1.use; ClrCSTO=T; ClrSSID=1297389156812-9086; ClrOSSID=1297389156812-9086; ClrSCD=1297389156812; WT_FPC=id=173.193.214.243-2605364368.30126492:lv=1297381960185:ss=1297381960185; JSESSIONID=Q3LJIA5WFPFVGCSGBI1MVCQ

Response

HTTP/1.1 200 OK
Server: Netscape-Enterprise/6.0
Content-Length: 786
Content-Type: application/x-javascript
ETag: "922ba38c-1-0-312"
Last-Modified: Thu, 09 Sep 2004 01:33:53 GMT
Accept-Ranges: bytes
Cache-Control: max-age=604795
Expires: Fri, 18 Feb 2011 01:51:27 GMT
Date: Fri, 11 Feb 2011 01:51:32 GMT
Connection: keep-alive

var to = false;
var flag = false;
function layerVis(id,dir) {
if (document.layers) {
v = (dir == "on") ? "show" : "hide";
//document.layers[id].visibility = v;
}
else if (d
...[SNIP]...

3.4. https://secure.hilton.com/en/common/js/popup.js previous next

Summary

Severity:	Medium
Confidence:	Firm
Host:	https://secure.hilton.com
Path:	/en/common/js/popup.js

Issue detail

The URL in the request appears to contain a session token within the query string:

https://secure.hilton.com/en/common/js/popup.js;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ

Request

GET /en/common/js/popup.js;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ HTTP/1.1
Host: secure.hilton.com
Connection: keep-alive
Referer: https://secure.hilton.com/en/hi/signup/create_account.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.94 Safari/534.13
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: cross-sell=hi; mmcore.tst=0.532; K3R7=3LJJ3QmEbCVHlmRdtFSbSwjmojI708sDnghZi0w-UFdVcbdJvAs_yWQ; mmid=1193586808%7CAQAAAAqUFIqT3gUAAA%3D%3D; mmcore.pd=1193586808%7CAQAAAAqUFIqT3gUAAA%3D%3D; mmcore.srv=cg1.use; ClrCSTO=T; ClrSSID=1297389156812-9086; ClrOSSID=1297389156812-9086; ClrSCD=1297389156812; WT_FPC=id=173.193.214.243-2605364368.30126492:lv=1297381960185:ss=1297381960185; JSESSIONID=Q3LJIA5WFPFVGCSGBI1MVCQ

Response

HTTP/1.1 200 OK
Server: Netscape-Enterprise/6.0
Content-Length: 1661
Content-Type: application/x-javascript
ETag: "a645a491-1-0-67d"
Last-Modified: Thu, 09 Sep 2004 01:33:53 GMT
Accept-Ranges: bytes
Cache-Control: max-age=604797
Expires: Fri, 18 Feb 2011 01:51:27 GMT
Date: Fri, 11 Feb 2011 01:51:30 GMT
Connection: keep-alive

function getWindowWidth() {
   winW = (ie) ? screen.width : window.outerWidth;
   return winW;
}

function getWindowHeight() {
   winH = (ie) ? screen.Availheight : window.outerHeight;
   return winH;
}

func
...[SNIP]...

3.5. https://secure.hilton.com/en/common/webtrends/wtbaseHilton.js previous next

Summary

Severity:	Medium
Confidence:	Firm
Host:	https://secure.hilton.com
Path:	/en/common/webtrends/wtbaseHilton.js

Issue detail

The URL in the request appears to contain a session token within the query string:

https://secure.hilton.com/en/common/webtrends/wtbaseHilton.js;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ

Request

GET /en/common/webtrends/wtbaseHilton.js;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ HTTP/1.1
Host: secure.hilton.com
Connection: keep-alive
Referer: https://secure.hilton.com/en/hi/signup/create_account.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.94 Safari/534.13
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: cross-sell=hi; mmcore.tst=0.532; K3R7=3LJJ3QmEbCVHlmRdtFSbSwjmojI708sDnghZi0w-UFdVcbdJvAs_yWQ; mmid=1193586808%7CAQAAAAqUFIqT3gUAAA%3D%3D; mmcore.pd=1193586808%7CAQAAAAqUFIqT3gUAAA%3D%3D; mmcore.srv=cg1.use; ClrCSTO=T; ClrSSID=1297389156812-9086; ClrOSSID=1297389156812-9086; ClrSCD=1297389156812; WT_FPC=id=173.193.214.243-2605364368.30126492:lv=1297381960185:ss=1297381960185; JSESSIONID=Q3LJIA5WFPFVGCSGBI1MVCQ

Response

HTTP/1.1 200 OK
Server: Netscape-Enterprise/6.0
Content-Length: 23653
Content-Type: application/x-javascript
ETag: "156f7922-5-0-5c65"
Last-Modified: Thu, 20 Jan 2011 09:22:33 GMT
Accept-Ranges: bytes
Cache-Control: max-age=604795
Expires: Fri, 18 Feb 2011 01:51:27 GMT
Date: Fri, 11 Feb 2011 01:51:32 GMT
Connection: keep-alive

// WebTrends SmartSource Data Collector Tag
// Version: 1.1.1
// Created: 2/13/2008 4:10:50 PM
// *******************************************************
// David Sinner 2/20/2008
// This tag was
...[SNIP]...

3.6. https://secure.hilton.com/en/common/webtrends/wtinit.js previous next

Summary

Severity:	Medium
Confidence:	Firm
Host:	https://secure.hilton.com
Path:	/en/common/webtrends/wtinit.js

Issue detail

The URL in the request appears to contain a session token within the query string:

https://secure.hilton.com/en/common/webtrends/wtinit.js;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ

Request

GET /en/common/webtrends/wtinit.js;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ HTTP/1.1
Host: secure.hilton.com
Connection: keep-alive
Referer: https://secure.hilton.com/en/hi/signup/create_account.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.94 Safari/534.13
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: cross-sell=hi; mmcore.tst=0.532; K3R7=3LJJ3QmEbCVHlmRdtFSbSwjmojI708sDnghZi0w-UFdVcbdJvAs_yWQ; mmid=1193586808%7CAQAAAAqUFIqT3gUAAA%3D%3D; mmcore.pd=1193586808%7CAQAAAAqUFIqT3gUAAA%3D%3D; mmcore.srv=cg1.use; ClrCSTO=T; ClrSSID=1297389156812-9086; ClrOSSID=1297389156812-9086; ClrSCD=1297389156812; WT_FPC=id=173.193.214.243-2605364368.30126492:lv=1297381960185:ss=1297381960185; JSESSIONID=Q3LJIA5WFPFVGCSGBI1MVCQ

Response

HTTP/1.1 200 OK
Server: Netscape-Enterprise/6.0
Content-Length: 1670
Content-Type: application/x-javascript
ETag: "9b903fed-1-0-686"
Last-Modified: Tue, 29 Jul 2008 18:10:44 GMT
Accept-Ranges: bytes
Cache-Control: max-age=604739
Expires: Fri, 18 Feb 2011 01:50:32 GMT
Date: Fri, 11 Feb 2011 01:51:33 GMT
Connection: keep-alive

// WebTrends SmartSource Data Collector Tag
// Version: 1.1.1
// Created: 2/13/2008 4:10:50 PM
// *******************************************************
// David Sinner 7/28/2008
// Added "javas
...[SNIP]...

3.7. https://secure.hilton.com/en/hi/login/reward_login.jhtml previous next

Summary

Severity:	Medium
Confidence:	Firm
Host:	https://secure.hilton.com
Path:	/en/hi/login/reward_login.jhtml

Issue detail

The response contains the following links that appear to contain session tokens:

https://secure.hilton.com/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/en/ch/home.do
https://secure.hilton.com/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/en_US/dt/index.do
https://secure.hilton.com/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/en_US/es/index.do
https://secure.hilton.com/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/en_US/gi/index.do
https://secure.hilton.com/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/en_US/hh/home_index.do
https://secure.hilton.com/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/en_US/hi/customersupport/index.do
https://secure.hilton.com/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/en_US/hi/customersupport/site-usage.do
https://secure.hilton.com/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/en_US/hi/index.do
https://secure.hilton.com/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/en_US/hi/sitemap/index.do
https://secure.hilton.com/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/en_US/hp/index.do
https://secure.hilton.com/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/en_US/ht/index.do
https://secure.hilton.com/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/en_US/hw/index.do
https://secure.hilton.com/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/en_US/ww/customersupport/privacy-policy.do
https://secure.hilton.com/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/es/hi/index.do
https://secure.hilton.com/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/fr/hi/index.do
https://secure.hilton.com/en/hi/cart/index.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ
https://secure.hilton.com/en/hi/ctg/index.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ
https://secure.hilton.com/en/hi/groups/index.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?eventType=Business
https://secure.hilton.com/en/hi/groups/index.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?eventType=Social&it=Tnav,GM
https://secure.hilton.com/en/hi/promotions/index.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ
https://secure.hilton.com/en/hi/reservations/index.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ

Request

GET /en/hi/login/reward_login.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?nextHandler=/com/hilton/res/client/handler/ChooseDatesProxyHandler&_requestid=288910 HTTP/1.1
Host: secure.hilton.com
Connection: keep-alive
Referer: http://www1.hilton.com/en_US/hi/hotel/BOSFDHF-Hilton-Boston-Financial-District-Massachusetts8b619%22%3E%3Cimg%20src%3da%20onerror%3dalert(document.cookie)%3E7fb045a4243/index.do;jsessionid=0ABC42E492304CBBBCE5486E110ECEB6.etc32?brand_id=HI&brand_directory=/en/hi/&xch=826093977,Q3LJIA5WFPFVGCSGBI1MVCQ
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.94 Safari/534.13
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: K3R7=3LJJ3QmEbCVHlmRdtFSbSwjmojI708sDnghZi0w-UFdVcbdJvAs_yWQ; ClrOSSID=1297389156812-9086; ClrSCD=1297389156812; JSESSIONID=Q3LJIA5WFPFVGCSGBI1MVCQ; cross-sell=hi; ClrCSTO=T; mmcore.tst=0.327; mmid=1956720199%7CBgAAAAqUFIqT3gUAAA%3D%3D; mmcore.srv=cg1.use; mmcore.pd=1956720199%7CBgAAAAqUFIqT3gUAAA%3D%3D; ClrSSID=1297389156812-9086; WT_FPC=id=173.193.214.243-2605364368.30126492:lv=1297382512615:ss=1297381960185

Response

HTTP/1.1 200 OK
Server: Netscape-Enterprise/6.0
Content-Type: text/html
P3p: policyref="/w3c/p3p.xml", CP="NOI DSP DEVa TAIa OUR BUS UNI"
Pragma: no-cache
Cache-Control: no-cache
Expires: Tue, 04 Dec 1993 21:29:02 GMT
Vary: Accept-Encoding
Date: Fri, 11 Feb 2011 02:02:20 GMT
Connection: keep-alive
Content-Length: 34237



<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

    <HTML>
<HEAD>

           <TITLE>Login Page</TITLE>


           <LINK rel
...[SNIP]...
<td><a href="/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/en_US/hi/index.do" title="Go to home page" tabindex="3" class="OneLinkKeepLinks"><img src="/en/hi/media/images/logos/hdr_logo.gif" alt="Hilton Hotels" border="0">
...[SNIP]...
<li id="navmain01" title="Specials & Packages"><a href="https://secure.hilton.com/en/hi/promotions/index.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ">Specials & Packages</a>
...[SNIP]...
<li id="navmain02" title="Reservations"><a href="https://secure.hilton.com/en/hi/reservations/index.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ">Reservations</a>
...[SNIP]...
<li id="navmain03" title="Meetings"><a href="https://secure.hilton.com/en/hi/groups/index.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?eventType=Business">Meetings</a>
...[SNIP]...
<li id="navmain0302" title="Social Gatherings"><a href="https://secure.hilton.com/en/hi/groups/index.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?eventType=Social&it=Tnav,GM">Social Gatherings</a>
...[SNIP]...
<li id="navmain05" title="Travel Guides"><a href="https://secure.hilton.com/en/hi/ctg/index.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ">Travel Guides</a>
...[SNIP]...
<li id="navmain07" title="My Favorite Hotels"><a href="https://secure.hilton.com/en/hi/cart/index.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ">My Favorite Hotels</a>
...[SNIP]...
<li class="brandBarLi brandBarLi_CH" id="brandBarLi_CH"><a class="brandBarLiA" href="/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/en/ch/home.do" onmouseover="turnOnPopup('brandBarLi_CH');" onmouseout="turnOffPopup('brandBarLi_CH');"></a>
...[SNIP]...
<li class="brandBarLi brandBarLi_HI" id="brandBarLi_HI"><a class="brandBarLiA" href="/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/en_US/hi/index.do" onmouseover="turnOnPopup('brandBarLi_HI');" onmouseout="turnOffPopup('brandBarLi_HI');"></a>
...[SNIP]...
<li class="brandBarLi brandBarLi_DT" id="brandBarLi_DT"><a class="brandBarLiA" href="/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/en_US/dt/index.do" onmouseover="turnOnPopup('brandBarLi_DT');" onmouseout="turnOffPopup('brandBarLi_DT');"></a>
...[SNIP]...
<li class="brandBarLi brandBarLi_ES" id="brandBarLi_ES"><a class="brandBarLiA" href="/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/en_US/es/index.do" onmouseover="turnOnPopup('brandBarLi_ES');" onmouseout="turnOffPopup('brandBarLi_ES');"></a>
...[SNIP]...
<li class="brandBarLi brandBarLi_GI" id="brandBarLi_GI"><a class="brandBarLiA" href="/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/en_US/gi/index.do" onmouseover="turnOnPopup('brandBarLi_GI');" onmouseout="turnOffPopup('brandBarLi_GI');"></a>
...[SNIP]...
<li class="brandBarLi brandBarLi_HP" id="brandBarLi_HP"><a class="brandBarLiA" href="/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/en_US/hp/index.do" onmouseover="turnOnPopup('brandBarLi_HP');" onmouseout="turnOffPopup('brandBarLi_HP');"></a>
...[SNIP]...
<li class="brandBarLi brandBarLi_HW" id="brandBarLi_HW"><a class="brandBarLiA" href="/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/en_US/hw/index.do" onmouseover="turnOnPopup('brandBarLi_HW');" onmouseout="turnOffPopup('brandBarLi_HW');"></a>
...[SNIP]...
<li class="brandBarLi brandBarLi_HT" id="brandBarLi_HT"><a class="brandBarLiA" href="/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/en_US/ht/index.do" onmouseover="turnOnPopup('brandBarLi_HT');" onmouseout="turnOffPopup('brandBarLi_HT');"></a>
...[SNIP]...
<li class="brandBarLi brandBarLi_WW" id="brandBarLi_WW"><a class="brandBarLiA" href="/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/en_US/hh/home_index.do"></a>
...[SNIP]...
<li>
                                           <a href="/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/en_US/hi/sitemap/index.do">Site Map</a>
...[SNIP]...
<li>
                                           <a href="/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/en_US/hi/customersupport/index.do" rel="nofollow">Customer Support</a>
...[SNIP]...
<li>
                                       <a href="/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/en_US/ww/customersupport/privacy-policy.do" target="_blank" rel="nofollow">Privacy Policy (updated July 2007)</a>
...[SNIP]...
<li>
                                       <a href="/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/en_US/hi/customersupport/site-usage.do" rel="nofollow">Site Usage Agreement</a>
...[SNIP]...
<li><a href="/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/es/hi/index.do">Espa.ol</a>
...[SNIP]...
<li><a href="/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/fr/hi/index.do">Fran.ais</a>
...[SNIP]...

3.8. https://secure.hilton.com/en/hi/login/reward_login.jhtml previous next

Summary

Severity:	Medium
Confidence:	Firm
Host:	https://secure.hilton.com
Path:	/en/hi/login/reward_login.jhtml

Issue detail

The URL in the request appears to contain a session token within the query string:

https://secure.hilton.com/en/hi/login/reward_login.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?nextHandler=/com/hilton/res/client/handler/ChooseDatesProxyHandler&_requestid=288910

Request

Response

3.9. https://secure.hilton.com/en/hi/res/choose_dates.jhtml previous next

Summary

Severity:	Medium
Confidence:	Firm
Host:	https://secure.hilton.com
Path:	/en/hi/res/choose_dates.jhtml

Issue detail

The URL in the request appears to contain a session token within the query string:

https://secure.hilton.com/en/hi/res/choose_dates.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?_requestid=285735

Request

GET /en/hi/res/choose_dates.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?_requestid=285735 HTTP/1.1
Host: secure.hilton.com
Connection: keep-alive
Referer: http://www1.hilton.com/en_US/hi/hotel/BOSFDHF-Hilton-Boston-Financial-District-Massachusetts/index.do;jsessionid=0ABC42E492304CBBBCE5486E110ECEB6.etc32?brand_id=HI&brand_directory=/en/hi/&xch=826093977,Q3LJIA5WFPFVGCSGBI1MVCQ
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.94 Safari/534.13
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: K3R7=3LJJ3QmEbCVHlmRdtFSbSwjmojI708sDnghZi0w-UFdVcbdJvAs_yWQ; ClrOSSID=1297389156812-9086; ClrSCD=1297389156812; JSESSIONID=Q3LJIA5WFPFVGCSGBI1MVCQ; cross-sell=hi; ClrCSTO=T; mmcore.tst=0.451; mmid=1891688497%7CBQAAAAqUFIqT3gUAAA%3D%3D; mmcore.pd=1891688497%7CBQAAAAqUFIqT3gUAAA%3D%3D; mmcore.srv=cg1.use; ClrSSID=1297389156812-9086; WT_FPC=id=173.193.214.243-2605364368.30126492:lv=1297382461468:ss=1297381960185

Response

3.10. https://secure.hilton.com/en/hi/res/choose_dates.jhtml previous next

Summary

Severity:	Medium
Confidence:	Firm
Host:	https://secure.hilton.com
Path:	/en/hi/res/choose_dates.jhtml

Issue detail

The response contains the following links that appear to contain session tokens:

https://secure.hilton.com/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/en_US/hi/hotel/BOSFDHF-Hilton-Boston-Financial-District-Massachusetts/index.do&ctyhocn=BOSFDHF
https://secure.hilton.com/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/en_US/hi/index.do
https://secure.hilton.com/en/hi/info/site_usage.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ

Request

Response

3.11. https://secure.hilton.com/en/hi/res/choose_rates.jhtml previous next

Summary

Severity:	Medium
Confidence:	Firm
Host:	https://secure.hilton.com
Path:	/en/hi/res/choose_rates.jhtml

Issue detail

The response contains the following links that appear to contain session tokens:

https://secure.hilton.com/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/en_US/hi/hotel/BOSFDHF-Hilton-Boston-Financial-District-Massachusetts/index.do&ctyhocn=BOSFDHF
https://secure.hilton.com/doxch.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?dst=http://HI/en_US/hi/index.do
https://secure.hilton.com/en/hi/info/site_usage.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ

Request

GET /en/hi/res/choose_rates.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?_requestid=290307 HTTP/1.1
Host: secure.hilton.com
Connection: keep-alive
Referer: https://secure.hilton.com/en/hi/res/choose_dates.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?_requestid=290028
Cache-Control: max-age=0
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.94 Safari/534.13
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: K3R7=3LJJ3QmEbCVHlmRdtFSbSwjmojI708sDnghZi0w-UFdVcbdJvAs_yWQ; ClrOSSID=1297389156812-9086; ClrSCD=1297389156812; JSESSIONID=Q3LJIA5WFPFVGCSGBI1MVCQ; cross-sell=hi; ClrCSTO=T; mmid=-1032479705%7CBwAAAAqUFIqT3gUAAA%3D%3D; mmcore.pd=-1032479705%7CBwAAAAqUFIqT3gUAAA%3D%3D; mmcore.srv=cg1.use; mmcore.tst=0.076; ClrSSID=1297389156812-9086; WT_FPC=id=173.193.214.243-2605364368.30126492:lv=1297382656474:ss=1297381960185

Response

3.12. https://secure.hilton.com/en/hi/res/choose_rates.jhtml previous next

Summary

Severity:	Medium
Confidence:	Firm
Host:	https://secure.hilton.com
Path:	/en/hi/res/choose_rates.jhtml

Issue detail

The URL in the request appears to contain a session token within the query string:

https://secure.hilton.com/en/hi/res/choose_rates.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?_requestid=290307

Request

Response

3.13. https://secure.hilton.com/en/hi/res/your_information.jhtml previous next

Summary

Severity:	Medium
Confidence:	Firm
Host:	https://secure.hilton.com
Path:	/en/hi/res/your_information.jhtml

Issue detail

The URL in the request appears to contain a session token within the query string:

https://secure.hilton.com/en/hi/res/your_information.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?_requestid=291424

Request

GET /en/hi/res/your_information.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?_requestid=291424 HTTP/1.1
Host: secure.hilton.com
Connection: keep-alive
Referer: https://secure.hilton.com/en/hi/res/choose_rates.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?_requestid=290307
Cache-Control: max-age=0
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.94 Safari/534.13
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: K3R7=3LJJ3QmEbCVHlmRdtFSbSwjmojI708sDnghZi0w-UFdVcbdJvAs_yWQ; ClrOSSID=1297389156812-9086; ClrSCD=1297389156812; JSESSIONID=Q3LJIA5WFPFVGCSGBI1MVCQ; cross-sell=hi; mmid=-1032479705%7CBwAAAAqUFIqT3gUAAA%3D%3D; mmcore.pd=-1032479705%7CBwAAAAqUFIqT3gUAAA%3D%3D; mmcore.srv=cg1.use; mmcore.tst=0.052; ClrSSID=1297389156812-9086; WT_FPC=id=173.193.214.243-2605364368.30126492:lv=1297382694099:ss=1297381960185

Response

HTTP/1.1 200 OK
Server: Netscape-Enterprise/6.0
Content-Length: 0
Content-Type: text/html
P3p: policyref="/w3c/p3p.xml", CP="NOI DSP DEVa TAIa OUR BUS UNI"
Pragma: no-cache
Cache-Control: no-cache
Expires: Tue, 04 Dec 1993 21:29:02 GMT
Date: Fri, 11 Feb 2011 02:05:13 GMT
Connection: keep-alive
Vary: Accept-Encoding

3.14. https://secure.hilton.com/en/hi/signup/create_account.jhtml previous next

Summary

Severity:	Medium
Confidence:	Firm
Host:	https://secure.hilton.com
Path:	/en/hi/signup/create_account.jhtml

Issue detail

The URL in the request appears to contain a session token within the query string:

https://secure.hilton.com/en/hi/signup/create_account.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ

Request

Response

3.15. https://secure.hilton.com/en/hi/signup/create_account.jhtml previous next

Summary

Severity:	Medium
Confidence:	Firm
Host:	https://secure.hilton.com
Path:	/en/hi/signup/create_account.jhtml

Issue detail

The response contains the following links that appear to contain session tokens:

https://secure.hilton.com/en/common/js/cart.js;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ
https://secure.hilton.com/en/common/js/common.js;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ
https://secure.hilton.com/en/common/js/footer.js;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ
https://secure.hilton.com/en/common/js/popup.js;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ
https://secure.hilton.com/en/common/webtrends/wtbaseHilton.js;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ
https://secure.hilton.com/en/common/webtrends/wtinit.js;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ
https://secure.hilton.com/en/hhonors/index.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ
https://secure.hilton.com/en/hi/brand/about.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ
https://secure.hilton.com/en/hi/cart/index.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ
https://secure.hilton.com/en/hi/ctg/index.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ
https://secure.hilton.com/en/hi/groups/index.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?eventType=Business
https://secure.hilton.com/en/hi/groups/index.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?eventType=Social&it=Tnav,GM
https://secure.hilton.com/en/hi/help/sign_in_help.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ
https://secure.hilton.com/en/hi/promotions/hilton_regional_main/index.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?cid=OM,HH,Homepagelinks,Regional,Offer&it=Offer,Regional
https://secure.hilton.com/en/hi/promotions/index.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ
https://secure.hilton.com/en/hi/reservations/index.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ
https://secure.hilton.com/en/hi/signup/hhonors_enroll.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ
https://secure.hilton.com/en/hi/signup/reservation_profile.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ

Request

Response

3.16. https://secure.hilton.com/en/hi/signup/reservation_profile.jhtml previous next

Summary

Severity:	Medium
Confidence:	Firm
Host:	https://secure.hilton.com
Path:	/en/hi/signup/reservation_profile.jhtml

Issue detail

The URL in the request appears to contain a session token within the query string:

https://secure.hilton.com/en/hi/signup/reservation_profile.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ

Request

GET /en/hi/signup/reservation_profile.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ HTTP/1.1
Host: secure.hilton.com
Connection: keep-alive
Referer: https://secure.hilton.com/en/hi/signup/create_account.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.94 Safari/534.13
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: cross-sell=hi; mmcore.tst=0.532; K3R7=3LJJ3QmEbCVHlmRdtFSbSwjmojI708sDnghZi0w-UFdVcbdJvAs_yWQ; mmid=1193586808%7CAQAAAAqUFIqT3gUAAA%3D%3D; mmcore.pd=1193586808%7CAQAAAAqUFIqT3gUAAA%3D%3D; mmcore.srv=cg1.use; ClrCSTO=T; ClrSSID=1297389156812-9086; ClrOSSID=1297389156812-9086; ClrSCD=1297389156812; JSESSIONID=Q3LJIA5WFPFVGCSGBI1MVCQ; WT_FPC=id=173.193.214.243-2605364368.30126492:lv=1297381970606:ss=1297381960185

Response

3.17. https://secure.hilton.com/en/hi/signup/reservation_profile.jhtml previous next

Summary

Severity:	Medium
Confidence:	Firm
Host:	https://secure.hilton.com
Path:	/en/hi/signup/reservation_profile.jhtml

Issue detail

The response contains the following links that appear to contain session tokens:

https://secure.hilton.com/en/hi/cart/index.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ
https://secure.hilton.com/en/hi/ctg/index.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ
https://secure.hilton.com/en/hi/groups/index.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?eventType=Business
https://secure.hilton.com/en/hi/groups/index.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?eventType=Social&it=Tnav,GM
https://secure.hilton.com/en/hi/help/sign_in_help.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ
https://secure.hilton.com/en/hi/promotions/index.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ
https://secure.hilton.com/en/hi/reservations/index.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ
https://secure.hilton.com/en/hi/signup/create_account.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ

Request

Response

4. Cookie without HttpOnly flag set previous next

Summary

Severity:	Low
Confidence:	Firm
Host:	https://secure.hilton.com
Path:	/en/hi/signup/create_account.jhtml

Issue detail

The following cookie was issued by the application and does not have the HttpOnly flag set:

JSESSIONID=Q3LJIA5WFPFVGCSGBI1MVCQ; path=/

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

Response

5. Password field with autocomplete enabled previous next
There are 7 instances of this issue:

/en/hi/login/reward_login.jhtml
/en/hi/res/choose_dates.jhtml
/en/hi/res/choose_dates.jhtml
/en/hi/signup/create_account.jhtml
/en/hi/signup/create_account.jhtml
/en/hi/signup/reservation_profile.jhtml
/en/hi/signup/reservation_profile.jhtml

Issue background

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).

5.1. https://secure.hilton.com/en/hi/login/reward_login.jhtml previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	https://secure.hilton.com
Path:	/en/hi/login/reward_login.jhtml

Issue detail

The page contains a form with the following action URL:

https://secure.hilton.com/en/hi/login/reward_login.jhtml?_DARGS=/en/crm/login/reward_login.jhtml.2

The form contains the following password field with autocomplete enabled:

password

Request

Response

5.2. https://secure.hilton.com/en/hi/res/choose_dates.jhtml previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	https://secure.hilton.com
Path:	/en/hi/res/choose_dates.jhtml

Issue detail

The page contains a form with the following action URL:

https://secure.hilton.com/en/wa/mytravelplanner/my_account.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?_DARGS=/en/crm/login/generic_widget.jhtml

The form contains the following password field with autocomplete enabled:

password

Request

GET /en/hi/res/choose_dates.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?_requestid=290028 HTTP/1.1
Host: secure.hilton.com
Connection: keep-alive
Referer: http://www1.hilton.com/en_US/hi/hotel/BOSFDHF-Hilton-Boston-Financial-District-Massachusetts8b619%22%3E%3Cimg%20src%3da%20onerror%3dalert(document.cookie)%3E7fb045a4243/index.do;jsessionid=0ABC42E492304CBBBCE5486E110ECEB6.etc32?brand_id=HI&brand_directory=/en/hi/&xch=826093977,Q3LJIA5WFPFVGCSGBI1MVCQ
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.94 Safari/534.13
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: K3R7=3LJJ3QmEbCVHlmRdtFSbSwjmojI708sDnghZi0w-UFdVcbdJvAs_yWQ; ClrOSSID=1297389156812-9086; ClrSCD=1297389156812; JSESSIONID=Q3LJIA5WFPFVGCSGBI1MVCQ; cross-sell=hi; ClrCSTO=T; mmcore.tst=0.868; mmid=-1032479705%7CBwAAAAqUFIqT3gUAAA%3D%3D; mmcore.pd=-1032479705%7CBwAAAAqUFIqT3gUAAA%3D%3D; mmcore.srv=cg1.use; ClrSSID=1297389156812-9086; WT_FPC=id=173.193.214.243-2605364368.30126492:lv=1297382639024:ss=1297381960185

Response

5.3. https://secure.hilton.com/en/hi/res/choose_dates.jhtml previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	https://secure.hilton.com
Path:	/en/hi/res/choose_dates.jhtml

Issue detail

The page contains a form with the following action URL:

https://secure.hilton.com/en/hi/mytravelplanner/my_account.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?_DARGS=/en/crm/login/generic_widget.jhtml

The form contains the following password field with autocomplete enabled:

password

Request

Response

5.4. https://secure.hilton.com/en/hi/signup/create_account.jhtml previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	https://secure.hilton.com
Path:	/en/hi/signup/create_account.jhtml

Issue detail

The page contains a form with the following action URL:

https://secure.hilton.com/en/hi/signup/create_account.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?_DARGS=/en/crm/signup/select_account.jhtml

The form contains the following password field with autocomplete enabled:

password

Request

Response

5.5. https://secure.hilton.com/en/hi/signup/create_account.jhtml previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	https://secure.hilton.com
Path:	/en/hi/signup/create_account.jhtml

Issue detail

The page contains a form with the following action URL:

https://secure.hilton.com/en/hi/signup/create_account.jhtml?_DARGS=/en/crm/signup/select_account.jhtml

The form contains the following password field with autocomplete enabled:

password

Request

Response

5.6. https://secure.hilton.com/en/hi/signup/reservation_profile.jhtml previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	https://secure.hilton.com
Path:	/en/hi/signup/reservation_profile.jhtml

Issue detail

The page contains a form with the following action URL:

https://secure.hilton.com/en/hi/signup/reservation_profile.jhtml?_DARGS=/en/crm/signup/res_acct.jhtml

The form contains the following password fields with autocomplete enabled:

password
confirmPassword

Request

Response

5.7. https://secure.hilton.com/en/hi/signup/reservation_profile.jhtml previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	https://secure.hilton.com
Path:	/en/hi/signup/reservation_profile.jhtml

Issue detail

The page contains a form with the following action URL:

https://secure.hilton.com/en/hi/mytravelplanner/my_account.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?_DARGS=/en/crm/login/widget_homepage.jhtml.8

The form contains the following password field with autocomplete enabled:

password

Request

Response

6. Cross-domain Referer leakage previous next
There are 4 instances of this issue:

/en/hi/login/reward_login.jhtml
/en/hi/res/choose_rates.jhtml
/en/hi/signup/create_account.jhtml
/en/hi/signup/reservation_profile.jhtml

Issue background

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.

6.1. https://secure.hilton.com/en/hi/login/reward_login.jhtml previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.hilton.com
Path:	/en/hi/login/reward_login.jhtml

Issue detail

The page was loaded from a URL containing a query string:

https://secure.hilton.com/en/hi/login/reward_login.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?nextHandler=/com/hilton/res/client/handler/ChooseDatesProxyHandler&_requestid=288910

The response contains the following link to another domain:

https://seal.verisign.com/getseal?host_name=secure.hilton.com&size=S&use_flash=YES&use_transparent=YES&lang=en

Request

Response

6.2. https://secure.hilton.com/en/hi/res/choose_rates.jhtml previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.hilton.com
Path:	/en/hi/res/choose_rates.jhtml

Issue detail

The page was loaded from a URL containing a query string:

https://secure.hilton.com/en/hi/res/choose_rates.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?_requestid=290307

The response contains the following link to another domain:

https://fls.doubleclick.net/activityi;src=2013561;type=count890;cat=brand636;ord=1;num=1?

Request

Response

6.3. https://secure.hilton.com/en/hi/signup/create_account.jhtml previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.hilton.com
Path:	/en/hi/signup/create_account.jhtml

Issue detail

The page was loaded from a URL containing a query string:

https://secure.hilton.com/en/hi/signup/create_account.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ

The response contains the following link to another domain:

https://seal.verisign.com/getseal?host_name=secure.hilton.com&size=S&use_flash=YES&use_transparent=YES&lang=en

Request

Response

6.4. https://secure.hilton.com/en/hi/signup/reservation_profile.jhtml previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.hilton.com
Path:	/en/hi/signup/reservation_profile.jhtml

Issue detail

The page was loaded from a URL containing a query string:

https://secure.hilton.com/en/hi/signup/reservation_profile.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ

The response contains the following link to another domain:

https://seal.verisign.com/getseal?host_name=secure.hilton.com&size=S&use_flash=YES&use_transparent=YES&lang=en

Request

Response

7. Cross-domain script include previous next
There are 3 instances of this issue:

/en/hi/login/reward_login.jhtml
/en/hi/signup/create_account.jhtml
/en/hi/signup/reservation_profile.jhtml

Issue background

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.

7.1. https://secure.hilton.com/en/hi/login/reward_login.jhtml previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.hilton.com
Path:	/en/hi/login/reward_login.jhtml

Issue detail

The response dynamically includes the following script from another domain:

https://seal.verisign.com/getseal?host_name=secure.hilton.com&size=S&use_flash=YES&use_transparent=YES&lang=en

Request

Response

7.2. https://secure.hilton.com/en/hi/signup/create_account.jhtml previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.hilton.com
Path:	/en/hi/signup/create_account.jhtml

Issue detail

The response dynamically includes the following script from another domain:

https://seal.verisign.com/getseal?host_name=secure.hilton.com&size=S&use_flash=YES&use_transparent=YES&lang=en

Request

Response

7.3. https://secure.hilton.com/en/hi/signup/reservation_profile.jhtml previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.hilton.com
Path:	/en/hi/signup/reservation_profile.jhtml

Issue detail

The response dynamically includes the following script from another domain:

https://seal.verisign.com/getseal?host_name=secure.hilton.com&size=S&use_flash=YES&use_transparent=YES&lang=en

Request

Response

8. Robots.txt file previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.hilton.com
Path:	/en/hi/signup/create_account.jhtml

Issue detail

The web server contains a robots.txt file.

Issue background

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: secure.hilton.com

Response

HTTP/1.0 200 OK
Server: Netscape-Enterprise/6.0
Content-Length: 25548
Content-Type: text/plain
ETag: "4199a553-587b-0-63cc"
Last-Modified: Thu, 28 Jan 2010 20:51:29 GMT
Accept-Ranges: bytes
Cache-Control: max-age=286406
Expires: Mon, 14 Feb 2011 09:24:56 GMT
Date: Fri, 11 Feb 2011 01:51:30 GMT
Connection: close

# Daytime instructions for search engines
# Do not visit Hilton.com during the day!
User-agent: Googlebot
Disallow: /guestlocale/
Disallow: /en/hhonors/login/owner_login.jhtml
Disallow: /en/hi/groups/
...[SNIP]...

9. Cacheable HTTPS response previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.hilton.com
Path:	/en/hi/res/choose_rates.jhtml

Issue description

Unless directed otherwise, browsers may store a local cached copy of content received from web servers. Some browsers, including Internet Explorer, cache content accessed via HTTPS. If sensitive information in application responses is stored in the local cache, then this may be retrieved by other users who have access to the same computer at a future time.

Issue remediation

The application should return caching directives instructing browsers not to store local copies of any sensitive data. Often, this can be achieved by configuring the web server to prevent caching for relevant paths within the web root. Alternatively, most web development platforms allow you to control the server's caching directives from within individual scripts. Ideally, the web server should return the following HTTP headers in all responses containing sensitive content:

Cache-control: no-store
Pragma: no-cache

Request

POST /en/hi/res/choose_rates.jhtml?_DARGS=/en/hw/res/choose_rates_form_body.jhtml.1 HTTP/1.1
Host: secure.hilton.com
Connection: keep-alive
Referer: https://secure.hilton.com/en/hi/res/choose_rates.jhtml;jsessionid=Q3LJIA5WFPFVGCSGBI1MVCQ?_requestid=295985
Cache-Control: max-age=0
Origin: https://secure.hilton.com
Content-Type: application/x-www-form-urlencoded
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.94 Safari/534.13
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: K3R7=3LJJ3QmEbCVHlmRdtFSbSwjmojI708sDnghZi0w-UFdVcbdJvAs_yWQ; ClrOSSID=1297389156812-9086; ClrSCD=1297389156812; JSESSIONID=Q3LJIA5WFPFVGCSGBI1MVCQ; cross-sell=hi; mmid=-1032479705%7CBwAAAAqUFIqT3gUAAA%3D%3D; mmcore.pd=-1032479705%7CBwAAAAqUFIqT3gUAAA%3D%3D; mmcore.srv=cg1.use; ClrCSTO=T; mmcore.tst=0.227; ClrSSID=1297389156812-9086; WT_FPC=id=173.193.214.243-2605364368.30126492:lv=1297382956320:ss=1297381960185
Content-Length: 1276

rateChooser=DJ%3AK1%3A0&_D%3ArateChooser=+&_D%3ArateChooser=+&_D%3ArateChooser=+&_D%3ArateChooser=+&_D%3ArateChooser=+&_D%3ArateChooser=+&_D%3ArateChooser=+&_D%3ArateChooser=+&_D%3ArateChooser=+&_D%3A
...[SNIP]...

Response

HTTP/1.1 200 OK
Server: Netscape-Enterprise/6.0
Content-Length: 0
Content-Type: text/html
P3p: policyref="/w3c/p3p.xml", CP="NOI DSP DEVa TAIa OUR BUS UNI"
Vary: Accept-Encoding
Date: Fri, 11 Feb 2011 02:08:12 GMT
Connection: keep-alive

10. HTML does not specify charset previous next
There are 5 instances of this issue:

/en/hi/login/reward_login.jhtml
/en/hi/res/choose_dates.jhtml
/en/hi/res/choose_rates.jhtml
/en/hi/signup/create_account.jhtml
/en/hi/signup/reservation_profile.jhtml

Issue description

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.

10.1. https://secure.hilton.com/en/hi/login/reward_login.jhtml previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.hilton.com
Path:	/en/hi/login/reward_login.jhtml

Request

Response

10.2. https://secure.hilton.com/en/hi/res/choose_dates.jhtml previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.hilton.com
Path:	/en/hi/res/choose_dates.jhtml

Request

Response

10.3. https://secure.hilton.com/en/hi/res/choose_rates.jhtml previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.hilton.com
Path:	/en/hi/res/choose_rates.jhtml

Request

Response

10.4. https://secure.hilton.com/en/hi/signup/create_account.jhtml previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.hilton.com
Path:	/en/hi/signup/create_account.jhtml

Request

Response

10.5. https://secure.hilton.com/en/hi/signup/reservation_profile.jhtml previous

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.hilton.com
Path:	/en/hi/signup/reservation_profile.jhtml

Request

Response

11. SSL certificate previous

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.hilton.com
Path:	/

Issue detail

The server presented a valid, trusted SSL certificate. This issue is purely informational.

The server presented the following certificates:

Server certificate

Issued to:	secure.hilton.com,ST=Tennessee
Issued by:	Akamai Subordinate CA 3
Valid from:	Thu Nov 18 09:27:10 CST 2010
Valid to:	Fri Nov 18 09:27:10 CST 2011

Certificate chain #1

Issued to:	Akamai Subordinate CA 3
Issued by:	GTE CyberTrust Global Root
Valid from:	Thu May 11 10:32:00 CDT 2006
Valid to:	Sat May 11 18:59:00 CDT 2013

Certificate chain #2

Issued to:	GTE CyberTrust Global Root
Issued by:	GTE CyberTrust Global Root
Valid from:	Wed Aug 12 19:29:00 CDT 1998
Valid to:	Mon Aug 13 18:59:00 CDT 2018

Issue background

SSL helps to protect the confidentiality and integrity of information in transit between the browser and server, and to provide authentication of the server's identity. To serve this purpose, the server must present an SSL certificate which is valid for the server's hostname, is issued by a trusted authority and is valid for the current date. If any one of these requirements is not met, SSL connections to the server will not provide the full protection for which SSL is designed.

It should be noted that various attacks exist against SSL in general, and in the context of HTTPS web connections. It may be possible for a determined and suitably-positioned attacker to compromise SSL connections without user detection even when a valid SSL certificate is used.

Report generated by CloudScan Vulnerability Crawler at Thu Feb 10 20:19:59 CST 2011.