CVE-2023-6874
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 · uneditedPrior to v7.4.0, Ember ZNet is vulnerable to a denial of service attack through manipulation of the NWK sequence number
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 confidenceEmber ZNet (a Zigbee protocol stack) prior to version 7.4.0 is vulnerable to denial of service via manipulation of the NWK (Network) sequence number, allowing attackers to disrupt Zigbee network communications.
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< 4.4.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 Ember ZNet version in useCheck the firmware/build manifest, release notes, or binary metadata for the Ember ZNet protocol stack version. This is typically found in the project configuration files (e.g., .slcp, .hwconf) or in the built firmware image header.Affected if Ember ZNet version is detected and is prior to 7.4.0
-
Identify Silabs Gecko SDK versionLocate the installed Silicon Labs Gecko Software Development Kit directory and check the SDK version. This is usually visible in the SDK installation path (e.g., C:\SiliconLabs\SimplicityStudio\v5\platforms\radioconfig\rfsim\gecko_sdk) or in the SDK release notes.Affected if Gecko SDK version is detected and is prior to 4.4.0
-
Confirm Zigbee network functionality is activeVerify that the device or application is configured to use Zigbee networking with the NWK (Network) layer enabled. Check the project configuration for zigbee stack initialization and network formation/joining settings.Affected if Zigbee/NWK stack is enabled and the device participates in Zigbee network communications
The environment is affected if Ember ZNet version is below 7.4.0 (or Silabs Gecko SDK is below 4.4.0) and Zigbee network functionality is in use, as this allows NWK sequence number manipulation for denial of service.
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.
dbcve · scoped4.4.0
Upgrade Ember ZNet to version 7.4.0 or later to remediate the vulnerability.
Ember ZNet v7.4.0 (or later)
- Upgrade Ember ZNet to version 7.4.0 or later to remediate the NWK sequence number manipulation vulnerability
- If using Gecko Software Development Kit, verify that the SDK version includes the fixed Ember ZNet components
- After upgrade, verify that the NWK sequence number handling is functioning correctly
- Test for any regressions in network join and rejoin functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-6874 — 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-2023-6874 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