# CVE-2010-0084: Information disclosure in n/a

> Remote attackers can exploit an unspecified vulnerability in the Java Runtime Environment to compromise data confidentiality.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 1 Apr 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-h267-7942-cfp5

## What is CVE-2010-0084?

CVE-2010-0084 is a medium-severity vulnerability in Sun Jdk, published on 1 Apr 2010. An attacker can exploit it over the internet without logging in.

### Official description

Unspecified vulnerability in the Java Runtime Environment component in Oracle Java SE and Java for Business 6 Update 18, 5.0 Update 23, and 1.4.2_25 allows remote attackers to affect confidentiality via unknown vectors, a different vulnerability than CVE-2010-0091.

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

It affects 3 products.


Products: Sun Jdk, Sun Jre, Sun Sdk.

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

Upgrade to a fixed version.

## Is CVE-2010-0084 being exploited?

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

What it is: CVE-2010-0084 is a medium-severity vulnerability in Sun Jdk, published on 1 Apr 2010. An attacker can exploit it over the internet without logging in.
Exploitation: There is no known exploitation of CVE-2010-0084 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-2010-0084/ (Markdown: https://insights.sbomify.com/CVE-2010-0084/index.md)
```

## Sources

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

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