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

> Local attackers can exploit a Java DB vulnerability to compromise confidentiality, requiring an upgrade to Oracle Java SE.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Feb 2011
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-qrv7-cr6p-439g

## What is CVE-2010-4474?

CVE-2010-4474 is a low-severity vulnerability in Sun Jdk, published on 17 Feb 2011. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unspecified vulnerability in the Java DB component in Oracle Java SE and Java for Business 6 Update 23, and, and earlier allows local users to affect confidentiality via unknown vectors related to Security, a similar vulnerability to CVE-2009-4269.

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

It affects 2 products.


Products: Sun Jdk, Sun Jre.

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

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

## Is CVE-2010-4474 being exploited?

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

What it is: CVE-2010-4474 is a low-severity vulnerability in Sun Jdk, published on 17 Feb 2011. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-4474 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-4474/ (Markdown: https://insights.sbomify.com/CVE-2010-4474/index.md)
```

## Sources

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

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