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

> Attackers can bypass Java security policies by exploiting a flaw in the JNLP SecurityManager that fails to throw exceptions, allowing unauthorized ClassLoader instantiation.

- **Severity:** Medium 6.8 (`AV:N/AC:M/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:** 20 Jan 2011
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-g6jh-xpq2-3rw2

## What is CVE-2010-4351?

CVE-2010-4351 is a medium-severity vulnerability in n/a, published on 20 Jan 2011. 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 JNLP SecurityManager in IcedTea (IcedTea.so) 1.7 before 1.7.7, 1.8 before 1.8.4, and 1.9 before 1.9.4 for Java OpenJDK returns from the checkPermission method instead of throwing an exception in certain circumstances, which might allow context-dependent attackers to bypass the intended security policy by creating instances of ClassLoader.

Weakness: CWE-264

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

It affects 1 product.


Products: Redhat Icedtea.

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

Upgrade to a fixed version.

## Is CVE-2010-4351 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-0025](https://insights.sbomify.com/CVE-2011-0025/): Security feature bypass in n/a (medium 6.8)
- [CVE-2010-3860](https://insights.sbomify.com/CVE-2010-3860/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-4351 and fix it if it is affected.

What it is: CVE-2010-4351 is a medium-severity vulnerability in n/a, published on 20 Jan 2011. 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-2010-4351 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-2010-4351/ (Markdown: https://insights.sbomify.com/CVE-2010-4351/index.md)
```

## Sources

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

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