JdkApplication · Oracle

CVE-2014-0417

HIGH · 9.3 CVSS v2.0 Published 2014-01-15

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

100/100

Remediation priority · Urgent

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Unspecified vulnerability in Oracle Java SE 5.0u55, 6u65, and 7u45; JavaFX 2.2.45; and Java SE Embedded 7u45 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to 2D.

Technical summary

dbcve analysis · moderate confidence

A remote code execution vulnerability in Oracle Java SE's 2D graphics subsystem (Java SE 5.0u55, 6u65, 7u45; JavaFX 2.2.45; Java SE Embedded 7u45) allows attackers to achieve complete compromise of confidentiality, integrity, and availability via unspecified vectors in the 2D rendering code. The critical CVSS score of 9.3 indicates network-exploitable code with no authentication required.

MitigationApply Oracle's Java Critical Patch Update (CPU) for January 2014 or later to obtain the security fix. For systems unable to update, disable Java browser plugins and restrict network access to untrusted sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

JdkApplication

Affected:= 1.5.0= 1.6.0

JreApplication

Affected:= 1.5.0= 1.7.0= 1.6.0

JavafxApplication

Affected:= 2.2.45

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify installed Java Runtime Environment (JRE) version

Open a terminal or command prompt and run: java -version. This displays the JRE version in the format '1.X.0_YY' where X is 5, 6, or 7

Affected if The version shows 1.5.0_55, 1.6.0_65, or 1.7.0_45 (or any earlier update version within these major releases)
Identify installed Java Development Kit (JDK) version

Run: javac -version. This shows the JDK compiler version, which indicates the JDK installation

Affected if The version shows 1.5.0, 1.6.0, or 1.7.0 (with any update version below the fixed releases)
Check for JavaFX installation and version

Locate the javafx runtime libraries. On Windows, check for javafx*.dll in the Java bin directory, or search for javafx folders under the Java installation path

Affected if JavaFX version 2.2.45 is installed
Verify Java 2D graphics subsystem is in use

This vulnerability affects any Java application that uses 2D rendering (java.awt or javax.imageio). No special configuration check needed - this is the default graphics subsystem for standard Java applications

Affected if Any Java application with graphical output (GUI, images, printing) is running on the affected JRE/JDK
Confirm Java is accessible over network

Review firewall rules and Java applet settings. Check if Java browser plugins are enabled or if Java Web Start applications can be launched remotely

Affected if Java is network-accessible through browser plugins, Web Start, or exposed RMI interfaces

You are affected if any Java 5.0 update 55 or earlier, Java 6 update 65 or earlier, or Java 7 update 45 or earlier is running, especially if network-accessible or used for graphical applications

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Apply Oracle's Java Critical Patch Update (CPU) for January 2014 or later to obtain the security fix. For systems unable to update, disable Java browser plugins and restrict network access to untrusted sources.

Recommended fix High confidence

Java 8 (or later LTS release) - the specific fix for CVE-2014-0417 is included in Java 7u60 and later, but upgrading to Java 8+ is recommended for better security support

1. Identify all systems running the affected Java versions (JDK/JRE 1.5.0, 1.6.0, 1.7.0, or JavaFX 2.2.45)
2. Download and install a patched version of Java. For Java 7u45, upgrade to Java 7u60 or later (which includes the fix for this 2D vulnerability)
3. For Java 6 (1.6.0), migrate to Java 8 or later as Java 6 is end-of-life and no longer receives public updates
4. For Java 5 (1.5.0), migrate to Java 8 or later as Java 5 is end-of-life
5. Verify the Java version after installation: run 'java -version' to confirm the new version is active
6. Update any JAVA_HOME environment variables to point to the new installation
7. Test all Java-dependent applications to ensure compatibility with the new Java version
8. Remove or disable old Java installations to prevent accidental usage

Caveat Upgrading from Java 5/6 to Java 8 may break existing applications due to removed APIs, bytecode changes, and deprecated feature removals. 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
Testing8.0 h
Review / QA2.0 h

16.0 hours of engineering $2,680

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-0417 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2014-0417?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 9.3 High

Exploit likelihood EPSS, next 30 days 5.4%

Affects: Jdk

Remediation

A high-priority fix

Fix this in Jdk 16 hrs · Moderate

Typical engagement from $2,680

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2014-0417 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References