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

> Attackers can force trusted applets to run in vulnerable older JRE versions, enabling code execution via user interaction.

- **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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 25 Mar 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-q538-87mq-rwpp

## What is CVE-2009-1105?

CVE-2009-1105 is a high-severity vulnerability in n/a, published on 25 Mar 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 Plug-in in Java SE Development Kit (JDK) and Java Runtime Environment (JRE) 6 Update 12, 11, and 10 allows user-assisted remote attackers to cause a trusted applet to run in an older JRE version, which can be used to exploit vulnerabilities in that older version, aka CR 6706490.

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

It affects 1 product.


Products: Sun Java.

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

Upgrade to a fixed version.

## Is CVE-2009-1105 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-0887](https://insights.sbomify.com/CVE-2010-0887/): Other in n/a (critical 10.0)
- [CVE-2005-2529](https://insights.sbomify.com/CVE-2005-2529/): Privilege escalation in n/a (critical 10.0)
- [CVE-2005-2530](https://insights.sbomify.com/CVE-2005-2530/): Privilege escalation in n/a (critical 10.0)
- [CVE-2008-3440](https://insights.sbomify.com/CVE-2008-3440/): Code injection in n/a (high 7.5)
- [CVE-2009-1102](https://insights.sbomify.com/CVE-2009-1102/): Code injection in n/a (medium 6.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-1105 is a high-severity vulnerability in n/a, published on 25 Mar 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-1105 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-1105/ (Markdown: https://insights.sbomify.com/CVE-2009-1105/index.md)
```

## Sources

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

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