First published: Mon May 05 2008(Updated: )
Stack-based buffer overflow in the FastCGI SAPI (fastcgi.c) in PHP before 5.2.6 has unknown impact and attack vectors.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
PHP | =5.1.5 | |
PHP | =5.1.2 | |
PHP | =5.1.1 | |
PHP | =5.0.0-beta1 | |
PHP | =5.1.6 | |
PHP | =5.2.2 | |
PHP | =5.0.5 | |
PHP | =5.0.1 | |
PHP | =5.1.4 | |
PHP | =5.0.4 | |
PHP | =5.0.0-rc2 | |
PHP | =5.2.3 | |
PHP | =5.0.3 | |
PHP | =5.1.0 | |
PHP | =5.0.0-rc3 | |
PHP | <=5.2.5 | |
PHP | =5.2.0 | |
PHP | =5.2.4 | |
PHP | =5.0.0-beta3 | |
PHP | =5.1.3 | |
PHP | =5.0.0-rc1 | |
PHP | =5.0.2 | |
PHP | =5.2.1 | |
PHP | =5.0.0-beta4 | |
PHP | =5.0.0-beta2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2008-2050 is not explicitly stated but it involves a stack-based buffer overflow in PHP, which could lead to various potential impacts.
To fix CVE-2008-2050, upgrade PHP to version 5.2.6 or later.
CVE-2008-2050 affects PHP versions prior to 5.2.6, including versions like 5.1.5, 5.1.2, and earlier.
Symptoms of exploitation are not specified, but a successful attack may result in abnormal behavior or crashes in PHP applications using the FastCGI SAPI.
While no specific workaround is mentioned for CVE-2008-2050, limiting access to the affected PHP versions and using additional security measures might help mitigate risks until an update can be applied.