CVE-2008-2050: Buffer Overflow

Published May 5, 2008
·
Updated

Stack-based buffer overflow in the FastCGI SAPI (fastcgi.c) in PHP before 5.2.6 has unknown impact and attack vectors.

Affected Software

25 affected components
PHP PHP=5.1.5
PHP PHP=5.1.2
PHP PHP=5.1.1
PHP PHP=5.0.0-beta1
PHP PHP=5.1.6
PHP PHP=5.2.2
PHP PHP=5.0.5
PHP PHP=5.0.1
PHP PHP=5.1.4
PHP PHP=5.0.4
PHP PHP=5.0.0-rc2
PHP PHP=5.2.3
PHP PHP=5.0.3
PHP PHP=5.1.0
PHP PHP=5.0.0-rc3
PHP PHP<=5.2.5
PHP PHP=5.2.0
PHP PHP=5.2.4
PHP PHP=5.0.0-beta3
PHP PHP=5.1.3
PHP PHP=5.0.0-rc1
PHP PHP=5.0.2
PHP PHP=5.2.1
PHP PHP=5.0.0-beta4
PHP PHP=5.0.0-beta2

Event History

May 5, 2008
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2008-2050?

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.

2

How do I fix CVE-2008-2050?

To fix CVE-2008-2050, upgrade PHP to version 5.2.6 or later.

3

What versions of PHP are affected by CVE-2008-2050?

CVE-2008-2050 affects PHP versions prior to 5.2.6, including versions like 5.1.5, 5.1.2, and earlier.

4

What symptoms indicate an exploitation of CVE-2008-2050?

Symptoms of exploitation are not specified, but a successful attack may result in abnormal behavior or crashes in PHP applications using the FastCGI SAPI.

5

Is there a workaround for CVE-2008-2050 if I cannot update PHP?

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203