# CVE-2022-24611: Denial of service in n/a

> Local attackers can block protected Z-Wave networks by sending crafted S0 NonceGet packages with invalid NodeIDs in Silicon Labs Z-Wave 500 series devices.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 May 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-q4jj-h5gh-j3vm

## What is CVE-2022-24611?

CVE-2022-24611 is a medium-severity denial of service vulnerability in n/a, published on 17 May 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Denial 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.

## Which versions are affected by CVE-2022-24611?

It affects 5 products.


Products: Silabs Sd3502 Firmware, Silabs Sd3503 Firmware, Silabs Zm5101 Firmware, Silabs Zm5202 Firmware, Silabs Zm5304 Firmware.

## How do I fix CVE-2022-24611?

No fix has been published for CVE-2022-24611 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-24611 being exploited?

There is no known exploitation of CVE-2022-24611 in the wild and no public exploit code.

Public exploit code:

- Details regarding the Z-Wave S0-No-More attack (github_poc): https://github.com/ITSecLab-HSEL/CVE-2022-24611

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-24611 and fix it if it is affected.

What it is: CVE-2022-24611 is a medium-severity denial of service vulnerability in n/a, published on 17 May 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-24611 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-24611/ (Markdown: https://insights.sbomify.com/CVE-2022-24611/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-24611
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-24611
- OSV: https://osv.dev/vulnerability/CVE-2022-24611

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-24611/
Summaries are generated and may contain mistakes; the official description above is the record.