# CVE-2012-2688: Integer overflow in n/a

> An unspecified overflow in PHP's stream implementation allows remote attackers to cause unknown impacts, requiring an upgrade to patched versions.

- **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:** 20 Jul 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-5xf9-hrqg-23cp

## What is CVE-2012-2688?

CVE-2012-2688 is a critical vulnerability in Php Php, published on 20 Jul 2012. It can be exploited over the network.

### Official description

Unspecified vulnerability in the _php_stream_scandir function in the stream implementation in PHP before 5.3.15 and 5.4.x before 5.4.5 has unknown impact and remote attack vectors, related to an "overflow."

## Which versions are affected by CVE-2012-2688?

It affects 1 product.


Products: Php Php.

## How do I fix CVE-2012-2688?

Upgrade to a fixed version.

## Is CVE-2012-2688 being exploited?

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

Public exploit code:

- A CVE-2012-2688 shell (github_poc): https://github.com/shelld3v/CVE-2012-2688

## Other vulnerabilities in Php Php

- [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)
- [CVE-2008-2050](https://insights.sbomify.com/CVE-2008-2050/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-2688 and fix it if it is affected.

What it is: CVE-2012-2688 is a critical vulnerability in Php Php, published on 20 Jul 2012. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2012-2688 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-2012-2688/ (Markdown: https://insights.sbomify.com/CVE-2012-2688/index.md)
```

## Sources

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

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