JreApplication · Sun

CVE-2010-0089

MEDIUM · 5.0 CVSS v2.0 Published 2010-04-01
Fix available
A fix is available. Upgrade to after 1.6.0 or later.
See remediation →
59/100
Remediation priority · Elevated
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, and 1.4.2_25 allows remote attackers to affect 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 · low confidence

Vulnerability in Java Web Start and Java Plug-in allows remote attackers to affect availability (denial of service) via unknown vectors. Affects Java SE/Java for Business versions 6 Update 18, 5.0 Update 23, and 1.4.2_25.

MitigationUpdate to patched Java versions. If Java Web Start/Plug-in is not required, consider disabling these components to reduce attack surface.

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
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
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:N/C:N/I:N/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. Check if Java is installed
    Run 'java -version' or 'java -fullversion' from command line to retrieve the installed Java version
    Affected if No Java installation found means not affected by this specific Java vulnerability
  2. Identify exact Java version
    Run 'java -version 2>&1' and parse the version string (e.g., 1.6.0_18, 1.5.0_23, 1.4.2_25)
    Affected if Version matches 1.6.0 (any update), 1.5.0 (any update), or 1.4.2 through 1.4.2_25 (any sub-version) indicates affected
  3. Verify Java product type
    Check if installed JRE/JDK is Sun/Oracle branded (java -version output shows vendor)
    Affected if If Sun JRE, Sun JDK, or Sun SDK is installed and version falls in affected ranges, vulnerability applies
  4. Confirm Java Web Start or Plug-in presence
    Look for javaws.exe (Web Start) or java plugin files in browser plugins directory; on Windows check Program Files/Java for javaws.exe
    Affected if If Java Web Start (javaws) or Java Plug-in browser component is present on a system with affected version, it could be exploited

A system is affected if it runs any Sun JRE/JDK/SDK version 1.6.0, 1.5.0, or 1.4.2 through 1.4.2_25 that includes Java Web Start or Java Plug-in components.

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

Update to patched Java versions. If Java Web Start/Plug-in is not required, consider disabling these components to reduce attack surface.

Fix this in Jre Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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