CVE-2022-24938
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 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 stack overflow vulnerability exists in the Ember ZNet Zigbee stack where specially crafted malformed packets trigger overflow of a stack buffer. This causes an assertion failure that results in an immediate device reset, effectively creating a denial-of-service condition while clearing error state.
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 data= 1.0.0CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/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 Zigbee stack vendorExamine the device firmware documentation, firmware image metadata, or boot logs to determine which Zigbee stack implementation the device uses. Look for 'Ember', 'EmberZNet', or 'Silicon Labs' references in firmware strings or chipset identification.Affected if The device does not use Ember ZNet stack - if using a different vendor's Zigbee stack, this CVE does not apply.
-
Determine Emberznet firmware versionQuery the device's firmware version through its management interface (e.g., via Zigbee ZCL attributes, serial debug console, or API endpoint). For Ember-based devices, version information is often exposed through the EmberZNet NCP (Network Co-Processor) version command or displayed in bootup serial output.Affected if Version is 1.0.0 exactly - this is the only affected version per the CVE.
-
Check if Zigbee network functionality is activeVerify that the EmberZNet stack is actually running and processing network traffic. Check device status for active Zigbee network join/permit-join functionality or monitor for incoming Zigbee packets on the network.Affected if Zigbee stack is disabled or device is not functioning as a Zigbee network node - the vulnerability requires the stack to process packets.
-
Confirm device accepts external Zigbee packetsDetermine if the device has permit-join enabled or accepts Zigbee packets from untrusted sources. Check network configuration for open join permissions or review access control settings for Zigbee traffic processing.Affected if Device only processes pre-authenticated, closed-group traffic - the malformed packet must reach the device's Zigbee stack to trigger the overflow.
-
Review crash logs for reset patternsExamine persistent device logs, serial console output, or network management logs for evidence of unexpected resets, assertion failures, or stack overflow messages occurring during Zigbee packet processing.Affected if Recurring unexplained device resets correlate with Zigbee traffic - this would indicate the vulnerability is being triggered.
A defender is affected only if their device runs Ember ZNet stack version 1.0.0, has Zigbee networking enabled, and processes incoming Zigbee packets from potential attackers.
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 dataApply vendor-supplied firmware patches for Ember ZNet stack; implement stricter packet length validation and bounds checking before stack operations; consider adding persistent logging before reset to capture crash context.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24938 — 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-24938 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