# CVE-2008-2050: Memory corruption in n/a

> A stack-based buffer overflow in PHP's FastCGI SAPI allows attackers to potentially execute arbitrary code or cause a denial of service.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 5 May 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-w79f-6v3g-v46x

## What is CVE-2008-2050?

CVE-2008-2050 is a critical memory corruption vulnerability in Php Php, published on 5 May 2008. It can be exploited over the network.

### Official description

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

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2008-2050?

It affects 1 product.


Products: Php Php.

## How do I fix CVE-2008-2050?

Upgrade to a fixed version.

## Is CVE-2008-2050 being exploited?

There is no known exploitation of CVE-2008-2050 in the wild and no public exploit code.

## Other vulnerabilities in Php Php

- [CVE-2012-2688](https://insights.sbomify.com/CVE-2012-2688/): Integer overflow in n/a (critical 10.0)
- [CVE-2012-2376](https://insights.sbomify.com/CVE-2012-2376/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-3268](https://insights.sbomify.com/CVE-2011-3268/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-4143](https://insights.sbomify.com/CVE-2009-4143/): Other in n/a (critical 10.0)
- [CVE-2008-5557](https://insights.sbomify.com/CVE-2008-5557/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-2050 and fix it if it is affected.

What it is: CVE-2008-2050 is a critical memory corruption vulnerability in Php Php, published on 5 May 2008. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2008-2050 in the wild and no public exploit code.

Affected product: Php Php. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2008-2050/ (Markdown: https://insights.sbomify.com/CVE-2008-2050/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2008-2050
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2008-2050
- OSV: https://osv.dev/vulnerability/CVE-2008-2050

---
From sbomify Insights: https://insights.sbomify.com/CVE-2008-2050/
Summaries are generated and may contain mistakes; the official description above is the record.