CVE-2010-0837 Other in n/a
High 7.5
Published
Updated
Check this codebase for CVE-2010-0837 and fix it if it is affected.
What it is: CVE-2010-0837 is a high-severity vulnerability in Sun Jdk, published on 1 Apr 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-0837 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-0837/ (Markdown: https://insights.sbomify.com/CVE-2010-0837/index.md)
Remote attackers can compromise confidentiality, integrity, and availability in Oracle Java SE via the Pack200 component.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2010-0837?
CVE-2010-0837 is a high-severity vulnerability in Sun Jdk, published on 1 Apr 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Unspecified vulnerability in the Pack200 component in Oracle Java SE and Java for Business 6 Update 18, 5.0, Update, and 23 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors.
Which versions are affected by CVE-2010-0837?
It affects 2 products.
How do I fix CVE-2010-0837?
Upgrade to a fixed version.
Is CVE-2010-0837 being exploited?
There is no known exploitation of CVE-2010-0837 in the wild and no public exploit code.
Other vulnerabilities in Sun Jdk
Sources
Also known as GHSA-ch7p-82hg-j456.