# CVE-2024-22472: Long S0 frames received by 500 series Z-Wave devices may cause buffer overflow

> Attackers can cause buffer overflow via long S0 frames, leading to denial of service or remote code execution on Z-Wave devices.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 May 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-34vc-vhj3-rw45

## What is CVE-2024-22472?

CVE-2024-22472 is a high-severity memory corruption vulnerability in Silicon Labs Z-Wave SDK, published on 7 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A buffer Overflow vulnerability in Silicon Labs 500 Series Z-Wave devices may allow Denial of Service, and potential Remote Code execution

This issue affects all versions of Silicon Labs 500 Series SDK prior to v6.85.2

running on Silicon Labs 500 series Z-wave devices.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2024-22472?


## How do I fix CVE-2024-22472?

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

## Is CVE-2024-22472 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-22472 and fix it if it is affected.

What it is: CVE-2024-22472 is a high-severity memory corruption vulnerability in Silicon Labs Z-Wave SDK, published on 7 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-22472 in the wild and no public exploit code.

Affected product: Silicon Labs Z-Wave SDK. 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-2024-22472/ (Markdown: https://insights.sbomify.com/CVE-2024-22472/index.md)
```

## Sources

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

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