Hmi 3 Control Panel FirmwareOperating system · Swisslog Healthcare

CVE-2021-37166

HIGH · 7.5 CVSS v3.1 Published 2021-08-02
Fix available
A fix is available. Upgrade to 7.2.5.7 or later.
See remediation →
84/100
Remediation priority · High
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 buffer overflow issue leading to denial of service was discovered in HMI3 Control Panel in Swisslog Healthcare Nexus Panel operated by released versions of software before Nexus Software 7.2.5.7. When HMI3 starts up, it binds a local service to a TCP port on all interfaces of the device, and takes extensive time for the GUI to connect to the TCP socket, allowing the connection to be hijacked by an external attacker.

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 · moderate confidence

A buffer overflow vulnerability in HMI3 Control Panel in Swisslog Healthcare Nexus Panel allows remote attackers to cause denial of service. The HMI3 service binds to a TCP port on all network interfaces (0.0.0.0) instead of localhost only, and the extended time for the GUI to connect creates a window for connection hijacking by external attackers.

MitigationUpdate to Nexus Software 7.2.5.7 or later to patch the buffer overflow vulnerability. Additionally, network segmentation should be implemented to restrict access to the HMI3 control panel interface from untrusted networks.

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
Hmi 3 Control Panel FirmwareOperating system
Affected:< 7.2.5.7

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Check HMI3 firmware version
    Access the HMI3 Control Panel web interface or check the firmware version through the admin console. Look for a version display in the system information or about section.
    Affected if The firmware version is displayed as lower than 7.2.5.7 (e.g., 7.2.5.6, 7.2.4.x, etc.)
  2. Identify HMI3 TCP port binding
    Run 'netstat -an' or 'ss -tlnp' on the device hosting the HMI3 Control Panel. Look for the HMI3 service listening on 0.0.0.0 rather than 127.0.0.1 or localhost.
    Affected if The HMI3 service is listening on 0.0.0.0 (all interfaces) instead of 127.0.0.1 (localhost only)
  3. Verify network exposure of HMI3 port
    Check firewall rules or network configuration to determine if the HMI3 TCP port is accessible from external networks. Use 'iptables -L' or check network segmentation configurations.
    Affected if The HMI3 port is reachable from untrusted network segments or the internet

You are affected if the HMI3 firmware version is below 7.2.5.7 AND the service is bound to 0.0.0.0 with exposure to untrusted networks.

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

Update to Nexus Software 7.2.5.7 or later to patch the buffer overflow vulnerability. Additionally, network segmentation should be implemented to restrict access to the HMI3 control panel interface from untrusted networks.

Fix this in Hmi 3 Control Panel Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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