dbcve.org
JreApplication · Sun

CVE-2010-0839

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

Unspecified vulnerability in Java's Sound component affecting older Java SE versions (6u18, 5.0u23, 1.4.2_25, 1.3.1_27). Allows remote attackers to achieve complete impact on confidentiality, integrity, and availability via unknown vectors in the sound processing code.

MitigationUpgrade to a supported Java version beyond the affected releases. Oracle Critical Patch Update April 2010 addressed this vulnerability.

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 installed JRE/JDK version
    Run 'java -version' or 'java -fullversion' from command line to see the installed Java runtime version
    Affected if Version is 1.6.0 or lower, 1.5.0 or lower, 1.4.2_25 or lower, or matches any of the specific 1.4.2_x versions listed (1.4.2 through 1.4.2_6), or 1.3.1_27/1.3.x versions for JDK
  2. Check for Java Web Start usage
    Look for javaws.exe process or check for .jnlp files in the system. Run 'javaws -version' if javaws is available
    Affected if Java Web Start is used with an affected Java version, as the vulnerability can be exploited through web start applications
  3. Verify Java Sound API usage
    Check running applications for use of javax.sound API. Look for audio processing functionality in deployed Java applications. Review application code or logs for sound-related classes
    Affected if Any Java application using the Sound API (javax.sound.sampled or javax.sound.midi) is running on an affected Java version
  4. Check browser plugin status
    Verify if Java Plugin is enabled in browsers. In Windows, check registry under HKLM\Software\JavaSoft for Java Plug-in component
    Affected if Java browser plugin is enabled with an affected Java version, as the vulnerability can be exploited via malicious applets

System is affected if any installed Java version (JRE, JDK, or SDK) matches the affected version ranges: 1.6.0 or lower, 1.5.0 or lower, 1.4.2_25 or lower, or specific 1.4.2_x/1.3.x versions, AND Java Sound functionality is accessible (via applet, web start, or application).

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 to a supported Java version beyond the affected releases. Oracle Critical Patch Update April 2010 addressed this vulnerability.

Fix this in Jre Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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