# CVE-2005-3907: Security feature bypass in n/a

> Remote attackers can escape the Java sandbox via untrusted applets to execute arbitrary code or access files, requiring user interaction to load the applet.

- **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:** No
- **Published:** 30 Nov 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wg5j-8jqj-w57c

## What is CVE-2005-3907?

CVE-2005-3907 is a high-severity vulnerability in Sun Jdk, published on 30 Nov 2005. 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 Java Runtime Environment in Java JDK and JRE 5.0 Update 3 and earlier allows remote attackers to escape the Java sandbox and access arbitrary files or execute arbitrary applications via unknown attack vectors involving untrusted Java applets.

## Which versions are affected by CVE-2005-3907?

It affects 2 products.


Products: Sun Jdk, Sun Jre.

## How do I fix CVE-2005-3907?

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

## Is CVE-2005-3907 being exploited?

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

What it is: CVE-2005-3907 is a high-severity vulnerability in Sun Jdk, published on 30 Nov 2005. 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-2005-3907 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-2005-3907/ (Markdown: https://insights.sbomify.com/CVE-2005-3907/index.md)
```

## Sources

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

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