# CVE-2010-2225: Use after free in n/a

> Remote attackers can execute arbitrary code or read sensitive information via serialized data due to a use-after-free flaw in PHP's SplObjectStorage unserializer.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Jun 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6xh6-hvhw-h658

## What is CVE-2010-2225?

CVE-2010-2225 is a high-severity use after free vulnerability in Php Php, published on 23 Jun 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Use-after-free vulnerability in the SplObjectStorage unserializer in PHP 5.2.x and 5.3.x through 5.3.2 allows remote attackers to execute arbitrary code or obtain sensitive information via serialized data, related to the PHP unserialize function.

Weakness: CWE-399

## Which versions are affected by CVE-2010-2225?

It affects 1 product.


Products: Php Php.

## How do I fix CVE-2010-2225?

Upgrade to a fixed version.

## Is CVE-2010-2225 being exploited?

There is no known exploitation of CVE-2010-2225 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-2010-2225 and fix it if it is affected.

What it is: CVE-2010-2225 is a high-severity use after free vulnerability in Php Php, published on 23 Jun 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-2225 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-2010-2225/ (Markdown: https://insights.sbomify.com/CVE-2010-2225/index.md)
```

## Sources

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

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