dbcve.org
JavafxApplication · Oracle

CVE-2012-4301

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 JavaFX component in Oracle Java SE JavaFX 2.2.4 and earlier allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors, a different vulnerability than other CVEs listed in the February 2013 CPU. NOTE: the previous information is from the February 2013 CPU. Oracle has not commented on claims from a third party that this issue allows remote attackers to execute arbitrary code via an "invalid type case" in the init method of the D3DShader class in the com.sun.prism.d3d package. CPU.

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

A critical vulnerability in Oracle Java SE JavaFX 2.2.4 and earlier allows remote attackers to execute arbitrary code via an 'invalid type case' in the init method of the D3DShader class within the com.sun.prism.d3d package. This enables complete compromise of confidentiality, integrity, and availability.

MitigationApply the February 2013 Critical Patch Update to upgrade JavaFX beyond version 2.2.4, or update to a patched JDK version that addresses this vulnerability.

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
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 if JavaFX is installed on the system
    On Windows, check for JavaFX installation by looking for javafx*.jar files in the Java installation directory (e.g., C:\Program Files\Java\jre7\lib\ or C:\Program Files\Oracle\), or check the Windows Registry under HKLM\SOFTWARE\JavaSoft\JavaFX for the property "Version" or "PathToHome". On Linux/Unix, check /usr/share/java/ or the Java home lib directory for javafx*.jar files.
    Affected if JavaFX is present on the system with a version matching 2.0, 2.0.2, 2.0.3, 2.1, 2.2, 2.2.3, or any version <= 2.2.4
  2. Verify the installed JavaFX version number
    If using Windows Registry, query the "Version" string value under HKLM\SOFTWARE\JavaSoft\JavaFX. If the JAR file is found, check the manifest file inside javafx*.jar for the Implementation-Version attribute, or use the command: java -jar javafx.jar to invoke and query the version via Java code.
    Affected if The installed version is 2.2.4 or any version 2.0 through 2.2.3, or any version <= 2.2.4
  3. Confirm the D3D rendering pipeline is in use
    This vulnerability exists in the D3DShader class within com.sun.prism.d3d package, which is used only on Windows systems with Direct3D rendering. Check if the JavaFX application or runtime is configured to use the D3D pipeline. This can be verified by examining JavaFX runtime logs with debug tracing enabled (set JAVA_TOOL_OPTIONS="-Dprism.verbose=true") or by checking if the application runs on a Windows platform with hardware acceleration enabled.
    Affected if The system is Windows-based and JavaFX is using the D3D (Direct3D) rendering pipeline, which is the default on Windows for JavaFX 2.x versions.

A system is affected if it runs any Windows version of JavaFX 2.2.4 or earlier (versions 2.0 through 2.2.3 or any version <= 2.2.4) with D3D rendering enabled, which is the default on Windows.

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

Apply the February 2013 Critical Patch Update to upgrade JavaFX beyond version 2.2.4, or update to a patched JDK version that addresses this vulnerability.

Recommended fix Moderate confidence

Latest JavaFX 2.x or migrate to Java SE 7u6+ which includes bundled JavaFX

  1. 1. Identify all deployments and systems running JavaFX versions 2.0, 2.0.2, 2.0.3, or 2.2.4 and earlier.
  2. 2. Check Oracle's official February 2013 Critical Patch Update (CPU) advisory for JavaFX security fixes.
  3. 3. Upgrade JavaFX to the latest version available from Oracle's official JavaFX download pages or via your Java SE subscription.
  4. 4. Alternatively, upgrade to Java SE 7 update 15 or later (which bundles fixed JavaFX components) as Oracle integrated JavaFX into the JDK starting with Java SE 7u6.
  5. 5. After upgrading, test all JavaFX applications to ensure functionality is preserved.
  6. 6. Verify the fix by confirming the JavaFX version number matches a release dated after February 2013.
Caveat Migration to newer JavaFX/JDK may require code changes if APIs changed between 2.0-2.2.x and later versions; bundled JavaFX in JDK 7u6+ replaced the separate JavaFX SDK

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

Fix this in Javafx Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,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 $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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