dbcve.org
JdkApplication · Oracle

CVE-2015-4843

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 Libraries.

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

This is an unspecified vulnerability in the Libraries component of Oracle Java SE 6u101, 7u85, 8u60 and Java SE Embedded 8u51. The vulnerability allows remote attackers to achieve complete compromise of confidentiality, integrity, and availability via unknown vectors.

MitigationUpgrade to a Java version beyond the affected releases (Java 6u101+, 7u85+, or 8u60+), or migrate to more recent Java LTS versions such as Java 11 or 17, after compatibility testing.

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. Check installed Java version
    Run `java -version` from the command line to display the installed JRE/JDK version information
    Affected if The version shown is 1.6.0 up to but not including 1.6.0_101, 1.7.0 up to but not including 1.7.0_85, or 1.8.0 up to but not including 1.8.0_60 (or 1.8.0_51 for Embedded)
  2. Identify all Java installations on the system
    Search for java executables in common locations such as /usr/bin/, /usr/lib/jvm/, /opt/java/, or use `which java` and `find /usr -name java -type f`
    Affected if Any java binary found resolves to a version in the vulnerable ranges identified in step 1
  3. Check Java runtime in use by applications
    Identify running Java processes with `ps aux | grep java` or by checking application configurations that reference Java home paths
    Affected if Any active Java process or application configuration points to a vulnerable Java version

The environment is affected if any installed or running Java version falls below 1.6.0_101, 1.7.0_85, or 1.8.0_60 (or 1.8.0_51 for Embedded).

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

Upgrade to a Java version beyond the affected releases (Java 6u101+, 7u85+, or 8u60+), or migrate to more recent Java LTS versions such as Java 11 or 17, after compatibility testing.

Recommended fix High confidence

Java 6u102+, Java 7u91+, or Java 8u71+ (or Java 11 LTS for long-term support)

  1. 1. Identify the currently installed Java version by running 'java -version' or checking the system package manager
  2. 2. For Java 6: upgrade to Java SE 6u102 or later from http://www.oracle.com/technetwork/java/javase/downloads/index.html
  3. 3. For Java 7: upgrade to Java SE 7u91 or later from http://www.oracle.com/technetwork/java/javase/downloads/index.html
  4. 4. For Java 8: upgrade to Java SE 8u71 or later from http://www.oracle.com/technetwork/java/javase/downloads/index.html
  5. 5. Alternatively, upgrade to Java 8 (8u72 or later) or Java 11 LTS for longer term support and security patches
  6. 6. Verify the new Java version is active by running 'java -version' after installation
  7. 7. Update any JAVA_HOME environment variables or application configurations to point to the new Java installation path
Caveat May require testing of applications for compatibility with newer Java versions; some deprecated APIs or features may be removed in newer versions

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 the patch applied

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-2015-4843 — 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-4843 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