JreApplication · Sun

CVE-2010-0841

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

NVD · unedited

Unspecified vulnerability in the ImageIO 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. NOTE: the previous information was obtained from the March 2010 CPU. Oracle has not commented on claims from a reliable researcher that this is an integer overflow in the Java Runtime Environment that allows remote attackers to execute arbitrary code via a JPEG image that contains subsample dimensions with large values, related to JPEGImageReader and "stepX".

Technical summary

dbcve analysis · high confidence

Integer overflow vulnerability in Java Runtime Environment's JPEGImageReader component allows remote attackers to execute arbitrary code via specially crafted JPEG images containing large subsample dimensions (stepX). This affects Java versions 6 Update 18, 5.0 Update 23, and 1.4.2_25.

MitigationApply the March 2010 CPU patch or update to a newer Java version to address the integer overflow in ImageIO's JPEGImageReader. Consider disabling the Java browser plugin until patches are applied.

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

Affected products & versions

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

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?

dbcve checks

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

Determine Java version installed

Run 'java -version' from command line, or check registry on Windows (HKLM\Software\JavaSoft\Java Runtime Environment), or check /usr/java or /opt/java directories on Linux/Unix systems

Affected if Version is 1.6.0 any update through Update 18, 1.5.0 any update through Update 23, or 1.4.2 through 1.4.2_25
Identify if Java is using ImageIO with JPEG support

Verify the jre/lib/rt.jar contains the JPEGImageReader class (com.sun.imageio.plugins.jpeg.JPEGImageReader), which is included by default in standard Java installations

Affected if Java's ImageIO with JPEG decoding capability is present and operational
Confirm Java browser plugin is enabled

Check browser plugin settings: on Windows check for npappl.dll in browser addons, on Linux check for libjavaplugin.so in browser plugin directories; examine browser's plugins or add-ons list for Java entries

Affected if Java browser plugin is enabled and can process remote JPEG images through web pages

System is affected if installed Java version is 1.6.0 through 1.6.0_18, 1.5.0 through 1.5.0_23, or 1.4.2 through 1.4.2_25 AND Java's ImageIO functionality (with JPEGImageReader) is available, particularly if the browser plugin is active.

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

Remediation

From vendor data

Upgrade available Upgrade to a release after 1.6.0

Interim mitigation

Apply the March 2010 CPU patch or update to a newer Java version to address the integer overflow in ImageIO's JPEGImageReader. Consider disabling the Java browser plugin until patches are applied.

Fix this in Jre Scoped from the published advisory

Consultation3.0 h
Implementation4.0 h
Testing6.0 h
Review / QA3.0 h

16.0 hours of engineering $2,760

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2010-0841?

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.

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

At a glance

A fix existsUpgrade to after 1.6.0 or later

Severity 7.5 High

Exploit likelihood EPSS, next 30 days 6.2%

Affects: Jre

Remediation

A high-priority fix

Fix this in Jre 16 hrs · Moderate

Typical engagement from $2,760

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2010-0841 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References