# CVE-2010-3563: Security feature bypass in n/a

> Remote attackers can bypass Java Web Start sandbox restrictions via forged security policies, leading to privilege escalation and potential code execution.

- **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:** 19 Oct 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fj9r-jhxx-vm9v

## What is CVE-2010-3563?

CVE-2010-3563 is a critical vulnerability in Sun Jdk, published on 19 Oct 2010. 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 the Deployment component in Oracle Java SE and Java for Business 6 Update 21 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors. NOTE: the previous information was obtained from the October 2010 CPU. Oracle has not commented on claims from a reliable researcher that this is related to "how Web Start retrieves security policies," BasicServiceImpl, and forged policies that bypass sandbox restrictions.

## Which versions are affected by CVE-2010-3563?

It affects 2 products.


Products: Sun Jdk, Sun Jre.

## How do I fix CVE-2010-3563?

Apply the vendor's patch.

## Is CVE-2010-3563 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-3563 exists.

Public exploit code:

- Sun Java Web Start BasicServiceImpl Code Execution (metasploit)
- Sun Java Web Start BasicServiceImpl - Remote Code Execution (Metasploit) (exploitdb)

## 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-2010-3563 and fix it if it is affected.

What it is: CVE-2010-3563 is a critical vulnerability in Sun Jdk, published on 19 Oct 2010. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-3563 exists.

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-2010-3563/ (Markdown: https://insights.sbomify.com/CVE-2010-3563/index.md)
```

## Sources

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

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