# CVE-2024-3051: Z/IP Gateway Device Reset Locally Denial of Service Vulnerability

> Attackers can send malformed commands to the Z/IP Gateway to temporarily deny service to end devices by preventing frame acknowledgments.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Apr 2024
- **Updated:** 27 Sep 2024
- **Also known as:** GHSA-cp7v-2p64-673r

## What is CVE-2024-3051?

CVE-2024-3051 is a high-severity denial of service vulnerability in silabs.com Z/IP Gateway SDK, published on 26 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Malformed Device Reset Locally command classes can be sent to temporarily deny service to an end device. Any frames sent by the end device will not be acknowledged by the gateway during this time.

Weakness: CWE-419 (Unprotected Primary Channel), CWE-248 (Uncaught Exception)

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


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

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

## Is CVE-2024-3051 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-3051 is a high-severity denial of service vulnerability in silabs.com Z/IP Gateway SDK, published on 26 Apr 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-3051 in the wild and no public exploit code.

Affected product: silabs.com Z/IP Gateway 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-3051/ (Markdown: https://insights.sbomify.com/CVE-2024-3051/index.md)
```

## Sources

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

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