# CVE-2024-3043: Zigbee co-ordinator realignment packet may lead to denial of service

> Unauthenticated Zigbee packets can force network identifier changes, causing denial of service in devices using the Ember ZNet SDK.

- **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:** 27 Jun 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-44x3-2gc7-3w5m

## What is CVE-2024-3043?

CVE-2024-3043 is a high-severity denial of service vulnerability in silabs.com Ember ZNet SDK, published on 27 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unauthenticated IEEE 802.15.4 'co-ordinator realignment' packet can be used to force Zigbee nodes to change their network identifier (pan ID), leading to a denial of service. This packet type is not useful in production and should be used only for PHY qualification.

Weakness: CWE-829 (Inclusion of Functionality from Untrusted Control Sphere)

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


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

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

## Is CVE-2024-3043 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-3043 is a high-severity denial of service vulnerability in silabs.com Ember ZNet SDK, published on 27 Jun 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-3043 in the wild and no public exploit code.

Affected product: silabs.com Ember ZNet 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-3043/ (Markdown: https://insights.sbomify.com/CVE-2024-3043/index.md)
```

## Sources

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

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