CVE-2019-11994
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. An API is used to execute a command manifest file during upgrade does not correctly prevent directory traversal and so can be used to execute manifest files in arbitrary locations on the node. The API does not require user authentication and is accessible over the management network, resulting in the potential for unauthenticated remote execution of manifest files. 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_US000061901&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 confidenceA directory traversal vulnerability exists in the HPE SimpliVity upgrade API that executes command manifest files without proper path validation. The API lacks authentication and allows unauthenticated attackers to execute arbitrary manifest files in any location on the node by manipulating file paths, resulting in unauthenticated remote code execution.
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.5.2, <= 3.7.9>= 3.5.2, <= 3.7.9>= 3.5.2, <= 3.7.9>= 3.5.2, <= 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/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 checksWork through these to decide whether this CVE applies to you.
-
Identify HPE SimpliVity product modelLog into the HPE SimpliVity management interface or use the `svt-cli` command if available, and determine the exact model (e.g., SimpliVity 380 Gen9, 2600 Gen10, Omnicube, Omnistack for Dell/Cisco/Lenovo)Affected if The model matches any of the known affected product lines (380 Gen9, 380 Gen10 G, 380 Gen10, 2600 Gen10, Omnicube, Omnistack for Dell, Omnistack for Cisco, Omnistack for Lenovo)
-
Check installed firmware versionAccess the HPE SimpliVity admin console or use the command line interface to retrieve the current firmware version. This is typically found in the system information or firmware management sectionAffected if The firmware version falls within any of these ranges: >= 3.6.2 and <= 3.7.9 (for 380 Gen9), >= 3.7.8 and <= 3.7.9 (for 380 Gen10 G), >= 3.7.1 and <= 3.7.9 (for 380 Gen10), >= 3.7.5 and <= 3.7.9 (for 2600 Gen10), or >= 3.5.2 and <= 3.7.9 (for Omnicube and all Omnistack variants)
-
Verify upgrade API accessibilityAttempt to access the upgrade API endpoint on the SimpliVity node (typically port 443 or a management interface). The vulnerability exists in the upgrade API that processes manifest files. Check if this API is exposed and respondingAffected if The upgrade API is accessible and accepts requests without authentication - this is the vulnerable condition required for exploitation
-
Confirm path validation behaviorIf you have authorization to safely test, observe whether the upgrade API permits path traversal in manifest file paths (e.g., references to files outside the expected manifest directory). This check should only be performed in authorized testing environmentsAffected if The API allows arbitrary file path specifications in manifest file references without proper validation, indicating the directory traversal vulnerability is present
The environment is affected if the product is an HPE SimpliVity model with firmware version 3.5.2 through 3.7.9 (specific to each model) and the upgrade API is accessible 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.
dbcve · scopedUpgrade HPE OmniStack to version 3.7.10 or later to apply the permanent fix. For environments unable to upgrade immediately, implement the temporary workaround documented in HPE security bulletin.
HPE SimpliVity OmniStack 3.7.10 or later
- Schedule the upgrade during a planned maintenance window to minimize business impact
- Download HPE SimpliVity OmniStack version 3.7.10 or later from the HPE Support Center (support.hpe.com)
- Follow HPE's documented upgrade procedure for your specific SimpliVity model (OmniCube, Omnistack for Dell/Lenovo/Cisco, or SimpliVity 380/2600)
- Apply the upgrade to all affected nodes in the cluster following HPE's recommended sequence
- Verify the upgrade completed successfully by checking the firmware version in the management interface
- Confirm the path traversal vulnerability is remediated by verifying the API no longer accepts directory traversal sequences
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11994 — 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-11994 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