dbcve.org
JdkApplication · Oracle

CVE-2014-4247

HIGH · 9.3 CVSS v2.0 Published 2014-07-17
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 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 Oracle Java SE 8u5 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to JavaFX.

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

Vulnerability in Oracle Java SE 8u5's JavaFX component allows remote attackers to achieve full compromise (confidentiality, integrity, availability) with high CVSS 9.3 score, indicating easily exploitable remote code execution or similar critical impact.

MitigationApply Oracle Critical Patch Update (CPU) for July 2014 or later to resolve the JavaFX vulnerability; alternatively, remove JavaFX/Java plugin from untrusted network contexts if patching is not feasible.

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.8.0
JreApplication
Affected:= 1.8.0

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
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 checks

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

  1. Identify installed Java version
    Run 'java -version' or 'java -fullversion' from command line to retrieve the installed Java version string
    Affected if Version displayed is 1.8.0 (exact match)
  2. Confirm JDK vs JRE installation
    Check if the system has JDK (development kit) or only JRE (runtime) installed by looking for 'java' binary location or checking in Control Panel > Programs > Java
    Affected if Either Oracle JDK 1.8.0 or Oracle JRE 1.8.0 is installed
  3. Verify JavaFX component presence
    Look for javafx packages in the Java installation directory (commonly in JRE/lib/ext or as a separate javafx runtime), or attempt to import javafx.scene in any deployed Java applications
    Affected if JavaFX runtime libraries are present in the Java 1.8.0 installation
  4. Check Java plugin status in browsers
    Inspect installed browser plugins (chrome://plugins in Chrome, Add-ons > Plugins in Firefox) for 'Java' or 'JavaFX' plugin entries enabled for web browser execution
    Affected if Java or JavaFX browser plugin is enabled and Java 1.8.0 is the underlying runtime

You are affected if Oracle Java SE 1.8.0 (JDK or JRE) with JavaFX component is installed and the Java/JavaFX browser plugin is enabled, as this specific version contains the vulnerable JavaFX code.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Update (CPU) for July 2014 or later to resolve the JavaFX vulnerability; alternatively, remove JavaFX/Java plugin from untrusted network contexts if patching is not feasible.

Recommended fix Moderate confidence

Java 8u11 or later (recommended: latest available Java 8 update for security fixes)

  1. 1. Identify all systems running JDK or JRE version 1.8.0 (Java 8u5)
  2. 2. Download and install a later version of Java 8 (such as Java 8u11 or later) from the official Oracle JDK download page or your organization's Java distribution source
  3. 3. Update the JAVA_HOME environment variable to point to the new Java installation directory
  4. 4. Verify that all applications depending on this Java version function correctly with the new installation
  5. 5. Ensure any deployment scripts, build tools, or container configurations referencing the old Java path are updated to use the new version
Caveat Application compatibility should be tested; some applications may have dependencies on specific Java 8 update versions

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

Fix this in Jdk Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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