dbcve.org
JreApplication · Sun

CVE-2010-0093

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 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 Runtime Environment 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 confidentiality, integrity, and availability via unknown vectors, a different vulnerability than CVE-2010-0095.

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

A vulnerability in the Java Runtime Environment (JRE) affecting Oracle Java SE and Java for Business versions 6 Update 18, 5.0 Update 23, and 1.4.2_25 allows remote attackers to impact confidentiality, integrity, and availability through unspecified vectors.

MitigationUpgrade Java to a patched version beyond the affected releases (6u18, 5.0u23, 1.4.2_25) or apply Oracle critical patch updates; for legacy systems that cannot upgrade, consider removing or disabling the Java plugin from browsers.

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

AV:N/AC:H/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 installed JRE version
    Run 'java -version' from command line or check registry under HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment for the 'CurrentVersion' value
    Affected if The reported version matches 1.6.0, 1.5.0, 1.4.2, or 1.4.2_1 through 1.4.2_25 or any version <= 1.6.0, <= 1.5.0, or <= 1.4.2_25
  2. Identify installed JDK version
    Run 'javac -version' from command line or check registry under HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Development Kit
    Affected if The JDK version matches 1.6.0, 1.5.0, or any version <= 1.6.0 or <= 1.5.0 (JDK includes a bundled JRE)
  3. Identify installed SDK version
    Check registry under HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java SDK or run 'java -version' if SDK is the only Java installation
    Affected if The SDK version matches 1.4.2, 1.4.2_1 through 1.4.2_25, or any version <= 1.4.2_25
  4. Check if Java browser plugin is enabled
    For Internet Explorer, check Tools > Manage Add-ons > Java Plug-ins; for Firefox, check Add-ons > Plugins for 'Java Platform SE'; for Chrome, navigate to chrome://plugins
    Affected if Any Java plugin is listed and enabled, and the underlying JRE version is one of the affected versions listed above

You are affected if any installed JRE, JDK, or SDK version matches 1.6.0, 1.5.0, 1.4.2 (any update), or any version numerically lower than these releases, particularly if the Java browser plugin is enabled.

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 Java to a patched version beyond the affected releases (6u18, 5.0u23, 1.4.2_25) or apply Oracle critical patch updates; for legacy systems that cannot upgrade, consider removing or disabling the Java plugin from browsers.

Fix this in Jre Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-0093 — 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-0093 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