JreApplication · Sun

CVE-2010-0085

MEDIUM · 5.1 CVSS v2.0 Published 2010-04-01

Fix available

A fix is available. Upgrade to after 1.6.0 or later.

See remediation →

60/100

Remediation priority · Elevated

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

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

Technical summary

dbcve analysis · moderate confidence

Unspecified vulnerability in the Java Runtime Environment affecting Java SE/Business versions 6 Update 18, 5.0 Update 23, 1.4.2_25, and 1.3.1_27. Allows remote attackers to affect confidentiality, integrity, and availability via unknown attack vectors. Different vulnerability from CVE-2010-0088.

MitigationUpgrade to later Java versions beyond those listed (Java 6u18+, 5.0u23+, 1.4.2_25+, 1.3.1_27+) or apply Oracle critical patch updates. Given the full CIA impact and remote attack vector, prioritize patching for any systems exposed to untrusted input.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

JreApplication

Affected:<= 1.6.0= 1.6.0<= 1.5.0= 1.5.0<= 1.4.2_25= 1.4.2= 1.4.2_1= 1.4.2_2= 1.4.2_3= 1.4.2_4= 1.4.2_5= 1.4.2_6

JdkApplication

Affected:<= 1.6.0= 1.6.0<= 1.5.0= 1.5.0<= 1.3.1_27= 1.3.0= 1.3.0_01= 1.3.0_02= 1.3.0_03= 1.3.0_04= 1.3.0_05= 1.3.1

SdkApplication

Affected:<= 1.4.2_25= 1.4.2= 1.4.2_1= 1.4.2_02= 1.4.2_3= 1.4.2_4= 1.4.2_5= 1.4.2_6= 1.4.2_7= 1.4.2_8= 1.4.2_9= 1.4.2_10

CVSS breakdown

From the vector

Attack vector: Network
Complexity: High
Authentication: None
Confidentiality: Partial
Integrity: Partial
Availability: Partial

AV:N/AC:H/Au:N/C:P/I:P/A:P

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify installed Java version

Run 'java -version' from command line or check JAVA_HOME environment variable for the installation path, then inspect the version file in that directory

Affected if The reported version matches any of these patterns: 1.6.0.x (where x is any update up to 18), 1.5.0.x (up to update 23), 1.4.2_x (where x is 25 or lower), or 1.3.1_x (where x is 27 or lower)
Determine Java product type

Check if the installation is JRE, JDK, or SDK by examining the installation directory structure or running 'which java' and 'java -version' output

Affected if The product is Sun JRE, Sun JDK, or Sun SDK versions listed in the affected versions field
Confirm Java is actively used or exposed

Identify if Java applications are running or if the Java plugin is enabled in browsers, as the vulnerability affects the runtime environment

Affected if Java is running as a service, used by web applications, or the Java browser plugin is enabled and the version is within the affected range

A system is affected if it runs any Sun JRE, JDK, or SDK version at or below 1.6.0u18, 1.5.0u23, 1.4.2_25, or 1.3.1_27, with remote attack vectors impacting confidentiality, integrity, and availability.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Upgrade available Upgrade to a release after 1.6.0

Interim mitigation

Upgrade to later Java versions beyond those listed (Java 6u18+, 5.0u23+, 1.4.2_25+, 1.3.1_27+) or apply Oracle critical patch updates. Given the full CIA impact and remote attack vector, prioritize patching for any systems exposed to untrusted input.

Fix this in Jre Scoped from the published advisory

Consultation4.0 h
Implementation8.0 h
Testing6.0 h
Review / QA2.0 h

20.0 hours of engineering $3,500

Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2010-0085 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-0085 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2010-0085?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

A fix existsUpgrade to after 1.6.0 or later

Severity 5.1 Medium

Exploit likelihood EPSS, next 30 days 3.1%

Affects: Jre

Remediation

Need this fixed?

Fix this in Jre 20 hrs · Moderate

Typical engagement from $3,500

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2010-0085 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References