dbcve.org
Hci H610s FirmwareOperating system · Netapp

CVE-2020-8573

MEDIUM · 6.5 CVSS v3.1 Published 2020-06-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
The NetApp HCI H610C, H615C and H610S Baseboard Management Controllers (BMC) are shipped with a documented default account and password that should be changed during the initial node setup. During upgrades to Element 11.8 and 12.0 or the Compute Firmware Bundle 12.2.92 the BMC account password on the H610C, H615C and H610S platforms is reset to the default documented value which could allow remote attackers to cause a Denial of Service (DoS).

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

NetApp HCI H610C, H615C, and H610S Baseboard Management Controllers have a documented default account and password that should be changed during initial setup. During upgrades to Element 11.8, 12.0, or Compute Firmware Bundle 12.2.92, the BMC password is reset to this default documented value, potentially allowing remote attackers with knowledge of the default credentials to access the BMC and cause Denial of Service.

MitigationAfter any affected upgrade, immediately change the default BMC password to a strong, unique password on all H610C, H615C, and H610S nodes. Consider documenting this as a required post-upgrade step in change management procedures.

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
Hci H610s FirmwareOperating system
Affected:all versions

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 the node model
    Check the physical or inventory list of NetApp HCI nodes to determine if the system includes H610C, H615C, or H610S compute nodes.
    Affected if The environment contains any H610C, H615C, or H610S nodes.
  2. Check the installed Element version
    Use the NetApp Element UI or API to view the current Element software version. Navigate to Cluster > About in the Element web interface or run GetElementVersion via API.
    Affected if The Element version is 11.8 or 12.0.
  3. Check the Compute Firmware Bundle version
    Use the NetApp HCI management node or compute node inventory to view the current Compute Firmware Bundle version. Check via the VMware vCenter or NetApp Deployment Engine.
    Affected if The Compute Firmware Bundle version is 12.2.92.
  4. Verify BMC password has been changed
    Access the Baseboard Management Controller web interface or use IPMI tooling to attempt authentication. Log into the BMC and check if the password has been modified from the documented default. Documented default credentials should be changed during initial setup per NetApp documentation.
    Affected if The BMC password remains at the documented default value.
  5. Check BMC network accessibility
    Ping the BMC IP addresses for all affected nodes and verify if the BMC management interfaces are reachable from untrusted networks. Review firewall rules and network segmentation for BMC interfaces.
    Affected if BMC interfaces are accessible from untrusted networks without proper network segmentation.

You are affected if you have H610C, H615C, or H610S nodes and either upgraded to Element 11.8, Element 12.0, or Compute Firmware Bundle 12.2.92 while the BMC password remains at the documented default value.

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

After any affected upgrade, immediately change the default BMC password to a strong, unique password on all H610C, H615C, and H610S nodes. Consider documenting this as a required post-upgrade step in change management procedures.

Fix this in Hci H610s Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing3.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,050
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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