CVE-2022-24939
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 · uneditedA malformed packet containing an invalid destination address, causes a stack overflow in the Ember ZNet stack. This causes an assert which leads to a reset, immediately clearing the error.
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 malformed network packet with an invalid destination address triggers a stack overflow in the Ember ZNet stack. The overflow causes an assertion failure that results in an immediate system reset, clearing the error condition.
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 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 if the device uses Silabs Ember ZNet stackCheck product documentation, firmware build files, or SDK documentation for 'Ember ZNet', 'Emberznet', or 'Silabs Zigbee' references. Inspect boot logs or firmware strings for 'Ember' or 'Silabs' Zigbee components.Affected if The product explicitly uses Silabs Ember ZNet or Zigbee stack from Silabs Gecko SDK
-
Verify the SDK or stack is from SilabsExamine the firmware binary, build system, or software bill of materials (SBOM) for Silabs Gecko SDK components or libznet.a/zigbee libraries. Check development toolchain for Silabs Simplicity Studio or Gecko SDK paths.Affected if The firmware links against Silabs Gecko SDK libraries or contains Ember ZNet components
-
Look for unexplained system resetsMonitor device uptime and check for sudden resets. Review system logs, watchdog timers, or crash dumps for assertion failures occurring after receiving network traffic. Check for reset reason codes indicating assert/panic.Affected if The device exhibits unexplained resets, especially after receiving Zigbee network traffic, and reset reason shows assertion failure or panic
-
Inspect network traffic for malformed packetsCapture Zigbee network traffic using a sniffer or protocol analyzer before any reset events. Look for packets with invalid or malformed destination addresses that precede device resets.Affected if Malformed Zigbee packets with invalid destination addresses are received immediately before device resets
-
Check for vendor patch availabilityConsult Silabs security advisories or release notes for CVE-2022-24939. Contact Silabs support or check the security notice for your specific SDK version.Affected if A vendor patch exists and the current version has not been updated, indicating the unpatched vulnerability is present
A user is affected if their device uses the Silabs Ember ZNet or Zigbee stack from the Gecko SDK and exhibits unexplained resets following receipt of malformed Zigbee network packets with invalid destination addresses.
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 dataImplement proper input validation for packet destination addresses and replace assert-based error handling with graceful error recovery. Update to any available vendor patch for the Ember ZNet stack.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24939 — 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-24939 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