AWStats Rawlog Plugin Logfile Parameter Input Validation Vulnerability



Date Discovered

August 16, 2004


AWStats Rawlog Plugin is reported prone to an input validation vulnerability. The issue is reported to exist because user supplied 'logfile' URI data passed to the '' script is not sanitized. An attacker may exploit this condition to execute commands remotely or disclose contents of web server readable files. It should be noted that although this vulnerability is reported to affect AWStats version 6.1, other versions might also be affected.

Technologies Affected

  • AWStats AWStats 5.0.0
  • AWStats AWStats 5.1.0
  • AWStats AWStats 5.2.0
  • AWStats AWStats 5.3.0
  • AWStats AWStats 5.4.0
  • AWStats AWStats 5.5.0
  • AWStats AWStats 5.6.0
  • AWStats AWStats 5.7.0
  • AWStats AWStats 5.8.0
  • AWStats AWStats 5.9.0
  • AWStats AWStats 6.0.0
  • AWStats AWStats 6.1.0
  • AWStats AWStats 6.2.0
  • AWStats AWStats 6.3.0


Block external access at the network boundary, unless external parties require service.
If the service is not required to be globally accessible it is recommended that access be restricted to trusted hosts and networks.

Deploy network intrusion detection systems to monitor network traffic for malicious activity.
It is possible that some attacks that result from this vulnerability may be detected by network intrusion detection systems (NIDS). Web servers, application servers and proxy servers also provide various logging facilities that may include indications of attacks. Audit all applicable logs on a regular basis.

Run all software as a nonprivileged user with minimal access rights.
Running the affected server with the least required privileges by forcing it to drop privileges after acquiring system resources is highly recommended. This may greatly reduce the consequences of successful exploitation.

The vendor has released AWStats 6.4 to address this issue.



Discovery of this vulnerability is credited to K-sPecial.

© 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


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 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.