dbcve.org
JdkApplication · Oracle

CVE-2012-1713

HIGH · 10.0 CVSS v2.0 Published 2012-06-16
Fix available
A fix is available. Upgrade to after 2.1 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 4 and earlier, 6 update 32 and earlier, 5 update 35 and earlier, 1.4.2_37 and earlier, and JavaFX 2.1 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 · high confidence

CVE-2012-1713 is a critical unspecified vulnerability in the Java Runtime Environment's 2D graphics component affecting Java SE 7u4 and earlier, 6u32 and earlier, 5u35 and earlier, and JavaFX 2.1 and earlier. The flaw allows remote attackers to execute arbitrary code via unknown vectors in the 2D subsystem, achieving complete compromise of confidentiality, integrity, and availability.

MitigationUpgrade to Java SE 7 Update 5 or later, 6 Update 33 or later, or 5 Update 36 or later; alternatively, apply Oracle Critical Patch Update June 2012. Disable Java browser plugins where possible until patching is complete.

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
JdkApplication
Affected:<= 1.7.0<= 1.6.0
JreApplication
Affected:<= 1.7.0<= 1.6.0
JdkApplication
Affected:<= 1.5.0<= 1.4.2_37
JreApplication
Affected:<= 1.5.0<= 1.4.2_37
JavafxApplication
Affected:<= 2.1

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. Identify installed Java Runtime Environment version
    Open a terminal and run 'java -version' or 'java -fullversion' to display the installed JRE version number
    Affected if The version displayed is 1.7.0 or earlier, 1.6.0 update 32 or earlier, 1.5.0 update 35 or earlier, or 1.4.2 update 37 or earlier
  2. Identify installed Java Development Kit version
    Run 'javac -version' in a terminal to check the installed JDK version
    Affected if The version is 1.7.0 or earlier, 1.6.0 update 32 or earlier, 1.5.0 update 35 or earlier, or 1.4.2 update 37 or earlier
  3. Check for JavaFX installation and version
    Locate JavaFX runtime files or check program listings for JavaFX components; version information is typically found in the JavaFX release notes or system registry
    Affected if JavaFX 2.1 or earlier is installed
  4. Verify Java browser plugin status
    Check web browser settings for the Java plug-in (Java Plug-in 2) or use the Java Control Panel to view enabled browser plugins
    Affected if The Java browser plugin is enabled in any web browser

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

Upgrade to Java SE 7 Update 5 or later, 6 Update 33 or later, or 5 Update 36 or later; alternatively, apply Oracle Critical Patch Update June 2012. Disable Java browser plugins where possible until patching is complete.

Recommended fix High confidence

Java 7 Update 5+, Java 6 Update 33+, Java 5 Update 36+, Java 1.4.2_38+, JavaFX 2.2+

  1. 1. Identify all Java installations on the system using 'java -version' and checking JAVA_HOME environment variable
  2. 2. For JDK 1.7.0: upgrade to JDK 7 Update 5 (1.7.0_05) or later
  3. 3. For JDK 1.6.0: upgrade to JDK 6 Update 33 (1.6.0_33) or later
  4. 4. For JDK 1.5.0: upgrade to JDK 5 Update 36 (1.5.0_36) or later
  5. 5. For JDK 1.4.2: upgrade to JDK 1.4.2_38 or later
  6. 6. For JavaFX 2.1: upgrade to JavaFX 2.2 or later which includes the security fix
  7. 7. Verify the upgrade by running 'java -version' and confirming the updated patch level
  8. 8. Test any critical applications to ensure compatibility with the new Java version
Caveat Upgrading Java versions may cause compatibility issues with applications compiled for older Java versions due to removed APIs or behavioral changes; test thoroughly before production deployment

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

Fix this in Jdk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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