Hyperflex Hx Data PlatformOperating system · Cisco
CVE-2019-1664
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 vulnerability in the hxterm service of Cisco HyperFlex Software could allow an unauthenticated, local attacker to gain root access to all nodes in the cluster. The vulnerability is due to insufficient authentication controls. An attacker could exploit this vulnerability by connecting to the hxterm service as a non-privileged, local user. A successful exploit could allow the attacker to gain root access to all member nodes of the HyperFlex cluster. 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 confidenceThe hxterm service in Cisco HyperFlex Software lacks proper authentication controls, allowing any local user to connect and escalate privileges to root on all cluster nodes. An unauthenticated attacker with local access can achieve full cluster compromise by exploiting this insufficient authorization mechanism.
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
= 2.6\(1a\)= 2.6\(1b\)= 2.6\(1d\)= 2.6\(1e\)= 3.0\(1a\)= 3.0\(1b\)= 3.0\(1c\)= 3.0\(1d\)= 3.0\(1e\)= 3.0\(1h\)= 3.0\(1i\)= 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Confirm Cisco HyperFlex installationIdentify if the system runs Cisco HyperFlex by checking for HyperFlex-specific directories (such as /opt/hxtools, /etc/hx), hyperflex-related processes, or the hyperflex cluster membershipAffected if System is running Cisco HyperFlex Software
-
Check Hx Data Platform versionLocate the installed Hx Data Platform version file or use the 'hxsh' CLI tool with 'version' command, or check /etc/hxrelease or similar version documentation filesAffected if Version equals any of: 2.6(1a), 2.6(1b), 2.6(1d), 2.6(1e), 3.0(1a), 3.0(1b), 3.0(1c), 3.0(1d), 3.0(1e), 3.0(1h), 3.0(1i), 3.5(1a)
-
Verify hxterm service is runningCheck for the hxterm process using 'ps' command or check if port 5000 (or the hxterm service port) is listeningAffected if hxterm service is running and bound to a network interface accessible to local users
Environment is affected if it runs Cisco HyperFlex Hx Data Platform version 2.6(1a) through 3.5(1a) with the hxterm service exposed to local users.
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 Cisco HyperFlex Software to version 3.5(2a) or later to remediate this vulnerability. As an interim measure, restrict network access to the hxterm service to trusted administrative segments.
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
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 locallyCheck whether your project pulls in CVE-2019-1664 — 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-1664 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