webranking.eu, trace.axd, CWE-200, Information Exposure

Information Exposure, trace.axd available in webranking.eu | Vulnerability Crawler Report

Report generated by XSS.CX at Fri Dec 31 13:52:39 CST 2010.

Contents

Loading

1. ASP.NET tracing enabled

2. Cross-domain Referer leakage

3. Cross-domain script include

4. Private IP addresses disclosed

5. Robots.txt file


1. ASP.NET tracing enabled  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.webranking.eu
Path:   /trace.axd

Issue detail

ASP.NET tracing appears to be enabled at the application level.

Issue background

ASP.NET tracing is a debugging feature which is designed for use during development to help troubleshoot problems. It discloses sensitive information to users, and if enabled in production contexts may present a serious security threat.

Application-level tracing enables any user to retrieve full details about recent requests to the application, including those of other users. This information includes session tokens and request parameters, which may enable an attacker to compromise other users and even take control of the entire application.

Page-level tracing returns the same information, but relating only to the current request. This may still contain sensitive data in session and server variables which would be of use to an attacker.

Issue remediation

To disable tracing, open the Web.config file for the application, and find the <trace> element within the <system.web> section. Either set the enabled attribute to "false" (to disable tracing) or set the localOnly attribute to "true" (to enable tracing only on the server itself).

Note that even with tracing disabled in this way, it is possible for individual pages to turn on page-level tracing either within the Page directive of the ASP.NET page, or programmatically through application code. If you observe tracing output only on some application pages, you should review the page source and the code behind, to find the reason why tracing is occurring.

It is strongly recommended that you refer to your platform's documentation relating to this issue, and do not rely solely on the above remediation.

Request

GET /trace.axd HTTP/1.0
Host: www.webranking.eu

Response

HTTP/1.1 200 OK
Connection: close
Date: Fri, 31 Dec 2010 19:18:29 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 5047

...<html>
<head>
<style type="text/css">
span.tracecontent b { color:white }
span.tracecontent { background-color:white; color:black;font: 10pt verdana, arial; }
span.tracecontent table { clear:l
...[SNIP]...
<body>
<span class="tracecontent">
<table cellspacing="0" cellpadding="0" border="0" width="100%">
...[SNIP]...
2. Cross-domain Referer leakage  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.webranking.eu
Path:   /news-and-articles/Articles/2010/HH-Webranking-Italy-2010/

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 /news-and-articles/Articles/2010/HH-Webranking-Italy-2010/?home_2010_en_tab=editorial HTTP/1.1
Host: www.webranking.eu
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
Connection: close
Date: Fri, 31 Dec 2010 19:18:27 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Set-Cookie: ASP.NET_SessionId=xsglqoqyakjr5t45rv4jsnv3; path=/; HttpOnly
Cache-Control: private
Expires: Thu, 30 Dec 2010 19:18:27 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 39398

...
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="sv">
<head><title>
   H&amp;H Webra
...[SNIP]...
<!-- #Wezz Share -->
<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.4.4/jquery.min.js"></script>
...[SNIP]...
<li><a class="no-padding" id="_lpChatBtn" onclick="lpButtonCTTUrl = 'http://server.iad.liveperson.net/hc/64849991/?cmd=file&amp;file=visitorWantsToChat&amp;site=64849991&amp;imageUrl=http://www.webranking.eu/images/LivePerson&amp;referrer='+escape(document.location); lpButtonCTTUrl = (typeof(lpAppendVisitorCookies) != 'undefined' ? lpAppendVisitorCookies(lpButtonCTTUrl) : lpButtonCTTUrl); window.open(lpButtonCTTUrl,'chat64849991','width=475,height=400,resizable=yes');return false;" href="http://server.iad.liveperson.net/hc/64849991/?cmd=file&amp;file=visitorWantsToChat&amp;site=64849991&amp;byhref=1&amp;imageUrl=http://www.webranking.eu/Templates/Styles/Skins/webranking" target="chat64849991"><img alt="" src="http://server.iad.liveperson.net/hc/64849991/?cmd=repstate&amp;site=64849991&amp;channel=web&amp;&amp;ver=1&amp;imageUrl=http://www.webranking.eu/Templates/Styles/Skins/webranking" border="0" name="hcIcon" /> </a>
...[SNIP]...
3. Cross-domain script include  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.webranking.eu
Path:   /news-and-articles/Articles/2010/HH-Webranking-Italy-2010/

Issue detail

The response dynamically includes the following script from another domain:

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 /news-and-articles/Articles/2010/HH-Webranking-Italy-2010/ HTTP/1.1
Host: www.webranking.eu
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
Connection: close
Date: Fri, 31 Dec 2010 19:18:26 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Set-Cookie: ASP.NET_SessionId=ko2fi345aooqi13rc2r24ffs; path=/; HttpOnly
Cache-Control: private
Expires: Thu, 30 Dec 2010 19:18:26 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 39371

...
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="sv">
<head><title>
   H&amp;H Webra
...[SNIP]...
<!-- #Wezz Share -->
<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.4.4/jquery.min.js"></script>
...[SNIP]...
4. Private IP addresses disclosed  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.webranking.eu
Path:   /Trace.axd

Issue detail

The following RFC 1918 IP address was disclosed in the response:

Issue background

RFC 1918 specifies ranges of IP addresses that are reserved for use in private networks and cannot be routed on the public Internet. Although various methods exist by which an attacker can determine the public IP addresses in use by an organisation, the private addresses used internally cannot usually be determined in the same ways.

Discovering the private addresses used within an organisation can help an attacker in carrying out network-layer attacks aiming to penetrate the organisation's internal infrastructure.

Issue remediation

There is not usually any good reason to disclose the internal IP addresses used within an organisation's infrastructure. If these are being returned in service banners or debug messages, then the relevant services should be configured to mask the private addresses. If they are being used to track back-end servers for load balancing purposes, then the addresses should be rewritten with innocuous identifiers from which an attacker cannot infer any useful information about the infrastructure.

Request

GET /Trace.axd?id=0 HTTP/1.1
Host: www.webranking.eu
Proxy-Connection: keep-alive
Referer: http://www.webranking.eu/trace.axd
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.224 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
Date: Fri, 31 Dec 2010 19:50:58 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 10096

...<html>
<head>
<style type="text/css">
span.tracecontent b { color:white }
span.tracecontent { background-color:white; color:black;font: 10pt verdana, arial; }
span.tracecontent table { clear:l
...[SNIP]...
<td>192.168.10.7</td>
...[SNIP]...
5. Robots.txt file  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.webranking.eu
Path:   /news-and-articles/Articles/2010/HH-Webranking-Italy-2010/

Issue detail

The web server contains a robots.txt file.

Issue background

The file robots.txt is used to give instructions to web robots, such as search engine crawlers, about locations within the web site which robots are allowed, or not allowed, to crawl and index.

The presence of the robots.txt does not in itself present any kind of security vulnerability. However, it is often used to identify restricted or private areas of a site's contents. The information in the file may therefore help an attacker to map out the site's contents, especially if some of the locations identified are not linked from elsewhere in the site. If the application relies on robots.txt to protect access to these areas, and does not enforce proper access control over them, then this presents a serious vulnerability.

Issue remediation

The robots.txt file is not itself a security threat, and its correct use can represent good practice for non-security reasons. You should not assume that all web robots will honour the file's instructions. Rather, assume that attackers will pay close attention to any locations identified in the file. Do not rely on robots.txt to provide any kind of protection over unauthorised access.

Request

GET /robots.txt HTTP/1.0
Host: www.webranking.eu

Response

HTTP/1.1 200 OK
Content-Length: 124
Content-Type: text/plain
Content-Location: http://www.webranking.eu/robots.txt
Last-Modified: Wed, 03 Nov 2010 15:31:26 GMT
Accept-Ranges: bytes
ETag: "21a7e22d6c7bcb1:356"
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Date: Fri, 31 Dec 2010 19:18:28 GMT
Connection: close

# robots.txt
User-agent: *
Disallow: /kwwprojects/
Disallow: /en/kwwprojects/
Sitemap: http://www.halvarsson.se/sitemap
Report generated by XSS.CX at Fri Dec 31 13:52:39 CST 2010.