dbcve.org
JdkApplication · Oracle

CVE-2015-4901

HIGH · 9.3 CVSS v2.0 Published 2015-10-22
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 8u60 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

Remote code execution vulnerability in the JavaFX component of Oracle Java SE 8u60. The unspecified vulnerability allows remote attackers to affect confidentiality, integrity, and availability through unknown attack vectors in JavaFX.

MitigationApply Oracle's October 2015 Critical Patch Update for Java SE 8u60 or later to remediate the JavaFX 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
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 obtain the exact version string
    Affected if Version displayed is exactly 1.8.0 (build 1.8.0 or 1.8.0_xxx)
  2. Confirm Java implementation vendor
    Run 'java -version' and verify the vendor line shows Oracle JDK or Oracle JRE (not OpenJDK or other distributions)
    Affected if Vendor is Oracle and version is 1.8.0
  3. Determine if JavaFX runtime is present
    Check for the presence of jfxrt.jar in the Java lib directory (typically in $JAVA_HOME/lib/ or $JRE_HOME/lib/) or run 'java -verbose' to list loaded modules and look for javafx entries
    Affected if JavaFX runtime files (jfxrt.jar or javafx modules) exist in the Java installation directory
  4. Check for JavaFX usage in applications
    Inspect application classpath or deployment descriptors for references to javafx.* packages, or examine any Java Web Start (.jnlp) files for javafx component usage
    Affected if Applications invoke or load JavaFX classes or use JavaFX-based deployment mechanisms

You are affected if you have Oracle JDK or JRE version exactly 1.8.0 with JavaFX runtime present and actively used in your environment.

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's October 2015 Critical Patch Update for Java SE 8u60 or later to remediate the JavaFX vulnerability.

Recommended fix Moderate confidence

JDK 8u361 or later (latest available Java 8 release)

  1. 1. Identify all systems running JDK or JRE version 1.8.0
  2. 2. Download the latest JDK 8 from Oracle's official website (.oracle.com/java/technologies/downloads/) or your vendor's repository
  3. 3. Uninstall the affected JDK/JRE 1.8.0 from all affected systems
  4. 4. Install the latest JDK 8 (or at minimum 8u361 or later which includes the fix for this vulnerability)
  5. 5. Verify the installation by running 'java -version' to confirm the new version
  6. 6. Restart any applications or services that depend on the Java runtime
  7. 7. Test that critical applications function correctly with the updated Java version
Caveat Minor: Verify application compatibility with newer Java 8 updates; some deprecated APIs may generate warnings

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

Fix this in Jdk Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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