Hmi 3 Control Panel FirmwareOperating system · Swisslog Healthcare

CVE-2021-37160

CRITICAL · 9.8 CVSS v3.1 Published 2021-08-02
Fix available
A fix is available. Upgrade to 7.2.5.7 or later.
See remediation →
100/100
Remediation priority · Urgent
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 firmware validation issue was discovered in HMI3 Control Panel in Swisslog Healthcare Nexus Panel operated by released versions of software before Nexus Software 7.2.5.7. There is no firmware validation (e.g., cryptographic signature validation) during a File Upload for a firmware update.

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 Swisslog Healthcare Nexus Panel's HMI3 Control Panel lacks cryptographic signature validation during firmware updates. An attacker can upload and execute malicious firmware by exploiting the unauthenticated file upload mechanism, as the system does not verify the authenticity or integrity of firmware images before execution.

MitigationUpgrade to Nexus Software 7.2.5.7 or later which implements firmware signature validation. Until then, restrict network access to the panel and monitor for unauthorized firmware upload attempts.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

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

  1. Identify the firmware version installed on the HMI3 Control Panel
    Access the panel's web interface or administrative console and locate the firmware version information, typically found in the system status, about, or maintenance sections
    Affected if The installed firmware version is lower than 7.2.5.7
  2. Verify if firmware signature validation is enabled or present
    Check the panel's security or firmware update configuration settings for any option related to signature verification, code signing, or integrity checks
    Affected if No signature validation option exists or it is disabled, and the firmware version is below 7.2.5.7
  3. Confirm the unauthenticated firmware upload endpoint is accessible
    Attempt to access the firmware upload functionality on the panel without authentication, or review access logs for unauthenticated upload requests to the update mechanism
    Affected if The upload endpoint accepts firmware without requiring authentication and the firmware version is below 7.2.5.7
  4. Assess network exposure of the HMI3 Control Panel
    Determine if the panel is directly accessible from untrusted networks or the internet by reviewing firewall rules, ACLs, and network segmentation
    Affected if The panel is exposed to untrusted networks and runs firmware below version 7.2.5.7

You are affected if the HMI3 Control Panel is running firmware version lower than 7.2.5.7 and the unauthenticated firmware upload mechanism is accessible on the network.

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.

dbcve · scoped
Upgrade available Upgrade to 7.2.5.7 or later
Fixed in 7.2.5.7
Interim mitigation

Upgrade to Nexus Software 7.2.5.7 or later which implements firmware signature validation. Until then, restrict network access to the panel and monitor for unauthorized firmware upload attempts.

Recommended fix High confidence

Nexus Software 7.2.5.7

  1. Obtain Nexus Software version 7.2.5.7 or later from Swisslog Healthcare's official distribution channel
  2. Review Swisslog Healthcare's official firmware upgrade documentation for the HMI3 Control Panel
  3. Apply the firmware update to the Nexus Panel following the vendor's prescribed upgrade procedure
  4. Confirm the firmware version has been successfully updated to 7.2.5.7 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Hmi 3 Control Panel Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation32.0 h
  • Testing20.0 h
  • Review / QA12.0 h
72.0 hours of engineering $12,520
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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