dbcve.org
JdkApplication · Oracle

CVE-2015-4731

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; Java SE Embedded 7u75; and Java SE Embedded 8u33 allows remote attackers to affect confidentiality, integrity, and availability via vectors related to JMX.

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 · high confidence

Unspecified vulnerability in Oracle Java SE JMX (Java Management Extensions) component allows remote attackers to fully compromise confidentiality, integrity, and availability. The CVSS 10 score indicates trivial exploitability with complete impact.

MitigationUpgrade to a patched Java version beyond 8u45 (for Java 8), 7u80 (for Java 7), or 6u95 (for Java 6). If JMX is not required, disable it to reduce attack surface.

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 the command line to obtain the exact Java version number
    Affected if Version displays as 1.6.0, 1.7.0, or 1.8.0 (any update patch level within these major versions)
  2. Locate Java installation directory
    On Windows: check JAVA_HOME environment variable or registry. On Linux/Unix: run 'which java' and 'readlink -f $(which java)' to find the JRE/JDK installation path
    Affected if The installation path contains references to JDK or JRE 1.6, 1.7, or 1.8
  3. Verify JMX is enabled
    Search startup scripts (startup.sh, catalina.sh, standalone.conf) for '-Dcom.sun.management.jmxremote' or similar JMX flags, or check for port 9090 or 9010 which are common JMX default ports in process listings (netstat -an | grep -E '9090|9010')
    Affected if JMX remote management flags are present in startup configuration or JMX ports are actively listening
  4. Check for JMX authentication disabled
    Review JMX configuration files or startup parameters for '-Dcom.sun.management.jmxremote.authenticate=false' which disables JMX authentication
    Affected if JMX is enabled AND authentication is explicitly disabled (vulnerability impact is higher)
  5. Confirm Java vendor is Oracle
    Run 'java -verbose' or check the vendor string from 'java -version' output (look for 'Oracle Corporation' or 'Java(TM)')
    Affected if Vendor is Oracle and version falls in affected range

System is affected if running Oracle JDK/JRE versions 1.6.0, 1.7.0, or 1.8.0 with JMX remote management enabled, regardless of authentication settings.

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 patched Java version beyond 8u45 (for Java 8), 7u80 (for Java 7), or 6u95 (for Java 6). If JMX is not required, disable it to reduce attack surface.

Recommended fix High confidence

Java SE 6u95+/7u80+/8u45+ (July 2015 CPU or later)

  1. 1. Identify all systems running affected Java versions (1.6.0, 1.7.0, 1.8.0)
  2. 2. Download the appropriate patched Java version from Oracle's official website or your organization's Java distribution channel
  3. 3. For Java 1.6.x systems: upgrade to Java SE 6u95 or later
  4. 4. For Java 1.7.x systems: upgrade to Java SE 7u80 or later
  5. 5. For Java 1.8.x systems: upgrade to Java SE 8u45 or later
  6. 6. Test applications thoroughly after upgrade to ensure compatibility
  7. 7. Deploy the updated Java runtime to all affected production systems
Caveat Minor - verify application compatibility; some deprecated APIs may require updates

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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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