CVE-1999-0238: Critical severity PHP PHP vulnerability
php.cgi allows attackers to read any file on the system.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Remove
Remove
PHP (php.cgi)from your environment.Uninstall or remove the php.cgi CGI binary/handler from affected systems or remove any webserver configuration that exposes php.cgi to HTTP requests.
- Configuration
Disable the php.cgi handler or disable CGI execution of PHP scripts in the web server configuration (remove AddHandler/Action directives or equivalent) so php.cgi is not invoked by HTTP requests.
Web server php CGI handler / CGI execution for .php = disabled - Compensating control
If php.cgi cannot immediately be removed or disabled, block or restrict access to php.cgi endpoints using network controls (firewall, reverse proxy, or web application firewall) so only trusted management IPs can reach it.
Event History
Frequently Asked Questions
What is the severity of CVE-1999-0238?
CVE-1999-0238 is considered a critical vulnerability due to its ability to allow unauthorized file access on the system.
How do I fix CVE-1999-0238?
To fix CVE-1999-0238, upgrade to a patched version of PHP that addresses this vulnerability.
What software versions are affected by CVE-1999-0238?
CVE-1999-0238 affects PHP versions 1.0, 2.0, and 2.0b10.
What type of attack can exploit CVE-1999-0238?
CVE-1999-0238 can be exploited to read any file on the system, leading to potential data exposure.
Is CVE-1999-0238 still relevant today?
CVE-1999-0238 is largely considered outdated, but it serves as a historical example of file access vulnerabilities.