Microsoft is investigating a reported vulnerability in its ASP.NET that could allow an attacker to bypass security features on a Web server and view sensitive content, the company said Thursday.
The company published an advisory for Web site administrators on the vulnerability on Tuesday and provided instructions for mitigating the effects of the hole, which is in a component of ASP.NET called the "canonicalization routine." Attackers could create URLs (uniform resource locators) that are specially designed to exploit the flaw, enabling them to bypass authentication or Windows authorization on Web applications that use ASP.NET, Microsoft said.
ASP.NET is the latest version of Microsoft's Active Server Page (ASP) technology, which allows developers to create Web-based applications by embedding small programs, written in a variety of languages such as Visual Basic, Perl and C#, in Web pages, which are then transmitted to users.
The canonicalization routine is a process that interprets URL requests for content on a Web server and determines the proper way to respond for those requests. For example, there is more than one way to refer to the location of a file, such as homepage.html, on a Web server. The canonicalization routine interprets the information in a URL to determine what page the URL is asking for, according to information on the Microsoft Web page.
The vulnerability affects all versions of ASP.NET, including versions running on Windows 2000, Windows 2000 Server, XP Professional and Windows Server 2003, Microsoft said. (See: http://www.microsoft.com/security/incident/aspnet.mspx.)
On Thursday, Microsoft released a small software module called the Microsoft ASP.NET ValidatePath module (VPModule.msi) that can be applied to Internet Information Server 5.0, 5.1 or 6.0 Web servers and will prevent exploitation of the ASP.NET vulnerability. The company is also working on a security patch for the vulnerability, it said.
The company also recommended that Web site owners review its knowledge base for suggestions on ways to program checks for problems with URL canonicalization. (See: http://support.microsoft.com/?kbid=887459.)