dbcve.org
UnisphereApplication · Emc

CVE-2015-0545

HIGH · 10.0 CVSS v2.0 Published 2015-06-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
EMC Unisphere for VMAX 8.x before 8.0.3.4 sets up the Java Debugging Wire Protocol (JDWP) service, which allows remote attackers to execute arbitrary code via unspecified vectors.

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

EMC Unisphere for VMAX versions 8.x prior to 8.0.3.4 ships with the Java Debugging Wire Protocol (JDWP) service enabled and accessible over the network. JDWP is a debugging protocol that, when exposed without authentication, allows a remote attacker to inject and execute arbitrary Java code on the target system, effectively achieving full remote code execution with the privileges of the Java process.

MitigationUpgrade to EMC Unisphere for VMAX 8.0.3.4 or later, which removes or disables the insecure JDWP service. If immediate patching is not feasible, network-level controls should be implemented to block access to the JDWP debugging port (typically 5005/tcp) from untrusted networks.

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
UnisphereApplication
Affected:= 8.0.0= 8.0.1= 8.0.2= 8.0.3

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 Unisphere version
    Locate the EMC Unisphere for VMAX installation and determine the exact version number. This is typically found in the software release notes, the installation directory, or the Unisphere web interface footer.
    Affected if The version is 8.0.0, 8.0.1, 8.0.2, or 8.0.3 (any version prior to 8.0.3.4).
  2. Verify JDWP debugging port is listening
    Run a network port scan or use the command 'netstat -an | grep 5005' or 'ss -tlnp | grep 5005' on the Unisphere server to check if port 5005/tcp is open and listening.
    Affected if Port 5005/tcp is in LISTEN state and bound to an accessible network interface.
  3. Test JDWP service accessibility
    Attempt a network connection to port 5005/tcp from a remote system using telnet, nc, or a JDWP client tool. A successful connection indicates the debugging service is network-accessible.
    Affected if TCP connections to port 5005/tcp are accepted from your testing system.
  4. Review network exposure of debugging port
    Inspect firewall rules, ACLs, or security group configurations to determine whether port 5005/tcp is reachable from untrusted networks or the internet.
    Affected if Port 5005/tcp is permitted through network filters from any untrusted or external network segment.

The environment is affected if Unisphere for VMAX version is 8.0.0 through 8.0.3 and the JDWP service on port 5005/tcp is exposed over the network.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to EMC Unisphere for VMAX 8.0.3.4 or later, which removes or disables the insecure JDWP service. If immediate patching is not feasible, network-level controls should be implemented to block access to the JDWP debugging port (typically 5005/tcp) from untrusted networks.

Recommended fix High confidence

Unisphere 8.0.3.4 or later (such as 8.0.4.x)

  1. Backup current Unisphere for VMAX configuration and data
  2. Upgrade Unisphere to version 8.0.3.4 or later (e.g., 8.0.3.4, 8.0.4.x)
  3. After upgrade, verify that the Java Debugging Wire Protocol (JDWP) service is disabled
  4. Confirm the upgrade was successful by logging into the Unisphere web interface and checking the version information

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

Fix this in Unisphere Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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