dbcve.org
JreApplication · Sun

CVE-2010-0087

HIGH · 7.5 CVSS v2.0 Published 2010-04-01
Fix available
A fix is available. Upgrade to after 1.6.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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.

NVD · unedited
Unspecified vulnerability in the Java Web Start, Java Plug-in 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.

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.

dbcve analysis · moderate confidence

Vulnerability in Java Web Start and Java Plug-in components allowing remote attackers complete impact on confidentiality, integrity, and availability via unknown vectors. The unspecified nature suggests a serious code execution flaw, likely exploitable through malicious JNLP files or applets. This affects client-side Java deployments.

MitigationUpgrade affected Java installations to patched versions beyond Update 18 for Java 6, or migrate away from deprecated Java Web Start/Plug-in technologies entirely.

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

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.

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 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.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

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

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.

dbcve checks

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

  1. Identify Java installation and version
    Run 'java -version' from command line or check for java.exe in common paths (C:\Program Files\Java\, /usr/lib/jvm/)
    Affected if Version number starts with 1.6.0, 1.5.0, 1.4.2, 1.3.1, 1.3.0, or matches any specific version listed in the affected products
  2. Determine if JRE (Java Runtime Environment) is installed
    Look for JRE-specific directories or check registry key HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment on Windows
    Affected if JRE version matches the affected version ranges (1.6.0 and below, 1.5.0 and below, 1.4.2 series)
  3. Check if Java Web Start (javaws) is present
    Run 'javaws -version' or locate javaws.exe in the Java installation bin directory
    Affected if javaws executable exists AND the underlying Java version is within the affected version list
  4. Check if Java Plug-in is enabled in browsers
    Examine browser plugin directories (e.g., Firefox plugins folder, Chrome extensions) or check Java Control Panel (javacpl.exe) for browser plugin status
    Affected if Java plugin is registered/enabled in any web browser AND Java version is among the affected versions

User is affected if they have any Sun Java installation (JRE, JDK, or SDK) matching versions 1.6.0 and below, 1.5.0 and below, or the specific 1.4.2 and 1.3.x versions listed, AND Java Web Start or Java Plug-in component is present and accessible.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Upgrade available Upgrade to a release after 1.6.0
Interim mitigation

Upgrade affected Java installations to patched versions beyond Update 18 for Java 6, or migrate away from deprecated Java Web Start/Plug-in technologies entirely.

Fix this in Jre Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing24.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,520
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-0087 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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