seriousgameplay.com, SQL Injection, SQLi, CWe-89, CAPEC-86

SQL Injection in seriousgameplay.com | Vulnerability Crawler Report

Report generated by XSS.CX at Thu Dec 30 20:38:49 CST 2010.



Contents

Loading

1. SQL injection

2. SSL cookie without secure flag set

2.1. https://www.seriousgameplay.com/register.asp

2.2. https://www.seriousgameplay.com/

2.3. https://www.seriousgameplay.com/sbg.asp

3. Cross-site scripting (reflected)

3.1. https://www.seriousgameplay.com/register.asp [Referer HTTP header]

3.2. https://www.seriousgameplay.com/register.asp [%5Fkey1 cookie]

4. Cookie without HttpOnly flag set

4.1. https://www.seriousgameplay.com/register.asp

4.2. https://www.seriousgameplay.com/

4.3. https://www.seriousgameplay.com/sbg.asp

5. Password field with autocomplete enabled

6. Cross-domain script include

6.1. https://www.seriousgameplay.com/

6.2. https://www.seriousgameplay.com/register.asp

6.3. https://www.seriousgameplay.com/sbg.asp

7. Email addresses disclosed

7.1. https://www.seriousgameplay.com/

7.2. https://www.seriousgameplay.com/register.asp

7.3. https://www.seriousgameplay.com/sbg.asp

8. Cacheable HTTPS response

8.1. https://www.seriousgameplay.com/

8.2. https://www.seriousgameplay.com/register.asp

8.3. https://www.seriousgameplay.com/sbg.asp

9. SSL certificate



1. SQL injection  next

Summary

Severity:   High
Confidence:   Firm
Host:   https://www.seriousgameplay.com
Path:   /register.asp

Issue detail

The %5Fkey1 cookie appears to be vulnerable to SQL injection attacks. The payload ' was submitted in the %5Fkey1 cookie, and a database error message was returned. 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 Microsoft SQL Server.

Remediation detail

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

Issue background

SQL injection vulnerabilities arise when user-controllable data is incorporated into database SQL queries in an unsafe manner. An attacker can supply crafted input to break out of the data context in which their input appears and interfere with the structure of the surrounding query.

Various attacks can be delivered via SQL injection, including reading or modifying critical application data, interfering with application logic, escalating privileges within the database and executing operating system commands.

Remediation background

The most effective way to prevent SQL injection attacks is to use parameterised queries (also known as prepared statements) for all database access. This method uses two steps to incorporate potentially tainted data into SQL queries: first, the application specifies the structure of the query, leaving placeholders for each item of user input; second, the application specifies the contents of each placeholder. Because the structure of the query has already defined in the first step, it is not possible for malformed data in the second step to interfere with the query structure. You should review the documentation for your database and application platform to determine the appropriate APIs which you can use to perform parameterised queries. It is strongly recommended that you parameterise every variable data item that is incorporated into database queries, even if it is not obviously tainted, to prevent oversights occurring and avoid vulnerabilities being introduced by changes elsewhere within the code base of the application.

You should be aware that some commonly employed and recommended mitigations for SQL injection vulnerabilities are not always effective:

Request

GET /register.asp HTTP/1.1
Host: www.seriousgameplay.com
Connection: keep-alive
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: __utmz=41989927.1293356350.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=41989927.727380761.1293356350.1293356350.1293644579.2; %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM; %5Fkey1=870557771'

Response

HTTP/1.1 200 OK
Date: Wed, 29 Dec 2010 22:19:22 GMT
Server: Microsoft-IIS/6.0
P3P: CP="NOI DSP COR NID"
X-Powered-By: ASP.NET
Content-Length: 274
Content-Type: text/html
Set-Cookie: ASPSESSIONIDCCRBARTC=LEBFLEKBHDDIEMHBKHGECIDB; path=/
Cache-control: private

Database SQL Error.<br>SQL Query: select ID, Vars from Sessions WITH (NOLOCK) where Key1=870557771' and Key2 = '12/25/2010 10:40:21 PM' and Key3='174.121.222.18' and AccountID is null order by Recalle
...[SNIP]...
<br>Error Description: Line 1: Incorrect syntax near ' and Key2 = '.

2. SSL cookie without secure flag set  previous  next
There are 3 instances of this issue:

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.


2.1. https://www.seriousgameplay.com/register.asp  next

Summary

Severity:   Medium
Confidence:   Firm
Host:   https://www.seriousgameplay.com
Path:   /register.asp

Issue detail

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

Request

GET /register.asp HTTP/1.1
Host: www.seriousgameplay.com
Connection: keep-alive
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: __utmz=41989927.1293356350.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=41989927.727380761.1293356350.1293356350.1293644579.2; %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM; %5Fkey1=870557771

Response

HTTP/1.1 200 OK
Date: Wed, 29 Dec 2010 22:08:54 GMT
Server: Microsoft-IIS/6.0
P3P: CP="NOI DSP COR NID"
X-Powered-By: ASP.NET
Content-Length: 50331
Content-Type: text/html
Set-Cookie: %5Fkey1=870557771; expires=Fri, 31-Jan-2025 05:00:00 GMT; path=/
Set-Cookie: %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM; expires=Fri, 31-Jan-2025 05:00:00 GMT; path=/
Set-Cookie: ASPSESSIONIDCCRBARTC=DCPELEKBLHKKDFCJMHMJDLLJ; path=/
Cache-control: private

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><link rel="shortcut icon" href="/favicon.ico" type="imag
...[SNIP]...

2.2. https://www.seriousgameplay.com/  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.seriousgameplay.com
Path:   /

Issue detail

The following cookies were issued by the application and do not have the secure flag set:The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.

Request

GET / HTTP/1.1
Host: www.seriousgameplay.com
Connection: keep-alive
Referer: https://www.seriousgameplay.com/register.asp
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: __utmz=41989927.1293356350.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=41989927.727380761.1293356350.1293356350.1293644579.2; ASPSESSIONIDCCRBARTC=DCPELEKBLHKKDFCJMHMJDLLJ; %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM; %5Fkey1=870557771

Response

HTTP/1.1 200 OK
Date: Wed, 29 Dec 2010 22:09:40 GMT
Server: Microsoft-IIS/6.0
P3P: CP="NOI DSP COR NID"
X-Powered-By: ASP.NET
Content-Length: 49059
Content-Type: text/html
Set-Cookie: %5Fkey1=870557771; expires=Fri, 31-Jan-2025 05:00:00 GMT; path=/
Set-Cookie: %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM; expires=Fri, 31-Jan-2025 05:00:00 GMT; path=/
Cache-control: private

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><link rel="shortcut icon" href="/favicon.ico" type="imag
...[SNIP]...

2.3. https://www.seriousgameplay.com/sbg.asp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.seriousgameplay.com
Path:   /sbg.asp

Issue detail

The following cookies were issued by the application and do not have the secure flag set:The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.

Request

GET /sbg.asp HTTP/1.1
Host: www.seriousgameplay.com
Connection: keep-alive
Referer: https://www.seriousgameplay.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.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: __utmz=41989927.1293356350.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=41989927.727380761.1293356350.1293356350.1293644579.2; ASPSESSIONIDCCRBARTC=DCPELEKBLHKKDFCJMHMJDLLJ; %5Fkey1=870557771; %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM

Response

HTTP/1.1 200 OK
Date: Wed, 29 Dec 2010 22:09:45 GMT
Server: Microsoft-IIS/6.0
P3P: CP="NOI DSP COR NID"
X-Powered-By: ASP.NET
Content-Length: 37435
Content-Type: text/html
Set-Cookie: %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM; expires=Fri, 31-Jan-2025 05:00:00 GMT; path=/
Set-Cookie: %5Fkey1=870557771; expires=Fri, 31-Jan-2025 05:00:00 GMT; path=/
Cache-control: private

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><link rel="shortcut icon" href="/favicon.ico" type="imag
...[SNIP]...

3. Cross-site scripting (reflected)  previous  next
There are 2 instances of this issue:

Issue background

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

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

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

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

Issue remediation

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


3.1. https://www.seriousgameplay.com/register.asp [Referer HTTP header]  previous  next

Summary

Severity:   Low
Confidence:   Certain
Host:   https://www.seriousgameplay.com
Path:   /register.asp

Issue detail

The value of the Referer HTTP header is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 4e9b9"><script>alert(1)</script>3fd6a9b9d69 was submitted in the Referer HTTP header. 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.

Because the user data that is copied into the response is submitted within a request header, the application's behaviour is not trivial to exploit in an attack against another user. In the past, methods have existed of using client-side technologies such as Flash to cause another user to make a request containing an arbitrary HTTP header. If you can use such a technique, you can probably leverage it to exploit the XSS flaw. This limitation partially mitigates the impact of the vulnerability.

Request

GET /register.asp HTTP/1.1
Host: www.seriousgameplay.com
Connection: keep-alive
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: __utmz=41989927.1293356350.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=41989927.727380761.1293356350.1293356350.1293644579.2; %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM; %5Fkey1=870557771
Referer: http://www.google.com/search?hl=en&q=4e9b9"><script>alert(1)</script>3fd6a9b9d69

Response

HTTP/1.1 200 OK
Date: Wed, 29 Dec 2010 22:20:26 GMT
Server: Microsoft-IIS/6.0
P3P: CP="NOI DSP COR NID"
X-Powered-By: ASP.NET
Content-Length: 50411
Content-Type: text/html
Set-Cookie: %5Fkey1=870557771; expires=Fri, 31-Jan-2025 05:00:00 GMT; path=/
Set-Cookie: %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM; expires=Fri, 31-Jan-2025 05:00:00 GMT; path=/
Set-Cookie: ASPSESSIONIDCCRBARTC=GLBFLEKBJBMCEDEOPAJDJFOG; path=/
Cache-control: private

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><link rel="shortcut icon" href="/favicon.ico" type="imag
...[SNIP]...
<a href="http://www.google.com/search?hl=en&q=4e9b9"><script>alert(1)</script>3fd6a9b9d69">
...[SNIP]...

3.2. https://www.seriousgameplay.com/register.asp [%5Fkey1 cookie]  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.seriousgameplay.com
Path:   /register.asp

Issue detail

The value of the %5Fkey1 cookie is copied into the HTML document as plain text between tags. The payload db336<script>alert(1)</script>9da33a43fb3 was submitted in the %5Fkey1 cookie. 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.

Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.

Request

GET /register.asp HTTP/1.1
Host: www.seriousgameplay.com
Connection: keep-alive
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: __utmz=41989927.1293356350.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=41989927.727380761.1293356350.1293356350.1293644579.2; %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM; %5Fkey1=870557771db336<script>alert(1)</script>9da33a43fb3

Response

HTTP/1.1 200 OK
Date: Wed, 29 Dec 2010 22:19:20 GMT
Server: Microsoft-IIS/6.0
P3P: CP="NOI DSP COR NID"
X-Powered-By: ASP.NET
Content-Length: 307
Content-Type: text/html
Set-Cookie: ASPSESSIONIDCCRBARTC=JEBFLEKBHMOBJBMPMFMNGCCI; path=/
Cache-control: private

Database SQL Error.<br>SQL Query: select ID, Vars from Sessions WITH (NOLOCK) where Key1=870557771db336<script>alert(1)</script>9da33a43fb3 and Key2 = '12/25/2010 10:40:21 PM' and Key3='174.121.222.18' and AccountID is null order by Recalled DESC<br>
...[SNIP]...

4. Cookie without HttpOnly flag set  previous  next
There are 3 instances of this issue:

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.



4.1. https://www.seriousgameplay.com/register.asp  previous  next

Summary

Severity:   Low
Confidence:   Firm
Host:   https://www.seriousgameplay.com
Path:   /register.asp

Issue detail

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

Request

GET /register.asp HTTP/1.1
Host: www.seriousgameplay.com
Connection: keep-alive
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: __utmz=41989927.1293356350.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=41989927.727380761.1293356350.1293356350.1293644579.2; %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM; %5Fkey1=870557771

Response

HTTP/1.1 200 OK
Date: Wed, 29 Dec 2010 22:08:54 GMT
Server: Microsoft-IIS/6.0
P3P: CP="NOI DSP COR NID"
X-Powered-By: ASP.NET
Content-Length: 50331
Content-Type: text/html
Set-Cookie: %5Fkey1=870557771; expires=Fri, 31-Jan-2025 05:00:00 GMT; path=/
Set-Cookie: %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM; expires=Fri, 31-Jan-2025 05:00:00 GMT; path=/
Set-Cookie: ASPSESSIONIDCCRBARTC=DCPELEKBLHKKDFCJMHMJDLLJ; path=/
Cache-control: private

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><link rel="shortcut icon" href="/favicon.ico" type="imag
...[SNIP]...

4.2. https://www.seriousgameplay.com/  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.seriousgameplay.com
Path:   /

Issue detail

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

Request

GET / HTTP/1.1
Host: www.seriousgameplay.com
Connection: keep-alive
Referer: https://www.seriousgameplay.com/register.asp
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: __utmz=41989927.1293356350.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=41989927.727380761.1293356350.1293356350.1293644579.2; ASPSESSIONIDCCRBARTC=DCPELEKBLHKKDFCJMHMJDLLJ; %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM; %5Fkey1=870557771

Response

HTTP/1.1 200 OK
Date: Wed, 29 Dec 2010 22:09:40 GMT
Server: Microsoft-IIS/6.0
P3P: CP="NOI DSP COR NID"
X-Powered-By: ASP.NET
Content-Length: 49059
Content-Type: text/html
Set-Cookie: %5Fkey1=870557771; expires=Fri, 31-Jan-2025 05:00:00 GMT; path=/
Set-Cookie: %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM; expires=Fri, 31-Jan-2025 05:00:00 GMT; path=/
Cache-control: private

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><link rel="shortcut icon" href="/favicon.ico" type="imag
...[SNIP]...

4.3. https://www.seriousgameplay.com/sbg.asp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.seriousgameplay.com
Path:   /sbg.asp

Issue detail

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

Request

GET /sbg.asp HTTP/1.1
Host: www.seriousgameplay.com
Connection: keep-alive
Referer: https://www.seriousgameplay.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.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: __utmz=41989927.1293356350.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=41989927.727380761.1293356350.1293356350.1293644579.2; ASPSESSIONIDCCRBARTC=DCPELEKBLHKKDFCJMHMJDLLJ; %5Fkey1=870557771; %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM

Response

HTTP/1.1 200 OK
Date: Wed, 29 Dec 2010 22:09:45 GMT
Server: Microsoft-IIS/6.0
P3P: CP="NOI DSP COR NID"
X-Powered-By: ASP.NET
Content-Length: 37435
Content-Type: text/html
Set-Cookie: %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM; expires=Fri, 31-Jan-2025 05:00:00 GMT; path=/
Set-Cookie: %5Fkey1=870557771; expires=Fri, 31-Jan-2025 05:00:00 GMT; path=/
Cache-control: private

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><link rel="shortcut icon" href="/favicon.ico" type="imag
...[SNIP]...

5. Password field with autocomplete enabled  previous  next

Summary

Severity:   Low
Confidence:   Certain
Host:   https://www.seriousgameplay.com
Path:   /register.asp

Issue detail

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

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

Request

GET /register.asp HTTP/1.1
Host: www.seriousgameplay.com
Connection: keep-alive
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: __utmz=41989927.1293356350.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=41989927.727380761.1293356350.1293356350.1293644579.2; %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM; %5Fkey1=870557771

Response

HTTP/1.1 200 OK
Date: Wed, 29 Dec 2010 22:08:54 GMT
Server: Microsoft-IIS/6.0
P3P: CP="NOI DSP COR NID"
X-Powered-By: ASP.NET
Content-Length: 50331
Content-Type: text/html
Set-Cookie: %5Fkey1=870557771; expires=Fri, 31-Jan-2025 05:00:00 GMT; path=/
Set-Cookie: %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM; expires=Fri, 31-Jan-2025 05:00:00 GMT; path=/
Set-Cookie: ASPSESSIONIDCCRBARTC=DCPELEKBLHKKDFCJMHMJDLLJ; path=/
Cache-control: private

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><link rel="shortcut icon" href="/favicon.ico" type="imag
...[SNIP]...
<hr noshade size=1><form method="post" action="register_zprocess.asp" onsubmit="CO_ToggleShipToFields(false);"><input type="hidden" name="BillCountry" value = "US UNITED STATES">
...[SNIP]...
<br><input type="password" name="password1" class="checkout" size=20 maxlength=20 class="register"> <small>
...[SNIP]...
<br><input type="password" name="password2" class="checkout" size=20 maxlength=20 class="register"></td>
...[SNIP]...

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

Issue background

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

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

Issue remediation

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


6.1. https://www.seriousgameplay.com/  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.seriousgameplay.com
Path:   /

Issue detail

The response dynamically includes the following script from another domain:

Request

GET / HTTP/1.1
Host: www.seriousgameplay.com
Connection: keep-alive
Referer: https://www.seriousgameplay.com/register.asp
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: __utmz=41989927.1293356350.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=41989927.727380761.1293356350.1293356350.1293644579.2; ASPSESSIONIDCCRBARTC=DCPELEKBLHKKDFCJMHMJDLLJ; %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM; %5Fkey1=870557771

Response

HTTP/1.1 200 OK
Date: Wed, 29 Dec 2010 22:09:40 GMT
Server: Microsoft-IIS/6.0
P3P: CP="NOI DSP COR NID"
X-Powered-By: ASP.NET
Content-Length: 49059
Content-Type: text/html
Set-Cookie: %5Fkey1=870557771; expires=Fri, 31-Jan-2025 05:00:00 GMT; path=/
Set-Cookie: %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM; expires=Fri, 31-Jan-2025 05:00:00 GMT; path=/
Cache-control: private

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><link rel="shortcut icon" href="/favicon.ico" type="imag
...[SNIP]...
</script><script language="JavaScript"
src="https://chat.livechatinc.net/licence/1006517/script.cgi?lang=en&groups=0">
</script>
...[SNIP]...

6.2. https://www.seriousgameplay.com/register.asp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.seriousgameplay.com
Path:   /register.asp

Issue detail

The response dynamically includes the following script from another domain:

Request

GET /register.asp HTTP/1.1
Host: www.seriousgameplay.com
Connection: keep-alive
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: __utmz=41989927.1293356350.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=41989927.727380761.1293356350.1293356350.1293644579.2; %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM; %5Fkey1=870557771

Response

HTTP/1.1 200 OK
Date: Wed, 29 Dec 2010 22:08:54 GMT
Server: Microsoft-IIS/6.0
P3P: CP="NOI DSP COR NID"
X-Powered-By: ASP.NET
Content-Length: 50331
Content-Type: text/html
Set-Cookie: %5Fkey1=870557771; expires=Fri, 31-Jan-2025 05:00:00 GMT; path=/
Set-Cookie: %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM; expires=Fri, 31-Jan-2025 05:00:00 GMT; path=/
Set-Cookie: ASPSESSIONIDCCRBARTC=DCPELEKBLHKKDFCJMHMJDLLJ; path=/
Cache-control: private

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><link rel="shortcut icon" href="/favicon.ico" type="imag
...[SNIP]...
</script><script language="JavaScript"
src="https://chat.livechatinc.net/licence/1006517/script.cgi?lang=en&groups=0">
</script>
...[SNIP]...

6.3. https://www.seriousgameplay.com/sbg.asp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.seriousgameplay.com
Path:   /sbg.asp

Issue detail

The response dynamically includes the following script from another domain:

Request

GET /sbg.asp HTTP/1.1
Host: www.seriousgameplay.com
Connection: keep-alive
Referer: https://www.seriousgameplay.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.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: __utmz=41989927.1293356350.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=41989927.727380761.1293356350.1293356350.1293644579.2; ASPSESSIONIDCCRBARTC=DCPELEKBLHKKDFCJMHMJDLLJ; %5Fkey1=870557771; %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM

Response

HTTP/1.1 200 OK
Date: Wed, 29 Dec 2010 22:09:45 GMT
Server: Microsoft-IIS/6.0
P3P: CP="NOI DSP COR NID"
X-Powered-By: ASP.NET
Content-Length: 37435
Content-Type: text/html
Set-Cookie: %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM; expires=Fri, 31-Jan-2025 05:00:00 GMT; path=/
Set-Cookie: %5Fkey1=870557771; expires=Fri, 31-Jan-2025 05:00:00 GMT; path=/
Cache-control: private

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><link rel="shortcut icon" href="/favicon.ico" type="imag
...[SNIP]...
</script><script language="JavaScript"
src="https://chat.livechatinc.net/licence/1006517/script.cgi?lang=en&groups=0">
</script>
...[SNIP]...

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

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


7.1. https://www.seriousgameplay.com/  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.seriousgameplay.com
Path:   /

Issue detail

The following email address was disclosed in the response:

Request

GET / HTTP/1.1
Host: www.seriousgameplay.com
Connection: keep-alive
Referer: https://www.seriousgameplay.com/register.asp
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: __utmz=41989927.1293356350.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=41989927.727380761.1293356350.1293356350.1293644579.2; ASPSESSIONIDCCRBARTC=DCPELEKBLHKKDFCJMHMJDLLJ; %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM; %5Fkey1=870557771

Response

HTTP/1.1 200 OK
Date: Wed, 29 Dec 2010 22:09:40 GMT
Server: Microsoft-IIS/6.0
P3P: CP="NOI DSP COR NID"
X-Powered-By: ASP.NET
Content-Length: 49059
Content-Type: text/html
Set-Cookie: %5Fkey1=870557771; expires=Fri, 31-Jan-2025 05:00:00 GMT; path=/
Set-Cookie: %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM; expires=Fri, 31-Jan-2025 05:00:00 GMT; path=/
Cache-control: private

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><link rel="shortcut icon" href="/favicon.ico" type="imag
...[SNIP]...
<a href="mailto:info@seriousshops.com">
...[SNIP]...

7.2. https://www.seriousgameplay.com/register.asp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.seriousgameplay.com
Path:   /register.asp

Issue detail

The following email address was disclosed in the response:

Request

GET /register.asp HTTP/1.1
Host: www.seriousgameplay.com
Connection: keep-alive
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: __utmz=41989927.1293356350.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=41989927.727380761.1293356350.1293356350.1293644579.2; %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM; %5Fkey1=870557771

Response

HTTP/1.1 200 OK
Date: Wed, 29 Dec 2010 22:08:54 GMT
Server: Microsoft-IIS/6.0
P3P: CP="NOI DSP COR NID"
X-Powered-By: ASP.NET
Content-Length: 50331
Content-Type: text/html
Set-Cookie: %5Fkey1=870557771; expires=Fri, 31-Jan-2025 05:00:00 GMT; path=/
Set-Cookie: %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM; expires=Fri, 31-Jan-2025 05:00:00 GMT; path=/
Set-Cookie: ASPSESSIONIDCCRBARTC=DCPELEKBLHKKDFCJMHMJDLLJ; path=/
Cache-control: private

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><link rel="shortcut icon" href="/favicon.ico" type="imag
...[SNIP]...
<a href="mailto:info@seriousshops.com">
...[SNIP]...

7.3. https://www.seriousgameplay.com/sbg.asp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.seriousgameplay.com
Path:   /sbg.asp

Issue detail

The following email address was disclosed in the response:

Request

GET /sbg.asp HTTP/1.1
Host: www.seriousgameplay.com
Connection: keep-alive
Referer: https://www.seriousgameplay.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.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: __utmz=41989927.1293356350.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=41989927.727380761.1293356350.1293356350.1293644579.2; ASPSESSIONIDCCRBARTC=DCPELEKBLHKKDFCJMHMJDLLJ; %5Fkey1=870557771; %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM

Response

HTTP/1.1 200 OK
Date: Wed, 29 Dec 2010 22:09:45 GMT
Server: Microsoft-IIS/6.0
P3P: CP="NOI DSP COR NID"
X-Powered-By: ASP.NET
Content-Length: 37435
Content-Type: text/html
Set-Cookie: %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM; expires=Fri, 31-Jan-2025 05:00:00 GMT; path=/
Set-Cookie: %5Fkey1=870557771; expires=Fri, 31-Jan-2025 05:00:00 GMT; path=/
Cache-control: private

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><link rel="shortcut icon" href="/favicon.ico" type="imag
...[SNIP]...
<a href="mailto:info@seriousshops.com">
...[SNIP]...

8. Cacheable HTTPS response  previous  next
There are 3 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:


8.1. https://www.seriousgameplay.com/  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.seriousgameplay.com
Path:   /

Request

GET / HTTP/1.1
Host: www.seriousgameplay.com
Connection: keep-alive
Referer: https://www.seriousgameplay.com/register.asp
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: __utmz=41989927.1293356350.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=41989927.727380761.1293356350.1293356350.1293644579.2; ASPSESSIONIDCCRBARTC=DCPELEKBLHKKDFCJMHMJDLLJ; %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM; %5Fkey1=870557771

Response

HTTP/1.1 200 OK
Date: Wed, 29 Dec 2010 22:09:40 GMT
Server: Microsoft-IIS/6.0
P3P: CP="NOI DSP COR NID"
X-Powered-By: ASP.NET
Content-Length: 49059
Content-Type: text/html
Set-Cookie: %5Fkey1=870557771; expires=Fri, 31-Jan-2025 05:00:00 GMT; path=/
Set-Cookie: %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM; expires=Fri, 31-Jan-2025 05:00:00 GMT; path=/
Cache-control: private

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><link rel="shortcut icon" href="/favicon.ico" type="imag
...[SNIP]...

8.2. https://www.seriousgameplay.com/register.asp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.seriousgameplay.com
Path:   /register.asp

Request

GET /register.asp HTTP/1.1
Host: www.seriousgameplay.com
Connection: keep-alive
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: __utmz=41989927.1293356350.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=41989927.727380761.1293356350.1293356350.1293644579.2; %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM; %5Fkey1=870557771

Response

HTTP/1.1 200 OK
Date: Wed, 29 Dec 2010 22:08:54 GMT
Server: Microsoft-IIS/6.0
P3P: CP="NOI DSP COR NID"
X-Powered-By: ASP.NET
Content-Length: 50331
Content-Type: text/html
Set-Cookie: %5Fkey1=870557771; expires=Fri, 31-Jan-2025 05:00:00 GMT; path=/
Set-Cookie: %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM; expires=Fri, 31-Jan-2025 05:00:00 GMT; path=/
Set-Cookie: ASPSESSIONIDCCRBARTC=DCPELEKBLHKKDFCJMHMJDLLJ; path=/
Cache-control: private

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><link rel="shortcut icon" href="/favicon.ico" type="imag
...[SNIP]...

8.3. https://www.seriousgameplay.com/sbg.asp  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.seriousgameplay.com
Path:   /sbg.asp

Request

GET /sbg.asp HTTP/1.1
Host: www.seriousgameplay.com
Connection: keep-alive
Referer: https://www.seriousgameplay.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.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: __utmz=41989927.1293356350.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=41989927.727380761.1293356350.1293356350.1293644579.2; ASPSESSIONIDCCRBARTC=DCPELEKBLHKKDFCJMHMJDLLJ; %5Fkey1=870557771; %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM

Response

HTTP/1.1 200 OK
Date: Wed, 29 Dec 2010 22:09:45 GMT
Server: Microsoft-IIS/6.0
P3P: CP="NOI DSP COR NID"
X-Powered-By: ASP.NET
Content-Length: 37435
Content-Type: text/html
Set-Cookie: %5Fkey2=12%2F25%2F2010+10%3A40%3A21+PM; expires=Fri, 31-Jan-2025 05:00:00 GMT; path=/
Set-Cookie: %5Fkey1=870557771; expires=Fri, 31-Jan-2025 05:00:00 GMT; path=/
Cache-control: private

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><link rel="shortcut icon" href="/favicon.ico" type="imag
...[SNIP]...

9. SSL certificate  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   https://www.seriousgameplay.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:  www.seriousgameplay.com
Issued by:  Go Daddy Secure Certification Authority
Valid from:  Tue Jul 07 14:36:58 CDT 2009
Valid to:  Sat May 28 16:44:14 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:  http://www.valicert.com/
Valid from:  Tue Jun 29 12:06:20 CDT 2004
Valid to:  Sat Jun 29 12:06:20 CDT 2024

Certificate chain #3

Issued to:  http://www.valicert.com/
Issued by:  http://www.valicert.com/
Valid from:  Fri Jun 25 19:19:54 CDT 1999
Valid to:  Tue Jun 25 19:19:54 CDT 2019

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 Thu Dec 30 20:38:49 CST 2010.