dbcve.org
JreApplication · Oracle

CVE-2013-2432

HIGH · 10.0 CVSS v2.0 Published 2013-04-17
Fix available
A fix is available. Upgrade to after 2.2.7 or later.
See remediation →
100/100
Remediation priority · Urgent
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 (JRE) component in Oracle Java SE 7 Update 17 and earlier, 6 Update 43 and earlier, 5.0 Update 41 and earlier, and JavaFX 2.2.7 and earlier allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to 2D, a different vulnerability than CVE-2013-2394 and CVE-2013-1491.

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 confidence

Critical remote code execution vulnerability in the Java 2D component of the JRE (affecting Java SE 7u17 and earlier, 6u43 and earlier, 5.0u41 and earlier, JavaFX 2.2.7 and earlier). Allows remote attackers to execute arbitrary code via unspecified vectors in the 2D graphics rendering subsystem, achieving complete compromise of confidentiality, integrity, and availability.

MitigationUpgrade to Java SE 7 Update 21+, 6 Update 45+, or later patched versions. If patching is not immediately feasible, disable the Java browser plugin or enable click-to-play for Java applet content to reduce attack surface.

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.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 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
Complete
Integrity
Complete
Availability
Complete

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

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. Determine installed JRE version
    Run 'java -version' or check JAVA_HOME environment variable and examine the runtime JAR files in the JRE lib directory
    Affected if Version is 1.7.0 (any update <= 17), 1.6.0 (any update <= 43), or 1.5.0 (any update <= 41)
  2. Determine installed JDK version
    Run 'javac -version' or check for JDK installation in Program Files/Java or /usr/lib/jvm/
    Affected if Version is 1.7.0 (any update <= 17), 1.6.0 (any update <= 43), or 1.5.0 (any update <= 41)
  3. Determine installed JavaFX version
    Check for javafx.* packages in the installation, or examine javafx.runtime.version property via 'java -jar' or through the Java Control Panel
    Affected if Version is 2.2.7 or earlier, or any 2.0.x, 2.1, or 2.2.x release (2.2.3, 2.2.4, 2.2.5)
  4. Confirm Java 2D component is in use
    Check if the system runs Java applets, Java Web Start applications, or any code that uses java.awt.Graphics2D or javax.imageio rendering pipelines
    Affected if The Java 2D rendering pipeline is actively used; the vulnerability is triggered through 2D graphics rendering operations

You are affected if any installed Java SE JRE/JDK is version 1.7.0 update 17 or earlier, 1.6.0 update 43 or earlier, or 1.5.0 update 41 or earlier, OR if JavaFX 2.2.7 or earlier is present and the Java 2D subsystem is used.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2.2.7
Interim mitigation

Upgrade to Java SE 7 Update 21+, 6 Update 45+, or later patched versions. If patching is not immediately feasible, disable the Java browser plugin or enable click-to-play for Java applet content to reduce attack surface.

Recommended fix High confidence

Java SE 7 Update 21+ (or Java SE 8 for long-term support), Java SE 6 Update 45+ (if support contract exists), JavaFX 2.2.8+

  1. Identify all systems running affected Java versions (JDK/JRE 1.5.0, 1.6.0 through Update 43, 7.0 through Update 17, or JavaFX 2.2.7 and earlier)
  2. Stop any applications or services that use the affected Java installations
  3. For Java SE 5.x (1.5.0): Upgrade to Java SE 7 or later as Java 5 is end-of-life and no longer receives security updates
  4. For Java SE 6.x: Upgrade to Java SE 6 Update 45 or later (recommended: Java SE 7 or 8 for continued support)
  5. For Java SE 7.x: Upgrade to Java SE 7 Update 21 or later (recommended: Java SE 8 or later for continued support)
  6. For JavaFX: Upgrade to JavaFX 2.2.8 or later
  7. Download the fixed JDK/JRE from Oracle's official Java SE download page (www.oracle.com/java/technologies/downloads/)
  8. Install the new Java version on all affected systems
Caveat Legacy applications written for Java 5/6 may require compilation changes for Java 7+; some deprecated APIs removed in newer versions may cause compilation or runtime errors

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jre Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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