dbcve.org
500 Series FirmwareOperating system · Silabs

CVE-2020-9060

MEDIUM · 6.5 CVSS v3.1 Published 2022-01-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
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
Z-Wave devices based on Silicon Labs 500 series chipsets using S2, including but likely not limited to the ZooZ ZST10 version 6.04, ZooZ ZEN20 version 5.03, ZooZ ZEN25 version 5.03, Aeon Labs ZW090-A version 3.95, and Fibaro FGWPB-111 version 4.3, are susceptible to denial of service and resource exhaustion via malformed SECURITY NONCE GET, SECURITY NONCE GET 2, NO OPERATION, or NIF REQUEST messages.

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

Z-Wave devices using Silicon Labs 500 series chipsets with S2 security are vulnerable to denial of service when receiving malformed SECURITY NONCE GET, SECURITY NONCE GET 2, NO OPERATION, or NIF REQUEST messages. These malformed messages cause resource exhaustion or device crashes.

MitigationApply vendor firmware updates when available; as a compensating control, network segment Z-Wave devices and restrict exposure to 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
500 Series FirmwareOperating system
Affected:all versions
Zw090 AOperating system
Affected:= 3.95
Fgwpb 111Operating system
Affected:= 4.3
Zen20Operating system
Affected:= 5.03
Zen25Operating system
Affected:= 5.03
Zst10Operating system
Affected:= 6.04

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

CVSS:3.1/AV:A/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. Identify your Z-Wave device model
    Check the physical device label, documentation, or your Z-Wave controller's device list to determine the exact model (e.g., Aeotec Zw090 A, Fibaro Fgwpb 111, Zooz Zen20, Zooz Zen25, Zooz Zst10)
    Affected if The device matches one of the affected models listed in the CVE (Aeotec Zw090 A, Fibaro Fgwpb 111, Zooz Zen20, Zooz Zen25, or Zooz Zst10)
  2. Determine the firmware version
    Access your Z-Wave controller interface and look for firmware version information for the device, or query the device directly using Z-Wave management tools
    Affected if The firmware version is 3.95 for Aeotec Zw090 A, 4.3 for Fibaro Fgwpb 111, 5.03 for Zooz Zen20 or Zooz Zen25, or 6.04 for Zooz Zst10, or if using Silabs 500 Series Firmware on any version
  3. Verify the chipset is Silicon Labs 500 series
    Check the device specifications, manual, or Z-Wave controller device info to confirm the chipset model; this information may also be visible in the Z-Wave device database
    Affected if The device uses a Silicon Labs 500 series chipset
  4. Confirm S2 security is enabled
    Check your Z-Wave controller to see if the device is included with S2 security class (Security 2); this is typically visible in the node information or device inclusion settings
    Affected if S2 security is enabled for the device inclusion (the vulnerability requires S2 security to be active)
  5. Assess network exposure
    Review your network configuration to determine if Z-Wave devices are accessible from untrusted networks or if they are properly segmented from external access
    Affected if The Z-Wave network is directly exposed to untrusted or external networks without firewall segmentation

You are affected if you have a device using Silicon Labs 500 series chipset with S2 security enabled, particularly if it is one of the listed models at the specified firmware versions, and the device is reachable from an untrusted 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware updates when available; as a compensating control, network segment Z-Wave devices and restrict exposure to untrusted networks.

Fix this in 500 Series Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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