# CVE-2007-2435: Privilege escalation in n/a

> Remote attackers can execute unauthorized actions and escalate privileges via malicious JNLP files in Sun Java Web Start.

- **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:** 2 May 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9ffv-4whq-h9qg

## What is CVE-2007-2435?

CVE-2007-2435 is a critical vulnerability in Sun Jre, published on 2 May 2007. 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

Sun Java Web Start in JDK and JRE 5.0 Update 10 and earlier, and Java Web Start in SDK and JRE 1.4.2_13 and earlier, allows remote attackers to perform unauthorized actions via an application that grants privileges to itself, related to "Incorrect Use of System Classes" and probably related to support for JNLP files.

Weakness: CWE-264

## Which versions are affected by CVE-2007-2435?

It affects 3 products.


Products: Sun Java Enterprise System, Sun Jre, Sun Sdk.

## How do I fix CVE-2007-2435?

Upgrade to a fixed version.

## Is CVE-2007-2435 being exploited?

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

## Other vulnerabilities in Sun Jre

- [CVE-2006-3127](https://insights.sbomify.com/CVE-2006-3127/): Denial of service in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-2435 and fix it if it is affected.

What it is: CVE-2007-2435 is a critical vulnerability in Sun Jre, published on 2 May 2007. 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-2007-2435 in the wild and no public exploit code.

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

## Sources

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

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