radiocentraal.com | CWE-79 | XSS | Hoyt LLC Research

Loading

Cross Site Scripting, XSS, Vulnerability Crawler

Report generated by XSS.CX at Thu Dec 09 21:26:02 CST 2010.

Contents

1. Cross-site scripting (reflected)

2. Cookie without HttpOnly flag set

3. Cross-domain Referer leakage

4. Email addresses disclosed

5. HTML does not specify charset

6. Content type incorrectly stated


1. Cross-site scripting (reflected)  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.radiocentraal.be
Path:   /Realescape/programmatie/133

Issue detail

The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 8dd04"-alert(1)-"4f11f2a3cd9 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 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.

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.

Request

GET /Realescape/programmatie/133?8dd04"-alert(1)-"4f11f2a3cd9=1 HTTP/1.1
Host: www.radiocentraal.be
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: Fri, 10 Dec 2010 02:29:39 GMT
Server: Apache/2.2.14 (Ubuntu)
X-Powered-By: PHP/5.2.14-0.dotdeb.0pw1
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
Set-Cookie: PHPSESSID=ff47cace8f69a1f9daf60f883f37f219; path=/
Set-Cookie: radio_centraal_restyle=standaard; expires=Fri, 17-Dec-2010 02:29:39 GMT; path=/; domain=www.radiocentraal.be
Vary: Accept-Encoding
Connection: close
Content-Type: text/html
Content-Length: 21972

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="nl">

<!--
Copyright:
Op deze website en de broncode berust copyright.
Implementatie van delen va
...[SNIP]...
ax_target_id);
           target_id = sajax_target_id;
           if (typeof(sajax_request_type) == "undefined" || sajax_request_type == "")
               sajax_request_type = "GET";
           
           uri = "/Realescape/programmatie/133?8dd04"-alert(1)-"4f11f2a3cd9=1";
           if (sajax_request_type == "GET") {
           
               if (uri.indexOf("?") == -1)
                   uri += "?rs=" + escape(func_name);
               else
                   uri += "&rs=" + escape(func_name);
               uri += "&rst=" + escape(saja
...[SNIP]...
2. Cookie without HttpOnly flag set  previous  next

Summary

Severity:   Low
Confidence:   Firm
Host:   http://www.radiocentraal.be
Path:   /Realescape/programmatie/133

Issue detail

The following cookies were issued by the application and do not have the HttpOnly flag set:The highlighted cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their 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 /Realescape/programmatie/133 HTTP/1.1
Host: www.radiocentraal.be
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: Fri, 10 Dec 2010 02:29:26 GMT
Server: Apache/2.2.14 (Ubuntu)
X-Powered-By: PHP/5.2.14-0.dotdeb.0pw1
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
Set-Cookie: PHPSESSID=e8af6a78f3c8496226eca1d992fa0538; path=/
Set-Cookie: radio_centraal_restyle=standaard; expires=Fri, 17-Dec-2010 02:29:26 GMT; path=/; domain=www.radiocentraal.be
Vary: Accept-Encoding
Connection: close
Content-Type: text/html
Content-Length: 17253

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="nl">

<!--
Copyright:
Op deze website en de broncode berust copyright.
Implementatie van delen va
...[SNIP]...
3. Cross-domain Referer leakage  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.radiocentraal.be
Path:   /Realescape/programmatie/133

Issue detail

The page was loaded from a URL containing a query string:The response contains the following links to other domains:

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 /Realescape/programmatie/133?8dd04%22-alert(%64%6F%63%75%6D%65%6E%74%2E%63%6F%6F%6B%69%65)-%224f11f2a3cd9=1 HTTP/1.1
Host: www.radiocentraal.be
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
Cookie: PHPSESSID=25cd33a28ca5ae326e1ecd70e7471a6d; radio_centraal_restyle=standaard; __utmz=114653828.1291951448.1.1.utmcsr=burp|utmccn=(referral)|utmcmd=referral|utmcct=/show/3; __utma=114653828.793650327.1291951448.1291951448.1291951448.1; __utmc=114653828; __utmb=114653828.1.10.1291951448

Response

HTTP/1.1 200 OK
Date: Fri, 10 Dec 2010 03:24:40 GMT
Server: Apache/2.2.14 (Ubuntu)
X-Powered-By: PHP/5.2.14-0.dotdeb.0pw1
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-Type: text/html
Content-Length: 22020

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="nl">

<!--
Copyright:
Op deze website en de broncode berust copyright.
Implementatie van delen va
...[SNIP]...
<p class="center"><a href="http://streaming.radiocentraal.org" rel="external" class="transparent_png make_link img_streaming"><img src="http://www.radiocentraal.be/Realescape/style/artwork/homeknopjes/streaming_logo.png" alt="Luister Radio Centraal online!" title="Luister Radio Centraal online!">
...[SNIP]...
<div><a href="http://webgang.radiocentraal.be/" rel="external" class="link_logo"><img src="http://www.radiocentraal.be/Realescape/style/artwork/homeknopjes/webgang_logo.png" alt="Webgang" title="Webgang">
...[SNIP]...
<div><a href="http://redactie.radiocentraal.be/Home/" rel="external" class="link_logo"><img src="http://www.radiocentraal.be/Realescape/style/artwork/homeknopjes/redactie_logo.png" alt="Redactie" title="Redactie">
...[SNIP]...
<li><a href='http://redactie.radiocentraal.be/Home/?p=964' rel='external'>Verkiezingen Haiti</a>
...[SNIP]...
<li><a href='http://redactie.radiocentraal.be/Home/?p=965' rel='external'>achtergrond BAM/ TV Sam en Noriant</a>
...[SNIP]...
<li><a href='http://redactie.radiocentraal.be/Home/?p=969' rel='external'>Sint Anna, beschermheilige der petrochemie</a>
...[SNIP]...
<li><a href='http://redactie.radiocentraal.be/Home/?p=966' rel='external'>Wikileaks: Over de boodschap en het schieten op de boodschapper</a>
...[SNIP]...
<li><a href='http://redactie.radiocentraal.be/Home/?p=963' rel='external'>Russel Tribunaal over illegale Dexia investeringen in Palestina</a>
...[SNIP]...
<div id="menu_extra">
       <a href="http://redactie.radiocentraal.be/Home/" rel="external" class="link_logo_redactie"><img src="http://www.radiocentraal.be/Realescape/style/artwork/homeknopjes/redactie_logo.png" alt="Redactie" title="Redactie">
...[SNIP]...
4. Email addresses disclosed  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.radiocentraal.be
Path:   /Realescape/functions/functions.js

Issue detail

The following email address was disclosed in the response:

Issue background

The presence of email addresses within application responses does not necessarily constitute a security vulnerability. Email addresses may appear intentionally within contact information, and many applications (such as web mail) include arbitrary third-party email addresses within their core content.

However, email addresses of developers and other individuals (whether appearing on-screen or hidden within page source) may disclose information that is useful to an attacker; for example, they may represent usernames that can be used at the application's login, and they may be used in social engineering attacks against the organisation's personnel. Unnecessary or excessive disclosure of email addresses may also lead to an increase in the volume of spam email received.

Issue remediation

You should review the email addresses being disclosed by the application, and consider removing any that are unnecessary, or replacing personal addresses with anonymous mailbox addresses (such as helpdesk@example.com).

Request

GET /Realescape/functions/functions.js HTTP/1.1
Host: www.radiocentraal.be
Proxy-Connection: keep-alive
Referer: http://www.radiocentraal.be/Realescape/programmatie/133?8dd04%22-alert(1)-%224f11f2a3cd9=1
Accept: */*
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: PHPSESSID=25cd33a28ca5ae326e1ecd70e7471a6d; radio_centraal_restyle=standaard

Response

HTTP/1.1 200 OK
Date: Fri, 10 Dec 2010 03:24:21 GMT
Server: Apache/2.2.14 (Ubuntu)
Last-Modified: Sun, 19 Sep 2010 17:28:42 GMT
ETag: "3c1d65-1572-490a0208b3d39"
Accept-Ranges: bytes
Vary: Accept-Encoding
Content-Type: application/javascript
Content-Length: 5490

/* Licensed public domain
* Script overgenomen van ijbema@xs4all.nl Waarvoor dank
*/

/*
* addLoadEvent based upon this blog article:
*
* http://simon.incutio.com/archive/2004/05/26/addLoadEvent
*/
function addLoadEvent(func) {
   var oldonload = window.onload;
   if
...[SNIP]...
5. HTML does not specify charset  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.radiocentraal.be
Path:   /Realescape/actors/get_current_prog.php

Issue description

If a web response states that it contains HTML content but does not specify a character set, then the browser may analyse the HTML and attempt to determine which character set it appears to be using. Even if the majority of the HTML actually employs a standard character set such as UTF-8, the presence of non-standard characters anywhere in the response may cause the browser to interpret the content using a different character set. This can have unexpected results, and can lead to cross-site scripting vulnerabilities in which non-standard encodings like UTF-7 can be used to bypass the application's defensive filters.

In most cases, the absence of a charset directive 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 HTML content, the application should include within the Content-type header a directive specifying a standard recognised character set, for example charset=ISO-8859-1.

Request

GET /Realescape/actors/get_current_prog.php HTTP/1.1
Host: www.radiocentraal.be
Proxy-Connection: keep-alive
Referer: http://www.radiocentraal.be/Realescape/style/artwork/flashbanner5.swf
Accept: */*
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: PHPSESSID=25cd33a28ca5ae326e1ecd70e7471a6d; radio_centraal_restyle=standaard; __utmz=114653828.1291951448.1.1.utmcsr=burp|utmccn=(referral)|utmcmd=referral|utmcct=/show/3; __utma=114653828.793650327.1291951448.1291951448.1291951448.1; __utmc=114653828; __utmb=114653828.1.10.1291951448

Response

HTTP/1.1 200 OK
Date: Fri, 10 Dec 2010 03:24:29 GMT
Server: Apache/2.2.14 (Ubuntu)
X-Powered-By: PHP/5.2.14-0.dotdeb.0pw1
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-Type: text/html
Content-Length: 162

boventekst_0=Nachtmachine&ondertekst_0=Machine+die+gekke+geluiden+verspreidt+ter+opvrolijking+van+de+nacht+en+eventueel+ook+dag.&progid_0=0&list_length=1&loaded=1
6. Content type incorrectly stated  previous

Summary

Severity:   Information
Confidence:   Firm
Host:   http://www.radiocentraal.be
Path:   /Realescape/actors/get_current_prog.php

Issue detail

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

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 /Realescape/actors/get_current_prog.php HTTP/1.1
Host: www.radiocentraal.be
Proxy-Connection: keep-alive
Referer: http://www.radiocentraal.be/Realescape/style/artwork/flashbanner5.swf
Accept: */*
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: PHPSESSID=25cd33a28ca5ae326e1ecd70e7471a6d; radio_centraal_restyle=standaard; __utmz=114653828.1291951448.1.1.utmcsr=burp|utmccn=(referral)|utmcmd=referral|utmcct=/show/3; __utma=114653828.793650327.1291951448.1291951448.1291951448.1; __utmc=114653828; __utmb=114653828.1.10.1291951448

Response

HTTP/1.1 200 OK
Date: Fri, 10 Dec 2010 03:24:29 GMT
Server: Apache/2.2.14 (Ubuntu)
X-Powered-By: PHP/5.2.14-0.dotdeb.0pw1
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-Type: text/html
Content-Length: 162

boventekst_0=Nachtmachine&ondertekst_0=Machine+die+gekke+geluiden+verspreidt+ter+opvrolijking+van+de+nacht+en+eventueel+ook+dag.&progid_0=0&list_length=1&loaded=1
Report generated by XSS.CX at Thu Dec 09 21:26:02 CST 2010.