Hyperflex Hx Data PlatformApplication · Cisco

CVE-2018-15380

HIGH · 8.8 CVSS v3.0 Published 2019-02-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
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
A vulnerability in the cluster service manager of Cisco HyperFlex Software could allow an unauthenticated, adjacent attacker to execute commands as the root user. The vulnerability is due to insufficient input validation. An attacker could exploit this vulnerability by connecting to the cluster service manager and injecting commands into the bound process. A successful exploit could allow the attacker to run commands on the affected host as the root user. This vulnerability affects Cisco HyperFlex Software releases prior to 3.5(2a).

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

Command injection vulnerability in Cisco HyperFlex Software's cluster service manager allows an unauthenticated, adjacent attacker to inject and execute arbitrary commands as root due to insufficient input validation on the bound process.

MitigationUpgrade Cisco HyperFlex Software to release 3.5(2a) or later to patch the command injection vulnerability in the cluster service manager.

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
Hyperflex Hx Data PlatformApplication
Affected:= 3.0\(1a\)= 3.5\(1a\)

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

CVSS:3.0/AV:A/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. Identify Cisco HyperFlex installation
    Check if Cisco HyperFlex Hx Data Platform is deployed in the environment by querying the management interface or using the HyperFlex CLI tool (stcli) if available
    Affected if The system does not have Cisco HyperFlex Hx Data Platform installed, the check is not applicable
  2. Check Hx Data Platform version
    Use the stcli command 'stcli cluster version' or check the HyperFlex management UI under the cluster information section to retrieve the installed Hx Data Platform version number
    Affected if The installed version matches 3.0(1a) or 3.5(1a) exactly, indicating the vulnerable versions are present
  3. Verify cluster service manager is enabled
    Confirm the cluster service manager process is running and bound to a network interface. This can be checked via HyperFlex management interfaces or by reviewing the running services on the HyperFlex cluster nodes
    Affected if The cluster service manager is active and accessible on the network, making the command injection surface exposed
  4. Confirm adjacency access to cluster service manager
    Determine if the cluster service manager listener is bound to an interface accessible from the adjacent network segment rather than localhost only
    Affected if The service is reachable from adjacent network segments, allowing an unauthenticated adjacent attacker to reach the vulnerable endpoint

The environment is affected if Cisco HyperFlex Hx Data Platform version 3.0(1a) or 3.5(1a) is installed AND the cluster service manager is accessible from 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Cisco HyperFlex Software to release 3.5(2a) or later to patch the command injection vulnerability in the cluster service manager.

Fix this in Hyperflex Hx Data Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-15380 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-15380 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