dbcve.org
JreApplication · Oracle

CVE-2013-0437

HIGH · 10.0 CVSS v2.0 Published 2013-02-02
Fix available
A fix is available. Upgrade to after 2.2.4 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 through Update 11 and JavaFX 2.2.4 and earlier allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to 2D.

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

CVE-2013-0437 is a critical severity vulnerability in the Java Runtime Environment (JRE) 2D graphics component affecting Java SE 7 through Update 11 and JavaFX 2.2.4 and earlier. The vulnerability allows remote attackers to impact confidentiality, integrity, and availability via unknown vectors related to 2D rendering, with CVSS 10 indicating likely remote code execution capability.

MitigationUpdate Java SE to a version beyond Update 11 (patched in later updates) and JavaFX beyond 2.2.4. Given the critical severity and network-exploitable nature, prioritize patching all affected Java installations, particularly those running Java applets or Java Web Start applications.

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
JdkApplication
Affected:= 1.7.0
JavafxApplication
Affected:<= 2.2.4= 2.0= 2.0.2= 2.0.3= 2.1= 2.2= 2.2.3

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. Check installed Java SE version
    Run 'java -version' or 'java -fullversion' from command line. Also check $JAVA_HOME/version if JAVA_HOME is set.
    Affected if Version displays as Java SE 7 (1.7.x) with update level 11 or earlier (for example, 1.7.0, 1.7.0_10, 1.7.0_11)
  2. Check installed JDK version
    Run 'javac -version' or check $JAVA_HOME/jre/version file.
    Affected if JDK version shows 1.7.0 with update 11 or earlier
  3. Check installed JavaFX version
    Check for javafx libraries in the installation path, or run 'java -jar javafxProperties.jar' if available. Also inspect JAR manifest files in JavaFX installations.
    Affected if JavaFX version is 2.2.4 or earlier, or any of these specific versions: 2.0, 2.0.2, 2.0.3, 2.1, 2.2, 2.2.3
  4. Identify if 2D rendering components are in use
    Inspect running Java processes for 2D-related system properties: 'java.awt.graphicsenv' or '-Dsun.java2d' flags. Review application dependencies for java2d or rendering-related classes.
    Affected if Any Java application using Java2D rendering pipelines is potentially using the vulnerable component

If Java SE 7 (1.7.x) at update 11 or earlier, or JavaFX 2.2.4 or earlier is installed and running applications with 2D graphics, the environment is affected by CVE-2013-0437.

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.4
Interim mitigation

Update Java SE to a version beyond Update 11 (patched in later updates) and JavaFX beyond 2.2.4. Given the critical severity and network-exploitable nature, prioritize patching all affected Java installations, particularly those running Java applets or Java Web Start applications.

Recommended fix High confidence

Oracle Java SE 7 Update 15 or later (recommended: Java SE 8u311 or Java SE 11 LTS for extended support)

  1. Check current Java version by running 'java -version' in terminal
  2. Identify all Java installations on the system using 'which java' or 'find /usr -name java'
  3. Download Oracle Java SE 7 Update 15 or later (or Java SE 8/11/17 LTS for long-term support) from official Oracle website or trusted distribution
  4. Install the new Java version following platform-specific installation instructions
  5. Update JAVA_HOME environment variable to point to the new installation path
  6. Update any application server or IDE configurations that reference the old Java path
  7. Verify the new Java version is active by running 'java -version'
  8. Ensure all applications are tested with the new Java version
Caveat Later Java 7 updates may have API behavior changes; applications using removed/deprecated APIs may require code updates. Consider thorough testing before production deployment.

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

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-2013-0437 — 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-0437 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