# CVE-2009-1896: Security feature bypass in n/a

> Attackers can execute arbitrary code by bypassing Java Web Start security restrictions if one trusted JAR is present in a crafted application.

- **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:** No
- **Published:** 10 Aug 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-c7vr-f88h-3fwr

## What is CVE-2009-1896?

CVE-2009-1896 is a critical vulnerability in n/a, published on 10 Aug 2009. 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

The Java Web Start framework in IcedTea in OpenJDK before 1.6.0.0-20.b16.fc10 on Fedora 10, and before 1.6.0.0-27.b16.fc11 on Fedora 11, trusts an entire application when at least one of the listed jar files is trusted, which allows context-dependent attackers to execute arbitrary code without the untrusted-code restrictions via a crafted application, related to NetX.

Weakness: CWE-264

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

It affects 1 product.


Products: Sun Openjdk.

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

No fix has been published for CVE-2009-1896 yet. Limit exposure of the affected software until one is available.

## Is CVE-2009-1896 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-0794](https://insights.sbomify.com/CVE-2009-0794/): Integer overflow in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-1896 is a critical vulnerability in n/a, published on 10 Aug 2009. 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-2009-1896 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-1896/ (Markdown: https://insights.sbomify.com/CVE-2009-1896/index.md)
```

## Sources

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

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