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).
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.
The value of the APIKey request parameter is copied into the HTML document as plain text between tags. The payload 1f91e<script>alert(1)</script>b4240fbabeb was submitted in the APIKey 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 /socialize.getUserInfo?format=jsonp&sdk=js&APIKey=1f91e<script>alert(1)</script>b4240fbabeb&enabledProviders=facebook%2Ctwitter%2Cyahoo%2Cmessenger%2Cgoogle%2Cmyspace&authMode=cookie&login_token=LT1_wYGVkkgCTuOFWv1NpFDEqA%3D%3D&retryPossible=false&callback=gigya.global.JPCMD.prototype.hanldeJPResponse&context=R1294454197214_0.5199622627023057&state=R1294454197214_0.5199622627023057 HTTP/1.1 Accept: */* Referer: http://msn.foxsports.com/ Accept-Language: en-US User-Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0) Accept-Encoding: gzip, deflate Host: socialize.gigya.com Connection: Keep-Alive Cookie: gcid=lanzMmg8ThR82hvFr2NHy0RwRgCH1h3N3MyTqetgjdM=
Response
HTTP/1.1 200 OK Cache-Control: private Connection: close Date: Sat, 08 Jan 2011 02:53:26 GMT Content-Type: text/javascript; charset=utf-8 Server: Microsoft-IIS/6.0 x-server: web503 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 X-XSS-Protection: 0 X-Timing: total=0 Vary: Accept-Encoding Content-Length: 376
The value of the callback request parameter is copied into the HTML document as plain text between tags. The payload ccd71<script>alert(1)</script>703e057ce8f was submitted in the callback 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 /socialize.getUserInfo?format=jsonp&sdk=js&APIKey=2_0mDflAmB2Uw-8uIvNcQDq7cV0-R4xz_-VK9rOU18T-Jc_50uceVqQUddE55Vkw25&enabledProviders=facebook%2Ctwitter%2Cyahoo%2Cmessenger%2Cgoogle%2Cmyspace&authMode=cookie&login_token=LT1_wYGVkkgCTuOFWv1NpFDEqA%3D%3D&retryPossible=false&callback=gigya.global.JPCMD.prototype.hanldeJPResponseccd71<script>alert(1)</script>703e057ce8f&context=R1294454197214_0.5199622627023057&state=R1294454197214_0.5199622627023057 HTTP/1.1 Accept: */* Referer: http://msn.foxsports.com/ Accept-Language: en-US User-Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0) Accept-Encoding: gzip, deflate Host: socialize.gigya.com Connection: Keep-Alive Cookie: gcid=lanzMmg8ThR82hvFr2NHy0RwRgCH1h3N3MyTqetgjdM=
Response
HTTP/1.1 200 OK Cache-Control: private Connection: close Date: Sat, 08 Jan 2011 02:53:39 GMT Content-Type: text/javascript; charset=utf-8 Server: Microsoft-IIS/6.0 x-server: web503 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 X-XSS-Protection: 0 X-Timing: total=0 Vary: Accept-Encoding Content-Length: 625
The value of the context request parameter is copied into the HTML document as plain text between tags. The payload 14a25<script>alert(1)</script>a7e95064a77 was submitted in the context 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 /socialize.getUserInfo?format=jsonp&sdk=js&APIKey=2_0mDflAmB2Uw-8uIvNcQDq7cV0-R4xz_-VK9rOU18T-Jc_50uceVqQUddE55Vkw25&enabledProviders=facebook%2Ctwitter%2Cyahoo%2Cmessenger%2Cgoogle%2Cmyspace&authMode=cookie&login_token=LT1_wYGVkkgCTuOFWv1NpFDEqA%3D%3D&retryPossible=false&callback=gigya.global.JPCMD.prototype.hanldeJPResponse&context=R1294454197214_0.519962262702305714a25<script>alert(1)</script>a7e95064a77&state=R1294454197214_0.5199622627023057 HTTP/1.1 Accept: */* Referer: http://msn.foxsports.com/ Accept-Language: en-US User-Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0) Accept-Encoding: gzip, deflate Host: socialize.gigya.com Connection: Keep-Alive Cookie: gcid=lanzMmg8ThR82hvFr2NHy0RwRgCH1h3N3MyTqetgjdM=
Response
HTTP/1.1 200 OK Cache-Control: private Connection: close Date: Sat, 08 Jan 2011 02:53:42 GMT Content-Type: text/javascript; charset=utf-8 Server: Microsoft-IIS/6.0 x-server: web503 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 X-XSS-Protection: 0 X-Timing: total=0 Vary: Accept-Encoding Content-Length: 625
The application publishes a Flash cross-domain policy which allows access from any domain.
Allowing access from all domains means that any domain can perform two-way interaction with this application. Unless the application consists entirely of unprotected public content, this policy is likely to present a significant security risk.
Issue background
The Flash cross-domain policy controls whether Flash client components running on other domains can perform two-way interaction with the domain which publishes the policy. If another domain is allowed by the policy, then that domain can potentially attack users of the application. If a user is logged in to the application, and visits a domain allowed by the policy, then any malicious content running on that domain can potentially gain full access to the application within the security context of the logged in user.
Even if an allowed domain is not overtly malicious in itself, security vulnerabilities within that domain could potentially be leveraged by a third-party attacker to exploit the trust relationship and attack the application which allows access.
Issue remediation
You should review the domains which are allowed by the Flash cross-domain policy and determine whether it is appropriate for the application to fully trust both the intentions and security posture of those domains.
Request
GET /crossdomain.xml HTTP/1.0 Host: socialize.gigya.com
Response
HTTP/1.1 200 OK Content-Length: 341 Content-Type: text/xml Last-Modified: Tue, 08 Sep 2009 07:27:09 GMT Accept-Ranges: bytes ETag: "c717c7c65530ca1:1b30" Server: Microsoft-IIS/6.0 x-server: web503 X-Powered-By: ASP.NET Date: Sat, 08 Jan 2011 02:53:09 GMT Connection: close
The format parameter appears to be vulnerable to XML injection. The payload ]]>> was appended to the value of the format parameter. The application's response indicated that this input may have caused an error within a server-side XML or SOAP parser, suggesting that the input has been inserted into an XML document or SOAP message without proper sanitisation.
Issue background
XML or SOAP injection vulnerabilities arise when user input is inserted into a server-side XML document or SOAP message in an unsafe way. It may be possible to use XML metacharacters to modify the structure of the resulting XML. Depending on the function in which the XML is used, it may be possible to interfere with the application's logic, to perform unauthorised actions or access sensitive data.
This kind of vulnerability can be difficult to detect and exploit remotely; you should review the application's response, and the purpose which the relevant input performs within the application's functionality, to determine whether it is indeed vulnerable.
Issue remediation
The application should validate or sanitise user input before incorporating it into an XML document or SOAP message. It may be possible to block any input containing XML metacharacters such as < and >. Alternatively, these characters can be replaced with the corresponding entities: < and >.
Request
GET /socialize.getUserInfo?format=jsonp]]>>&sdk=js&APIKey=2_0mDflAmB2Uw-8uIvNcQDq7cV0-R4xz_-VK9rOU18T-Jc_50uceVqQUddE55Vkw25&enabledProviders=facebook%2Ctwitter%2Cyahoo%2Cmessenger%2Cgoogle%2Cmyspace&authMode=cookie&login_token=LT1_wYGVkkgCTuOFWv1NpFDEqA%3D%3D&retryPossible=false&callback=gigya.global.JPCMD.prototype.hanldeJPResponse&context=R1294454197214_0.5199622627023057&state=R1294454197214_0.5199622627023057 HTTP/1.1 Accept: */* Referer: http://msn.foxsports.com/ Accept-Language: en-US User-Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0) Accept-Encoding: gzip, deflate Host: socialize.gigya.com Connection: Keep-Alive Cookie: gcid=lanzMmg8ThR82hvFr2NHy0RwRgCH1h3N3MyTqetgjdM=
Response
HTTP/1.1 200 OK Cache-Control: private Connection: close Date: Sat, 08 Jan 2011 02:53:21 GMT Content-Type: text/XML; charset=utf-8 Server: Microsoft-IIS/6.0 x-server: web503 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 X-XSS-Protection: 0 X-Timing: total=0 Vary: Accept-Encoding Content-Length: 902
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 /socialize.getUserInfo?format=jsonp&sdk=js&APIKey=2_0mDflAmB2Uw-8uIvNcQDq7cV0-R4xz_-VK9rOU18T-Jc_50uceVqQUddE55Vkw25&siteUID=p%2Fk94ON71KoD%2FEYqOMDzIDg%3D%3D&getUserInfoFor=notifyLogin&_operation=notifyLogin&authMode=cookie&login_token=LT1_wYGVkkgCTuOFWv1NpFDEqA%3D%3D&retryPossible=false&UIDTimestamp=1294446846&UIDSig=TlgMJALQw3pBL46xw0cyS0pwfz4%3D&callback=gigya.global.JPCMD.prototype.hanldeJPResponse&context=R1294446880774_0.16063666529549003&state=R1294446880774_0.16063666529549003 HTTP/1.1 Accept: */* Referer: https://s.foxsports.com/account/transition?fu=http%3A%2F%2Fmsn.foxsports.com%2F&initiatingAction=login&secure=true&egs=TlgMJALQw3pBL46xw0cyS0pwfz4%3D&ts=1294446846&esefsuid=p%2Fk94ON71KoD%2FEYqOMDzIDg%3D%3D Accept-Language: en-US User-Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0) Accept-Encoding: gzip, deflate Host: socialize.gigya.com Connection: Keep-Alive Cookie: gcid=lanzMmg8ThR82hvFr2NHy0RwRgCH1h3N3MyTqetgjdM=
Response
HTTP/1.1 200 OK Cache-Control: private Connection: close Date: Sat, 08 Jan 2011 00:34:13 GMT Content-Type: text/javascript; charset=utf-8 Server: Microsoft-IIS/6.0 x-server: web506 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 X-XSS-Protection: 0 X-Timing: db=15,total=15 Vary: Accept-Encoding Content-Length: 585
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Issue background
If the secure flag is set on a cookie, then browsers will not submit the cookie in any requests that use an unencrypted HTTP connection, thereby preventing the cookie from being trivially intercepted by an attacker monitoring network traffic. If the secure flag is not set, then the cookie will be transmitted in clear-text if the user visits any HTTP URLs within the cookie's scope. An attacker may be able to induce this event by feeding a user suitable links, either directly or via another web site. Even if the domain which issued the cookie does not host any content that is accessed over HTTP, an attacker may be able to use links of the form http://example.com:443/ to perform the same attack.
Issue remediation
The secure flag should be set on all cookies that are used for transmitting sensitive data when accessing content over HTTPS. If cookies are used to transmit session tokens, then areas of the application that are accessed over HTTPS should employ their own session handling mechanism, and the session tokens used should never be transmitted over unencrypted communications.
Request
GET /socialize.notifyLogin?format=jsonp&sdk=js&APIKey=2_0mDflAmB2Uw-8uIvNcQDq7cV0-R4xz_-VK9rOU18T-Jc_50uceVqQUddE55Vkw25&siteUID=p%2Fk94ON71KoD%2FEYqOMDzIDg%3D%3D&authMode=cookie&retryPossible=false&UIDTimestamp=1294446846&UIDSig=TlgMJALQw3pBL46xw0cyS0pwfz4%3D&callback=gigya.global.JPCMD.prototype.hanldeJPResponse&context=R1294446880511_0.4017471218878082&state=R1294446880511_0.4017471218878082 HTTP/1.1 Accept: */* Accept-Language: en-US User-Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0) Accept-Encoding: gzip, deflate Referer: https://s.foxsports.com/account/transition?fu=http%3A%2F%2Fmsn.foxsports.com%2F&initiatingAction=login&secure=true&egs=TlgMJALQw3pBL46xw0cyS0pwfz4%3D&ts=1294446846&esefsuid=p%2Fk94ON71KoD%2FEYqOMDzIDg%3D%3D Host: socialize.gigya.com Connection: Keep-Alive
The cookie does not appear to contain a session token, which may reduce 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 /socialize.notifyLogin?format=jsonp&sdk=js&APIKey=2_0mDflAmB2Uw-8uIvNcQDq7cV0-R4xz_-VK9rOU18T-Jc_50uceVqQUddE55Vkw25&siteUID=p%2Fk94ON71KoD%2FEYqOMDzIDg%3D%3D&authMode=cookie&retryPossible=false&UIDTimestamp=1294446846&UIDSig=TlgMJALQw3pBL46xw0cyS0pwfz4%3D&callback=gigya.global.JPCMD.prototype.hanldeJPResponse&context=R1294446880511_0.4017471218878082&state=R1294446880511_0.4017471218878082 HTTP/1.1 Accept: */* Accept-Language: en-US User-Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0) Accept-Encoding: gzip, deflate Referer: https://s.foxsports.com/account/transition?fu=http%3A%2F%2Fmsn.foxsports.com%2F&initiatingAction=login&secure=true&egs=TlgMJALQw3pBL46xw0cyS0pwfz4%3D&ts=1294446846&esefsuid=p%2Fk94ON71KoD%2FEYqOMDzIDg%3D%3D Host: socialize.gigya.com Connection: Keep-Alive
The server presented a valid, trusted SSL certificate. This issue is purely informational.
The server presented the following certificates:
Server certificate
Issued to:
*.gigya.com
Issued by:
Go Daddy Secure Certification Authority
Valid from:
Thu Nov 04 10:50:30 CDT 2010
Valid to:
Sun Nov 04 09:50:30 CST 2012
Certificate chain #1
Issued to:
Go Daddy Secure Certification Authority
Issued by:
Go Daddy Class 2 Certification Authority
Valid from:
Wed Nov 15 19:54:37 CST 2006
Valid to:
Sun Nov 15 19:54:37 CST 2026
Certificate chain #2
Issued to:
Go Daddy Class 2 Certification Authority
Issued by:
http://www.valicert.com/
Valid from:
Tue Jun 29 12:06:20 CDT 2004
Valid to:
Sat Jun 29 12:06:20 CDT 2024
Certificate chain #3
Issued to:
http://www.valicert.com/
Issued by:
http://www.valicert.com/
Valid from:
Fri Jun 25 19:19:54 CDT 1999
Valid to:
Tue Jun 25 19:19:54 CDT 2019
Issue background
SSL helps to protect the confidentiality and integrity of information in transit between the browser and server, and to provide authentication of the server's identity. To serve this purpose, the server must present an SSL certificate which is valid for the server's hostname, is issued by a trusted authority and is valid for the current date. If any one of these requirements is not met, SSL connections to the server will not provide the full protection for which SSL is designed.
It should be noted that various attacks exist against SSL in general, and in the context of HTTPS web connections. It may be possible for a determined and suitably-positioned attacker to compromise SSL connections without user detection even when a valid SSL certificate is used.Report generated by Unforgivable Vulnerabilities, DORK Search, Exploit Research at Fri Jan 07 21:05:09 CST 2011.