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

> Remote attackers can execute arbitrary code on Java applications by sending malicious serialized data via LDAP responses.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Mar 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5w5h-m7x5-fq48

## What is CVE-2009-1094?

CVE-2009-1094 is a critical unsafe deserialization vulnerability in Sun Jdk, published on 25 Mar 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unspecified vulnerability in the LDAP implementation in Java SE Development Kit (JDK) and Java Runtime Environment (JRE) 5.0 Update 17 and earlier; 6 Update 12 and earlier; SDK and JRE 1.3.1_24 and earlier; and 1.4.2_19 and earlier allows remote LDAP servers to execute arbitrary code via unknown vectors related to serialized data.

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

It affects 3 products.


Products: Sun Jdk, Sun Jre, Sun Sdk.

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

Upgrade to a fixed version.

## Is CVE-2009-1094 being exploited?

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

## Other vulnerabilities in Sun Jdk

- [CVE-2011-3521](https://insights.sbomify.com/CVE-2011-3521/): Deserialization in n/a (critical 10.0)
- [CVE-2011-3548](https://insights.sbomify.com/CVE-2011-3548/): Other in n/a (critical 10.0)
- [CVE-2011-3549](https://insights.sbomify.com/CVE-2011-3549/): Other in n/a (critical 10.0)
- [CVE-2011-3554](https://insights.sbomify.com/CVE-2011-3554/): Other in n/a (critical 10.0)
- [CVE-2011-0802](https://insights.sbomify.com/CVE-2011-0802/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-1094 is a critical unsafe deserialization vulnerability in Sun Jdk, published on 25 Mar 2009. 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-2009-1094 in the wild and no public exploit code.

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

## Sources

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

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