CVE-2012-4305
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 · uneditedUnspecified 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 the issue allows remote attackers to execute arbitrary code via vectors related to an "invalid type cast" and exposed native methods in the T2KGlyph class.
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 confidenceCVE-2012-4305 is an unspecified vulnerability in JavaFX 2.2.4 and earlier (part of Oracle Java SE) that allows remote attackers to achieve full impact (confidentiality, integrity, availability). Third-party analysis indicates the issue stems from an invalid type cast vulnerability in the T2KGlyph class that exposes native methods, enabling remote arbitrary code execution.
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<= 2.2.4= 2.0= 2.0.2= 2.0.3= 2.1= 2.2= 2.2.3CVSS 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/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 checksWork through these to decide whether this CVE applies to you.
-
Detect JavaFX installationSearch for javafx runtime files on the system. On Windows, check for jfx*.dll in the JRE\bin directory (e.g., C:\Program Files\Java\jre7\bin\jfx*.dll) or javafx*.jar in the lib directory. On Linux, look for libjfx*.so in the JRE/lib/amd64 or similar architecture folders.Affected if JavaFX runtime files (jfx*.dll or libjfx*.so) are present on the system
-
Identify JavaFX versionCheck the version of the installed JavaFX runtime. On Windows, right-click the jfx*.dll file, select Properties, then Details to view the File Version. Alternatively, run 'java -version' and check the JavaFX version output if available, or examine the javafx*.jar META-INF/MANIFEST.MF file for the Implementation-Version attribute.Affected if The detected JavaFX version is 2.2.4 or earlier, or matches any of these exact versions: 2.0, 2.0.2, 2.0.3, 2.1, 2.2, 2.2.3
-
Determine JavaFX usage contextIdentify if JavaFX applications are deployed via Java Web Start (jnlp files) or if the browser plugin is enabled. Check browser Java plugin settings and look for .jnlp file associations. On Windows, examine the registry under HKLM\SOFTWARE\JavaSoft\JavaFX for RuntimeVersion or similar entries.Affected if JavaFX is used in a context where it can be invoked remotely, such as through web browsers or Java Web Start applications
-
Check for exposed native methodsThe vulnerability resides in the T2KGlyph class which exposes native methods. Examine the JavaFX runtime library for the presence of T2KGlyph-related code. This is indirectly detectable by confirming the JavaFX version, as this specific class is present in all versions up to and including 2.2.4.Affected if JavaFX 2.2.4 or earlier is installed, meaning the vulnerable T2KGlyph class is present in the runtime
The environment is affected if JavaFX runtime version 2.2.4 or any earlier version (2.0, 2.0.2, 2.0.3, 2.1, 2.2, 2.2.3) is installed and accessible to remote users via browser plugins, Web Start, or networked applications.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate Java/JavaFX to versions later than 2.2.4 (applying the February 2013 Critical Patch Update or subsequent updates). Identify and remediate all affected Java installations across the environment, as the vulnerability can be exploited remotely without authentication.
Java SE 7 Update 15 or later (February 2013 CPU or subsequent)
- Download and install Java SE 7 Update 15 or later from Oracle's official Java SE downloads page (https://www.oracle.com/java/technologies/downloads/)
- If using JavaFX specifically, upgrade to JavaFX 2.2.5 or later which contains the February 2013 CPU security fixes
- Verify the installation by running 'java -version' to confirm the updated version is active
- Ensure any applications using JavaFX are restarted to load the updated runtime
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-4305 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-4305 in production — separate from our analysis above.
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.
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.
- 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