CCBill WhereAmI.CGI Remote Arbitrary Command Execution Vulnerability

Risk
High

Date Discovered
07-03-2003

Description
It has been reported that whereami.cgi distributed by CCBill does not properly handle some types of input. Because of this, an attacker may be able to gain access to a system with the privileges of the web server process.

Components Affected
CCBill whereami.cgi

Recommendations
Block external access at the network boundary, unless service is required by external parties.
Filter network traffic of questionable integrity at border routers and network firewalls. Traffic should be filtered in both directions to prevent unauthorized traffic from entering or escaping network boundaries.

Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Use network intrusion detection systems to monitor network traffic for anomalous activity and alert staff to potential attacks.

Running the server in a closed or restricted environment may limit the consequences of successful exploitation.
Do not execute server software with elevated privileges. Place server processes in restricted or chrooted environments to prevent further compromise of system in the event of successful compromise of the server process.

Currently we are not aware of any vendor-supplied patches for this issue. If you feel we are in error or are aware of more recent information, please mail us at: vuldb@securityfocus.com .

References
Source: Homepage
URL: http://about.ccbill.com/

Credits
Discovery credited to Dayne Jordan.

Copyright (c) 2003 by Symantec Corp.
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 symsecurity@symantec.com.

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