April 28, 2003
A vulnerability has been discovered in the mod_auth_any Apache module. The problem occurs due to insufficient sanitiziation of user-supplied arguments. As a result, it may be possible for an attacker to execute arbitrary commands, by placing shell metacharacters within an argument. All commands executed in this manner would be run with the privileges the Apache HTTPD server.
- mod_auth_any mod_auth_any 1.2.2
Block external access at the network boundary, unless external parties require service.
Restrict remote access to the Apache server from all but trusted hosts. This may limit attempts to exploit this and other latent vulnerabilities.
Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Malicious network activity may be indicated by network-based intrusion detection systems. Audit IDS and web server logs regularly to identify potential attacks.
Run all software as a nonprivileged user with minimal access rights.
Where possible, run the Apache server with privilege separation enabled. This may limit the consequences of an attacker exploiting this condition to execute arbitrary code.
Sun Microsystems has released a patch to address this issue. Red Hat has released a security advisory (RHSA-2003:114-09) containing fixes which address this issue. Further information on how to obtain and apply fixes can be found in the attached advisory.
The discovery of this vulnerability has been credited to Daniel Jarboe and Maneesh Sahani.
© 1995- Symantec Corporation
Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from firstname.lastname@example.org.
The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.
Symantec, Symantec products, Symantec Security Response, and email@example.com are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.