CVE-2022-24611
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 · uneditedDenial of Service (DoS) in the Z-Wave S0 NonceGet protocol specification in Silicon Labs Z-Wave 500 series allows local attackers to block S0/S2 protected Z-Wave network via crafted S0 NonceGet Z-Wave packages, utilizing included but absent NodeIDs.
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 confidenceA denial of service vulnerability exists in the Z-Wave S0 NonceGet protocol implementation in Silicon Labs Z-Wave 500 series devices. Local attackers can craft malicious S0 NonceGet packets using NodeIDs that are included in the network configuration but not actually present on the network, causing disruption to S0/S2 protected Z-Wave 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 dataall versionsall versionsall versionsall versionsall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Z-Wave device modelCheck the device label, documentation, or network management interface to determine the exact Silicon Labs Z-Wave device model (e.g., Zm5202, Zm5101, Sd3503, Sd3502, or Zm5304)Affected if The device is any of these five models: Zm5202, Zm5101, Sd3503, Sd3502, or Zm5304
-
Confirm Z-Wave firmware versionAccess the device firmware information through the Z-Wave controller interface, device documentation, or network management tools to retrieve the installed firmware versionAffected if The device is running any firmware version on the affected model line (all versions are affected)
-
Verify S0 or S2 security is enabledCheck the Z-Wave network configuration to determine if S0 or S2 security classes are active for any devices or associations in the networkAffected if S0 or S2 security is enabled - the vulnerability exploits the S0 NonceGet protocol in protected networks
-
Review Z-Wave network NodeID configurationUse the Z-Wave controller or network management tool to list all configured NodeIDs in the network, then compare against actively responding devices to identify orphaned NodeIDs (included in config but not present on network)Affected if The network contains NodeIDs that are in the configuration but do not correspond to active devices - these are the vectors for the attack
-
Check for network disruption symptomsMonitor Z-Wave network traffic or controller logs for unusual patterns such as repeated NonceGet requests, failed commands, or network latency affecting S0/S2 secured devicesAffected if The network shows signs of DoS such as repeated failed commands to non-existent nodes or degraded S0/S2 device responsiveness
You are affected if your Z-Wave network uses any of the five affected device models (Zm5202, Zm5101, Sd3503, Sd3502, Zm5304) with S0 or S2 security enabled, particularly if your network configuration contains orphaned NodeIDs that could be exploited for the DoS attack.
Generated from the published advisory. Verify against your own configuration.
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 dataContact Silicon Labs for firmware updates addressing the S0 NonceGet protocol specification. Ensure network segmentation and physical access controls are in place to limit local attack vectors until patches are applied.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24611 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-24611 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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