# CVE-2009-2723: Deserialization in n/a

> Unspecified deserialization vulnerability in Sun Java SE Provider class allows unknown impact, requiring an upgrade to a patched version.

- **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:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 10 Aug 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5f46-9784-q9xr

## What is CVE-2009-2723?

CVE-2009-2723 is a critical unsafe deserialization vulnerability in n/a, published on 10 Aug 2009. 

### Official description

Unspecified vulnerability in deserialization in the Provider class in Sun Java SE 5.0 before Update 20 has unknown impact and attack vectors, aka BugId 6444262.

## Which versions are affected by CVE-2009-2723?

It affects 1 product.


Products: Sun Java Se.

## How do I fix CVE-2009-2723?

Upgrade to a fixed version.

## Is CVE-2009-2723 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-2476](https://insights.sbomify.com/CVE-2009-2476/): Privilege escalation in n/a (critical 10.0)
- [CVE-2009-2689](https://insights.sbomify.com/CVE-2009-2689/): Security feature bypass in n/a (critical 10.0)
- [CVE-2009-2721](https://insights.sbomify.com/CVE-2009-2721/): Other in n/a (critical 10.0)
- [CVE-2009-2722](https://insights.sbomify.com/CVE-2009-2722/): Other in n/a (critical 10.0)
- [CVE-2009-2724](https://insights.sbomify.com/CVE-2009-2724/): Race condition in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-2723 and fix it if it is affected.

What it is: CVE-2009-2723 is a critical unsafe deserialization vulnerability in n/a, published on 10 Aug 2009. 
Exploitation: There is no known exploitation of CVE-2009-2723 in the wild and no public exploit code.

Affected product: n/a. 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-2009-2723/ (Markdown: https://insights.sbomify.com/CVE-2009-2723/index.md)
```

## Sources

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

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