Apache HTTP Server mod_alias script source information disclosure
| apache-modalias-information-disclosure (28357) |
Description:
Apache HTTP Server could allow a remote attacker to obtain sensitive information caused by a vulnerability in the mod_alias module. A remote attacker could send a URL request for a known script using an upper-case directory name which, when sent to a case-insensitive operating system, would cause the script's source code to be returned.
Platforms Affected:
- Apache, HTTP Server 2.0.58
- Apache, HTTP Server 2.2.2
- Apache, HTTP Server 2.2.3
Remedy:
No remedy available as of July 4, 2009.
Consequences:
Obtain Information
References:
- Apache Web site, Welcome! - The Apache HTTP Server Project at http://httpd.apache.org/.
- BugTraq Mailing List, Wed Aug 09 2006 - 05:15:42 CDT , CGI Script Source Code Disclosure Vulnerability in Apache for Windows at http://archives.neohapsis.com/archives/bugtraq/2006-08/0206.html.
- BID-19447: Apache CGI Script Source Code Information Disclosure Vulnerability
- CVE-2006-4110: Apache 2.2.2, when running on Windows, allows remote attackers to read source code of CGI programs via a request that contains uppercase (or alternate case) characters that bypass the case-sensitive ScriptAlias directive, but allow access to the file on case-insensitive file systems.
- OSVDB ID: 27913: Apache HTTP Server on Windows mod_alias URL Validation Canonicalization CGI Source Disclosure
- SA21490: Apache "mod_alias" URL Validation Canonicalization Vulnerability
- VUPEN/ADV-2006-3265: Apache mod_alias Alias Directive Arguments and URL Handling Vulnerability
Reported:
Aug 09, 2006
The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.
For corrections or additions please email xforce@iss.net
