CVE-2019-11993
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 · uneditedA security vulnerability has been identified in HPE SimpliVity 380 Gen 9, HPE SimpliVity 380 Gen 10, HPE SimpliVity 380 Gen 10 G, HPE SimpliVity 2600 Gen 10, SimpliVity OmniCube, SimpliVity OmniStack for Cisco, SimpliVity OmniStack for Lenovo and SimpliVity OmniStack for Dell nodes. Two now deprecated APIs run as root, accept a file name path, and can be used to create or delete arbitrary files on the nodes. These APIs do not require user authentication and are accessible over the management network, resulting in remote availability and integrity vulnerabilities For all customers running HPE OmniStack version 3.7.9 and earlier. HPE recommends upgrading the OmniStack software to version 3.7.10 or later, which contains a permanent resolution. Customers and partners who can upgrade to 3.7.10 should upgrade at the earliest convenience. For all customers and partners unable to upgrade their environments to the recommended version 3.7.10, HPE has created a Temporary Workaround https://support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=mmr_sf-EN_US000061675&withFrame for you to implement. All customer should upgrade to the recommended 3.7.10 or later version at the earliest convenience.
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 confidenceTwo deprecated APIs in HPE SimpliVity (and OmniStack variants) run as root, accept file name paths without sanitization, and allow unauthenticated remote attackers to create or delete arbitrary files on the node through the management network. This path traversal/file manipulation vulnerability with no authentication and root privileges yields remote availability and integrity compromise.
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>= 3.6.2, <= 3.7.9>= 3.7.8, <= 3.7.9>= 3.7.1, <= 3.7.9>= 3.7.5, <= 3.7.9>= 3.0.8, <= 3.7.9>= 3.0.8, <= 3.7.9>= 3.0.8, <= 3.7.9>= 3.0.8, <= 3.7.9CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the HPE SimpliVity or OmniStack product modelAccess the appliance management interface or use the command line interface (CLI) to retrieve the system model information. This is typically found in the OmniStack controller or vCenter management console under the appliance details.Affected if The system is any of these models: SimpliVity 380 Gen9, 380 Gen10 G, 380 Gen10, 2600 Gen10, Omnicube, Omnistack for Dell, Omnistack for Cisco, or Omnistack for Lenovo.
-
Determine the installed firmware versionUse the HPE SimpliVity management interface, OmniStack CLI, or vCenter plugin to view the current firmware version. This is usually accessible through the appliance health or version information panel.Affected if The firmware version falls within any of these ranges: 3.6.2 to 3.7.9, 3.7.8 to 3.7.9, 3.7.1 to 3.7.9, 3.7.5 to 3.7.9, or 3.0.8 to 3.7.9 depending on the specific model.
-
Verify whether deprecated APIs are exposed on the management networkReview the appliance network configuration and firewall rules to determine if the management network interface is accessible externally. Check for any open ports or services corresponding to the deprecated HPE SimpliVity APIs.Affected if The management network interface is externally accessible and the deprecated APIs are running and reachable over the network.
-
Confirm unauthenticated access to the API endpointsAttempt a locally initiated request to the API endpoints (if known from internal documentation) or review access control configurations to verify whether authentication is required for the deprecated API functions.Affected if The deprecated APIs accept requests without requiring authentication credentials.
A system is affected if it is any HPE SimpliVity or OmniStack model with firmware version between 3.0.8/3.6.2/3.7.1/3.7.5/3.7.8 (depending on model) and 3.7.9 inclusive, and the management network can reach the deprecated APIs without authentication.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade HPE OmniStack to version 3.7.10 or later which contains the permanent fix. For environments unable to upgrade immediately, implement HPE's temporary workaround from the official support document.
- Consultation3.0 h
- Implementation6.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11993 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-11993 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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