dbcve.org
Hyperflex Hx Data PlatformOperating system · Cisco

CVE-2019-1666

MEDIUM · 5.3 CVSS v3.1 Published 2019-02-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable 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 Graphite service of Cisco HyperFlex software could allow an unauthenticated, remote attacker to retrieve data from the Graphite service. The vulnerability is due to insufficient authentication controls. An attacker could exploit this vulnerability by sending crafted requests to the Graphite service. A successful exploit could allow the attacker to retrieve any statistics from the Graphite service. Versions prior to 3.5(2a) are affected.

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

The vulnerability exists in the Graphite service of Cisco HyperFlex software, where insufficient authentication controls allow unauthenticated remote attackers to retrieve arbitrary statistics by sending crafted requests to the service. This exposure enables an attacker to access sensitive performance and system metrics without any credentials.

MitigationUpgrade Cisco HyperFlex to version 3.5(2a) or later to resolve the authentication deficiency. If immediate upgrading is not feasible, implement network segmentation or firewall rules to restrict unauthorized access to the Graphite service port.

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:= 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify HyperFlex Hx Data Platform version
    Run 'show version' on the HyperFlex cluster controller or check the HX Data Platform version via the HX Connect web interface under Cluster > Information
    Affected if The installed version matches 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)
  2. Identify if Graphite service is enabled
    Check for the Graphite service process listening on port 2003 (default Graphite plaintext) or port 2004 (Graphite pickle) by running 'netstat -an | grep -E "2003|2004"' or 'ss -tlnp | grep -E "2003|2004"' on HyperFlex nodes
    Affected if The Graphite service is listening and accessible on any network interface
  3. Check Graphite service network exposure
    Verify if port 2003/2004 is bound to all interfaces (0.0.0.0) rather than localhost only, and test external connectivity by attempting a telnet or nc connection to those ports from an untrusted network segment
    Affected if The Graphite port is accessible from network segments outside the trusted management network
  4. Test Graphite unauthenticated access
    Send a test metric retrieval request to the Graphite service using echo -e "test.metric 123 $(date +%s)" | nc -w 3 <target_ip> 2003 followed by a query to verify if metrics can be retrieved without authentication
    Affected if Metrics can be retrieved or pushed without any authentication credentials
  5. Review firewall and ACL rules for Graphite port
    Check iptables rules with 'iptables -L -n' or HyperFlex firewall configuration to determine if port 2003/2004 is explicitly blocked or allowed for external IPs
    Affected if No firewall rule blocks unauthenticated access to the Graphite service from untrusted networks

You are affected if your HyperFlex Hx Data Platform version is any of the listed versions AND the Graphite service is network-accessible without authentication controls.

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 to version 3.5(2a) or later to resolve the authentication deficiency. If immediate upgrading is not feasible, implement network segmentation or firewall rules to restrict unauthorized access to the Graphite service port.

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-2019-1666 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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