CVE-2010-0847
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 · uneditedUnspecified vulnerability in the Java 2D 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. NOTE: the previous information was obtained from the March 2010 CPU. Oracle has not commented on claims from a reliable researcher that this is a heap-based buffer overflow that allows arbitrary code execution via a crafted image.
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 · high confidenceCVE-2010-0847 is a heap-based buffer overflow vulnerability in the Java 2D component that allows remote attackers to execute arbitrary code via a crafted image file. This flaw affects multiple legacy Java versions (1.3.1_27, 1.4.2_25, 5.0_23, 6 Update 18) and enables complete compromise of affected systems through the high-severity CVSS rating of 7.5.
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<= 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<= 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<= 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_10CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Java runtime versionRun 'java -version' or 'java -fullversion' from command line to obtain the JRE/JDK version stringAffected if The version matches or is older than: 1.6.0 (any update), 1.5.0 (any update), 1.4.2_25 or lower, or any of the specific 1.4.2_x versions listed (1, 2, 3, 4, 5, 6)
-
Confirm Java 2D component is presentVerify the JRE/JDK includes the Java 2D library by checking for the presence of the rt.jar or j2d.jar in the JRE lib directory (for example, $JAVA_HOME/jre/lib/rt.jar)Affected if The Java 2D library files exist in the installed Java runtime
-
Determine if Java applets or Java Web Start are enabledCheck browser plugin configuration (for Internet Explorer, look in Manage Add-ons; for Firefox, check Plugins under Add-ons) and look for 'Java Plug-in' or 'Java Deployment Toolkit' entriesAffected if Java browser plugins are enabled or Java Web Start is installed and accessible
-
Identify Java processes handling untrusted image filesReview running Java applications or services that process image input from untrusted sources, such as image converters, document processors, or media handlers that use JavaAffected if Java applications process image files from untrusted or external sources without additional validation
A system is affected if it runs any Java version matching the affected ranges (1.6.0 and below, 1.5.0 and below, 1.4.2_25 and below, or specific 1.4.2_x/1.3.x variants) AND has Java 2D accessible through applets, Java Web Start, or applications that process untrusted image files.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the relevant Java Critical Patch Update (CPU) from March 2010 that addresses this vulnerability, or upgrade to a patched Java version beyond the affected releases. If immediate patching is not feasible, disable Java browser plugins and restrict Java applet execution until updates can be deployed.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2010-0847 — 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- itrc.hp.com
- labs.idefense.com
- lists.apple.com
- lists.apple.com
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- marc.info
- marc.info
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- support.apple.com
- support.apple.com
- ubuntu.com
- www.mandriva.com
- www.oracle.com
- www.oracle.com
- www.redhat.com
- www.redhat.com
- www.redhat.com
- www.redhat.com
- www.securityfocus.com
- www.securityfocus.com
- www.vmware.com
- www.vmware.com
- www.vupen.com
- www.vupen.com
- www.vupen.com
- www.vupen.com
- oval.cisecurity.org
- oval.cisecurity.org
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2010-0847 in production — separate from our analysis above.
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.
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.
- 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