dbcve.org
JdkApplication · Oracle

CVE-2015-4844

HIGH · 10.0 CVSS v2.0 Published 2015-10-21
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 6u101, 7u85, and 8u60, and Java SE Embedded 8u51, allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to 2D.

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 unspecified vulnerability in Oracle Java SE's 2D graphics subsystem (affecting versions 6u101, 7u85, 8u60 and Embedded 8u51) allows remote attackers to execute arbitrary code with the privileges of the Java process, impacting confidentiality, integrity, and availability.

MitigationApply the corresponding Oracle security updates (CPU October 2015) to all affected Java installations; until patched, disable Java browser plugins and restrict network exposure of Java-enabled services.

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.6.0= 1.7.0= 1.8.0
JreApplication
Affected:= 1.6.0= 1.7.0= 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
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. Identify installed Java version
    Run 'java -version' or 'java -fullversion' from command line to obtain the exact version number
    Affected if Version displays as 1.6.0, 1.7.0, or 1.8.0 without the October 2015 security updates (prior to 6u101, 7u85, or 8u60 respectively)
  2. Confirm Java vendor and update channel
    Run 'java -verbose' or check the Java Control Panel to confirm this is Oracle Java SE (not OpenJDK or other implementations)
    Affected if The installation is Oracle Java SE rather than OpenJDK or alternative implementations
  3. Determine Java deployment context
    Check if Java browser plugin is enabled: examine browser plugin settings, or search for 'deployJava' files in the Java installation directory (jre/bin/plugin2 or similar)
    Affected if Java browser plugin is installed and enabled, allowing Java applets to run in web browsers
  4. Identify Java network exposure
    Review running Java processes with 'jps -l' or 'ps aux | grep java' to see if Java services are listening on network ports
    Affected if Java applications or services are exposed to network access without proper authentication or sandboxing

You are affected if your Oracle Java installation matches versions 1.6.0, 1.7.0, or 1.8.0 prior to the October 2015 critical patch updates (pre-6u101, pre-7u85, pre-8u60) AND the 2D graphics subsystem is accessible through browser plugins or network-exposed Java services.

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
Patch available Apply the vendor patch
Vendor patch www.oracle.com →
Interim mitigation

Apply the corresponding Oracle security updates (CPU October 2015) to all affected Java installations; until patched, disable Java browser plugins and restrict network exposure of Java-enabled services.

Recommended fix High confidence

Java 6 to 6u111+/Java 7 to 7u91+/Java 8 to 8u66+ (or migrate to latest supported LTS such as Java 11/17/21)

  1. 1. Identify all systems running Java JDK or JRE versions 1.6.0 through 1.6.0_101, 1.7.0 through 1.7.0_85, or 1.8.0 through 1.8.0_60
  2. 2. Determine your organization's supported Java version requirement (Java 6 is End of Life, consider upgrading to Java 7 or 8)
  3. 3. Download the latest patched Java version from Oracle's official download page: https://www.oracle.com/java/technologies/downloads/
  4. 4. For Java 6 users: Upgrade to Java 6u111 or later (or migrate to Java 7/8 as Java 6 is EOL)
  5. 5. For Java 7 users: Upgrade to Java 7u91 or later
  6. 6. For Java 8 users: Upgrade to Java 8u66 or later
  7. 7. Install the patched Java version on all affected systems
  8. 8. Verify the installed version using 'java -version' command
Caveat Java 6 is End-of-Life and no longer receives public updates; upgrading to newer Java versions may introduce API incompatibilities requiring code changes

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

Fix this in Jdk Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the patch applied

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 locally
dbcve dependency scanner

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