# CVE-2005-0836: Privilege escalation in n/a

> Untrusted Java Web Start applications can gain elevated privileges via argument injection in JNLP property tags, requiring user interaction to launch the 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:** 22 Mar 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cm9f-c35v-2642

## What is CVE-2005-0836?

CVE-2005-0836 is a critical vulnerability in n/a, published on 22 Mar 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

Argument injection vulnerability in Java Web Start for J2SE 1.4.2 up to 1.4.2_06 allows untrusted applications to gain privileges via the value parameter of a property tag in a JNLP file.

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

It affects 1 product.


Products: Sun J2se.

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

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

## Is CVE-2005-0836 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-6745](https://insights.sbomify.com/CVE-2006-6745/): Deserialization in n/a (critical 9.3)
- [CVE-2005-0418](https://insights.sbomify.com/CVE-2005-0418/): Privilege escalation in n/a (high 7.5)
- [CVE-2005-1973](https://insights.sbomify.com/CVE-2005-1973/): Privilege escalation in n/a (medium 5.1)
- [CVE-2005-1974](https://insights.sbomify.com/CVE-2005-1974/): Privilege escalation in n/a (medium 5.1)
- [CVE-2006-4302](https://insights.sbomify.com/CVE-2006-4302/): Security feature bypass in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-0836 and fix it if it is affected.

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

## Sources

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

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