JreApplication · Oracle

CVE-2013-2430

HIGH · 7.6 CVSS v2.0 Published 2013-04-17

Fix available

A fix is available. Upgrade to after 2.2.7 or later.

See remediation →

85/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 17 and earlier, 6 Update 43 and earlier, and 5.0 Update 41 and earlier; JavaFX 2.2.7 and earlier; and OpenJDK 6 and 7 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to ImageIO. NOTE: the previous information is from the April 2013 CPU. Oracle has not commented on claims from another vendor that this issue is related to "JPEGImageReader state corruption" when using native code.

Technical summary

dbcve analysis · high confidence

CVE-2013-2430 is a vulnerability in the Java Runtime Environment's ImageIO component, specifically involving JPEGImageReader state corruption when processing images using native code. The unspecified vulnerability in ImageIO allows remote attackers to affect confidentiality, integrity, and availability, likely through memory corruption that could enable arbitrary code execution.

MitigationApply the April 2013 Critical Patch Update from Oracle, which includes the fix for this vulnerability (upgrade to JDK/JRE 7u21, 6u45, or 5u45 or later; OpenJDK 6b18+ or 7b21+). If immediate patching is not feasible, disable Java browser plugins and restrict Java Web Start execution.

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.7.0= 1.7.0<= 1.6.0= 1.6.0<= 1.5.0= 1.5.0

JdkApplication

Affected:<= 1.7.0= 1.7.0<= 1.6.0= 1.6.0<= 1.5.0= 1.5.0

JreApplication

Affected:= 1.6.0= 1.5.0

JdkApplication

Affected:= 1.6.0= 1.5.0

JavafxApplication

Affected:<= 2.2.7= 2.0= 2.0.2= 2.0.3= 2.1= 2.2= 2.2.3= 2.2.4= 2.2.5

CVSS breakdown

From the vector

Attack vector: Network
Complexity: High
Authentication: None
Confidentiality: Complete
Integrity: Complete
Availability: Complete

AV:N/AC:H/Au:N/C:C/I:C/A:C

Am I affected?

dbcve checks

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

Identify installed Java version

Run 'java -version' or 'java -fullversion' from command line to display the installed JRE/JDK version

Affected if Version is 1.7.0 or earlier, 1.6.0 or earlier, or 1.5.0 (any update release within these major versions)
Determine Java vendor and product type

Run 'java -version' and check if the output shows Oracle, Sun, or OpenJDK. Also check if JavaFX is installed by looking for javafx*.jar in the Java lib directory or running 'java -version' for JavaFX-specific entries

Affected if Product is Oracle JRE/JDK, Sun JRE/JDK, or Oracle JavaFX within the affected version ranges
Verify ImageIO component availability

Check that the jre/lib/rt.jar (or equivalent in newer Java) contains the ImageIO classes. In Java, run: java -verbose:class 2>&1 | grep -i imageio to confirm ImageIO classes are loadable

Affected if ImageIO component is present (standard in all affected Java installations)
Check for applications using ImageIO

Review deployed Java applications for usage of javax.imageio package, specifically code using JPEGImageReader class to process JPEG images

Affected if Any Java application or applet uses ImageIO to process JPEG images

Your environment is affected if you run any Oracle or Sun JRE/JDK version 1.5.x, 1.6.x, or 1.7.x (or JavaFX 2.x through 2.2.7) that processes JPEG images via the ImageIO component.

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

Remediation

From vendor data

Upgrade available Upgrade to a release after 2.2.7

Interim mitigation

Apply the April 2013 Critical Patch Update from Oracle, which includes the fix for this vulnerability (upgrade to JDK/JRE 7u21, 6u45, or 5u45 or later; OpenJDK 6b18+ or 7b21+). If immediate patching is not feasible, disable Java browser plugins and restrict Java Web Start execution.

Fix this in Jre Scoped from the published advisory

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

18.0 hours of engineering $3,120

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2013-2430 — 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-2013-2430 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2013-2430?

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 2.2.7 or later

Severity 7.6 High

Exploit likelihood EPSS, next 30 days 5.7%

Affects: Jre

Remediation

A high-priority fix

Fix this in Jre 18 hrs · Moderate

Typical engagement from $3,120

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2013-2430 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