Hyperflex Hx Data PlatformOperating system · Cisco

CVE-2019-1958

HIGH · 8.8 CVSS v3.1 Published 2019-08-08
Fix available
A fix is available. Upgrade to 4.0 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 web-based management interface of Cisco HyperFlex Software could allow an unauthenticated, remote attacker to conduct a cross-site request forgery (CSRF) attack on an affected system. The vulnerability is due to insufficient CSRF protections for the web UI on an affected device. An attacker could exploit this vulnerability by persuading a user of the interface to follow a malicious link. A successful exploit could allow the attacker to perform arbitrary actions with the privilege level of the affected user.

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

This is a Cross-Site Request Forgery (CSRF) vulnerability in Cisco HyperFlex Software's web-based management interface. The vulnerability exists because the web UI lacks proper CSRF protection mechanisms, allowing an unauthenticated remote attacker to craft malicious links that, when clicked by an authenticated user, can cause the user's browser to perform unauthorized actions with that user's privilege level.

MitigationEnable and implement CSRF protections in the web-based management interface, including anti-CSRF tokens for state-changing operations and validation of Origin/Referer headers. Users should be advised to avoid clicking untrusted links while authenticated to the management interface.

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 PlatformOperating system
Affected:< 4.0\(2a\)

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 if Cisco HyperFlex Hx Data Platform is installed
    Locate the HyperFlex installation by checking for Hx Data Platform components, or access the management interface URL and look for HyperFlex branding and login page
    Affected if The system runs Cisco HyperFlex Hx Data Platform software
  2. Check the installed version of HyperFlex Hx Data Platform
    Access the web management interface, navigate to the About or System Information page, or run 'hxsh' commands to retrieve the version number
    Affected if The installed version is earlier than 4.0(2a)
  3. Confirm the web-based management interface is accessible
    Attempt to access the HyperFlex web UI via HTTPS on the management IP address
    Affected if The web management interface is reachable and accepts authentication
  4. Verify the CSRF protection mechanism is absent
    Submit a state-changing request (such as creating a user or modifying settings) without the proper CSRF token headers and observe if the request is accepted
    Affected if The web interface accepts state-changing operations without validating CSRF tokens or Origin/Referer headers

The environment is affected if Cisco HyperFlex Hx Data Platform version 4.0(2a) or later is not installed, and the web management interface processes requests without CSRF token validation.

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 4.0 or later
Fixed in 4.0
Interim mitigation

Enable and implement CSRF protections in the web-based management interface, including anti-CSRF tokens for state-changing operations and validation of Origin/Referer headers. Users should be advised to avoid clicking untrusted links while authenticated to the management interface.

Fix this in Hyperflex Hx Data Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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