dbcve.org
JdkApplication · Oracle

CVE-2015-4732

HIGH · 10.0 CVSS v2.0 Published 2015-07-16
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 6u95, 7u80, and 8u45, and Java SE Embedded 7u75 and 8u33 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to Libraries, a different vulnerability than CVE-2015-2590.

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 versions 6u95, 7u80, 8u45 and Java SE Embedded 7u75, 8u33 affecting the Libraries component. The flaw allows remote attackers to achieve complete compromise of confidentiality, integrity, and availability via unknown vectors.

MitigationUpgrade to Java versions that include the security patch (Java 8u51 or later for the 8u45 branch, or later supported versions). Prioritize remediation given the CVSS 10 severity indicating trivial exploitability.

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. Verify Java installation exists
    Run 'java -version' or 'which java' on the command line to confirm Java is installed on the system
    Affected if No Java installation is found - the system is not affected by this CVE
  2. Determine installed Java version
    Execute 'java -version' and note the full version string (for example: 1.8.0_45 or 1.7.0_80)
    Affected if The version shown is 1.6.0, 1.7.0, or 1.8.0 at any patch level prior to the fixed releases
  3. Identify JDK vs JRE installation
    Check if the system has the JDK (Development Kit) or only the JRE (Runtime) by looking for the 'javac' compiler executable: 'which javac' or 'ls $JAVA_HOME/bin/javac'
    Affected if Either JDK or JRE is installed at a vulnerable version - both are affected
  4. Confirm Libraries component is in use
    This vulnerability affects the Libraries component. Verify Java is actively used for applications or applets that may load untrusted code or make network connections
    Affected if Java is running and processing untrusted code or network data - the exploitation vector is present
  5. Check for specific vulnerable patch levels
    Compare your full version string (including update number) against known vulnerable versions: 6u95, 7u75, 7u80, 8u33, 8u45. Run 'java -fullversion' for more detail if available
    Affected if The installed patch level matches or predates one of these vulnerable update versions

You are affected if Java 1.6.0, 1.7.0, or 1.8.0 is installed at any patch level prior to the security patches (8u51 or later for the 8 branch, equivalent for 7u and 6u branches).

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 Java versions that include the security patch (Java 8u51 or later for the 8u45 branch, or later supported versions). Prioritize remediation given the CVSS 10 severity indicating trivial exploitability.

Recommended fix High confidence

Java 8u51 or later (or Java 11/17 LTS for long-term support)

  1. Identify the currently installed Java version by running 'java -version'
  2. Download the latest JDK 8 update from Oracle's official download page or your organization's Java distribution
  3. Remove the vulnerable Java installation using your system's package manager (e.g., 'yum remove java-1.6.0-openjdk' or 'apt-get remove openjdk-6-jdk')
  4. Install the new Java version using your package manager or by extracting the downloaded tarball to /usr/local/java/
  5. Set the JAVA_HOME environment variable to point to the new installation (e.g., 'export JAVA_HOME=/usr/local/java/jdk1.8.0_xxx')
  6. Update the PATH variable to include the new Java bin directory: 'export PATH=$JAVA_HOME/bin:$PATH'
  7. Verify the installation by running 'java -version' and 'javac -version' to confirm the new version is active
  8. Ensure any applications using the old Java path are updated or restarted to use the new version
Caveat Some legacy applications may have compatibility issues with newer Java versions; test thoroughly before deploying to production

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-4732 — 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-4732 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