dbcve.org
Esrs Policy ManagerApplication · Emc

CVE-2018-15764

CRITICAL · 9.8 CVSS v3.0 Published 2018-09-28
Fix available
A fix is available. Upgrade to after 6.8 or later.
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
Dell EMC ESRS Policy Manager versions 6.8 and prior contain a remote code execution vulnerability due to improper configurations of triggered JMX services. A remote unauthenticated attacker may potentially exploit this vulnerability to execute arbitrary code in the server's JVM.

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

Dell EMC ESRS Policy Manager versions 6.8 and prior expose JMX services with improper configurations, allowing remote unauthenticated attackers to inject and execute arbitrary Java code within the server's JVM context.

MitigationRestrict JMX access by enabling authentication, using SSL/TLS for JMX connections, and applying proper role-based access controls; upgrade to a patched version if available.

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
Esrs Policy ManagerApplication
Affected:<= 6.8

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Confirm ESRS Policy Manager is installed
    Check for ESRS Policy Manager installation directory, typically under /opt/emc/esrs/policy-manager or C:\Program Files\EMC\ESRS Policy Manager. Look for the policy-manager service or process running.
    Affected if ESRS Policy Manager is present on the system
  2. Identify the installed version
    Locate the version file or check the application properties. Common locations include version.properties in the installation directory, or the about/version section in the management console.
    Affected if The installed version is 6.8 or any version prior to 6.8
  3. Verify if JMX service is enabled and exposed
    Check the JMX configuration files (typically jmxremote.password, jmxremote.access, or the startup scripts) in the ESRS installation directory. Look for JMX connector configurations with ports commonly 8999, 9000, or 1099.
    Affected if JMX is enabled and configured without proper access restrictions
  4. Inspect JMX authentication configuration
    Examine the jmxremote.password and jmxremote.access files. Verify if authentication is enabled in the JMX connector configuration. Check for the presence of username/password entries.
    Affected if JMX authentication is disabled or the jmxremote.password file is missing or empty, meaning no credentials are required to access JMX
  5. Check if SSL/TLS is enforced for JMX connections
    Review the Java startup arguments for JMX-related flags such as -Dcom.sun.management.jmxremote.ssl=false or missing -Dcom.sun.management.jmxremote.ssl=true. Check the JMX connector configuration for SSL settings.
    Affected if SSL/TLS is disabled for JMX connections (com.sun.management.jmxremote.ssl=false or not set)
  6. Verify network exposure of JMX port
    Check if the JMX port binds to 0.0.0.0 or an external IP address rather than localhost only. Use netstat or ss to examine which network interfaces the JMX port is listening on.
    Affected if The JMX port is listening on all interfaces (0.0.0.0) making it externally accessible

A system is affected if ESRS Policy Manager version 6.8 or lower is installed with JMX enabled, no authentication configured, and SSL not enforced, especially if the JMX port is accessible from non-localhost network interfaces.

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.

From vendor data
Upgrade available Upgrade to a release after 6.8
Interim mitigation

Restrict JMX access by enabling authentication, using SSL/TLS for JMX connections, and applying proper role-based access controls; upgrade to a patched version if available.

Fix this in Esrs Policy Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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