CVE-2024-6350
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 802.15.4 packet causes a buffer overflow to occur leading to an assert and a denial of service. A watchdog reset clears the error condition automatically.
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 · high confidenceA buffer overflow vulnerability exists in the 802.15.4 (Zigbee) packet parsing implementation. When the device receives a malformed 802.15.4 packet, the insufficient bounds checking causes memory corruption that triggers an assert() call, resulting in a denial of service condition. The affected system automatically recovers via a watchdog reset mechanism.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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.
-
Confirm 802.15.4/Zigbee functionality is in useIdentify if the device or software implements 802.15.4/Zigbee stack. Check product documentation, running processes, or loaded kernel modules for Zigbee-related components (e.g., zigbee-host, zboss, zigate).Affected if The system actively processes or forwards 802.15.4 packets via a Zigbee radio or stack.
-
Determine firmware or software versionRetrieve the installed firmware version or software package version using vendor-specific commands (e.g., cat /proc/version, firmware version in boot logs, or software package manager). Compare against any known fixed versions provided by the vendor.Affected if The installed version falls within the vulnerable range or is unspecified and predates available patches.
-
Verify packet parsing is exposed to untrusted 802.15.4 trafficDetermine if the device receives 802.15.4 packets from untrusted sources. Check network configuration, radio state (e.g., is the Zigbee radio in listen/接收 mode), and whether the device acts as a coordinator, router, or end device that processes incoming packets.Affected if The device accepts incoming 802.15.4 frames without prior network-level filtering or authentication.
-
Inspect for watchdog reset events or assert failuresReview system logs, kernel messages, or hardware watchdog logs for patterns of unexpected resets, assert() call crashes, or repeated restart cycles that correlate with 802.15.4 traffic. Use dmesg, journalctl, or vendor log interfaces.Affected if Logs show unexplained watchdog resets or assert failures occurring when Zigbee traffic is present.
A user is affected if the system uses an unpatched 802.15.4/Zigbee implementation that processes incoming packets from potentially untrusted sources, especially if watchdog resets or assert failures are observed in logs.
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-provided firmware patches that implement proper input validation and bounds checking on incoming 802.15.4 packets. Consider deploying network-level filtering to reject malformed packets before they reach vulnerable devices.
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6350 — 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-2024-6350 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