Advisories

CVE-2006-6104: Mono XSP ASP.NET Server sourcecode disclosure

21 December, 2006

Tags: , , ,

CVSS Score
5.0
Confidentiality Impact Partial (There is considerable informational disclosure.)
Integrity Impact None (There is no impact to the integrity of the system)
Availability Impact None (There is no impact to the availability of the system.)
Access Complexity Low (Specialized access conditions or extenuating circumstances do not exist. Very little knowledge or skill is required to exploit. )
Authentication Not required (Authentication is not required to exploit the vulnerability.)
Gained Access None
Vulnerability Type(s)
CWE ID CWE id is not defined for this vulnerability

Version: Tested on mono 1.2.1
XSP for ASP.NET 1.1 and 2.0 (This is a regression as this issue didn’t exists in Mono 1.0)

Discovered by: José Ramón Palanco: jpalanco@gmail.com

Time Line

  • Nov 29, 2006: Discovered security issue by Jose Ramon Palanco
  • Nov 30, 2006: Reported to Mono Project
  • Dec 1, 2006: Patch in subversion rev 68776
  • Dec 5, 2006: Mono is testing the patch and building packages for the fix
  • Dec 19, 2006: Published advisory

Description

Attackers use source code disclosure attacks to try to obtain the source code of server-side applications. The basic role of Web servers is to serve files as requested by clients. Files can be static, such as image and HTML files, or dynamic, such as ASPX, ASHX, ASCX, ASAX, webservices like ASMX files and any language supported by Mono like: C#, boo, nemerle, vb files: .cs, .boo, vb, .n, … When the browser requests a dynamic file, the Web server first executes the file and then returns the result to the browser. Hence, dynamic files are actually code executed on the Web server.

Using a source code disclosure attack, an attacker can retrieve the source code of server-side file. Obtaining the source code of server-side files grants the attacker deeper knowledge of the logic behind the Web application, how the application handles requests and their parameters, the structure of the database, vulnerabilities in the code and source code comments. Having the source code, and possibly a duplicate application to test on, helps the attacker to prepare an attack on the application.

An attacker can cause source code disclosure using adding %20 (space char) after the uri, for example
http://www.server.com/app/Default.aspx%20

Update: is also possible retrieve Web.Config file. This file contains sensible information like credentials.

 

Share with your friends










Submit

Author

Jose Palanco

VP Threat Intelligence at ElevenPaths

Your email address will not be published.