# CVE-2010-4469: Memory corruption in n/a

> Remote attackers can execute arbitrary code or cause denial of service via malicious Java applets or Web Start applications exploiting a HotSpot memory corruption flaw.

- **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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 17 Feb 2011
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-34fq-m8qx-w3x4

## What is CVE-2010-4469?

CVE-2010-4469 is a critical memory corruption vulnerability in Sun Jdk, published on 17 Feb 2011. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Unspecified vulnerability in the Java Runtime Environment (JRE) in Oracle Java SE and Java for Business 6 Update 23 and earlier, 5.0 Update 27 and earlier, and 1.4.2_29 and earlier allows remote untrusted Java Web Start applications and untrusted Java applets to affect confidentiality, integrity, and availability via unknown vectors related to HotSpot.  NOTE: the previous information was obtained from the February 2011 CPU.  Oracle has not commented on claims from a downstream vendor that this issue is heap corruption related to the Verifier and "backward jsrs."

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

It affects 3 products.


Products: Sun Jdk, Sun Jre, Sun Sdk.

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

Upgrade to a fixed version.

## Is CVE-2010-4469 being exploited?

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

What it is: CVE-2010-4469 is a critical memory corruption vulnerability in Sun Jdk, published on 17 Feb 2011. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2010-4469 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-2010-4469/ (Markdown: https://insights.sbomify.com/CVE-2010-4469/index.md)
```

## Sources

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

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