Microsoft IIS Virtual Directory Naming Vulnerability
BID:882
Info
Microsoft IIS Virtual Directory Naming Vulnerability
| Bugtraq ID: | 882 |
| Class: | Failure to Handle Exceptional Conditions |
| CVE: | |
| Remote: | Yes |
| Local: | Yes |
| Published: | Dec 21 1999 12:00AM |
| Updated: | Dec 21 1999 12:00AM |
| Credit: | Reported to Microsoft by Adam Hunger and published in a Microsoft Security Advisory released December 21, 1999. |
| Vulnerable: |
Microsoft Site Server Commerce Edition 3.0 i386 Microsoft Site Server Commerce Edition 3.0 alpha Microsoft IIS 4.0 |
| Not Vulnerable: | |
Discussion
Microsoft IIS Virtual Directory Naming Vulnerability
Server side processing of web pages can be bypassed under a specific set of conditions. If an .asp or similar file resides in a virtual directory whose name ends in a legal extension, the source code of the file may be sent to the client browser.
IIS determines what action to take on a web document by parsing the URL for the filename extension. The first registered extension found in the string is used to make this decision. Therefore, if a request is made for the following file: /webroot/docs.htm/some.asp, and that file exists, IIS will parse the path and find the .htm extension in the virtual directory name docs.htm, determine that no preprocessing is required, and send the unprocessed source of the some.asp file.
Server side processing of web pages can be bypassed under a specific set of conditions. If an .asp or similar file resides in a virtual directory whose name ends in a legal extension, the source code of the file may be sent to the client browser.
IIS determines what action to take on a web document by parsing the URL for the filename extension. The first registered extension found in the string is used to make this decision. Therefore, if a request is made for the following file: /webroot/docs.htm/some.asp, and that file exists, IIS will parse the path and find the .htm extension in the virtual directory name docs.htm, determine that no preprocessing is required, and send the unprocessed source of the some.asp file.
Exploit / POC
Microsoft IIS Virtual Directory Naming Vulnerability
Currently the SecurityFocus staff are not aware of any exploits for this issue. If you feel we are in error or are aware of more recent information, please mail us at: [email protected].
Currently the SecurityFocus staff are not aware of any exploits for this issue. If you feel we are in error or are aware of more recent information, please mail us at: [email protected].
Solution / Fix
Microsoft IIS Virtual Directory Naming Vulnerability
Solution:
Microsoft has released a patch for this issue, available at:
Intel:
http://www.microsoft.com/Downloads/Release.asp?ReleaseID=16378
alpha:
http://www.microsoft.com/Downloads/Release.asp?ReleaseID=16379
The patch changes how IIS parses the URL. After applying the patch, IIS will return an error anytime a file in a virtual directory with a legal extension is requested.
Solution:
Microsoft has released a patch for this issue, available at:
Intel:
http://www.microsoft.com/Downloads/Release.asp?ReleaseID=16378
alpha:
http://www.microsoft.com/Downloads/Release.asp?ReleaseID=16379
The patch changes how IIS parses the URL. After applying the patch, IIS will return an error anytime a file in a virtual directory with a legal extension is requested.
References
Microsoft IIS Virtual Directory Naming Vulnerability
References:
References: