CVE-2023-51392
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 · uneditedEmber ZNet between v7.2.0 and v7.4.0 used software AES-CCM instead of integrated hardware cryptographic accelerators, potentially increasing risk of electromagnetic and differential power analysis sidechannel attacks.
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 confidenceEmber ZNet stack versions 7.2.0 through 7.4.0 implemented AES-CCM encryption in software rather than utilizing available hardware cryptographic accelerators, making the implementation vulnerable to electromagnetic analysis (EMA) and differential power analysis (DPA) side-channel attacks that can recover cryptographic keys.
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>= 7.2.0, <= 7.2.4CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 stack versionQuery the device firmware, SDK manifest, or stack configuration for the Ember ZNet version number. This is typically found in build files, firmware metadata, or by querying the stack at runtime using vendor-provided diagnostics.Affected if The reported version is between 7.2.0 and 7.2.4 inclusive.
-
Confirm AES-CCM encryption is in useInspect the security configuration or network settings to verify that AES-CCM mode is enabled for the Zigbee network. This is typically set in the stack configuration or security plugin settings.Affected if AES-CCM encryption is actively configured or used for network communications.
-
Check cryptographic implementation modeReview the build configuration or firmware image to determine whether AES-CCM operations are handled by software crypto libraries or offloaded to a hardware cryptographic accelerator. This may require examining compiler defines, SDK configuration options, or firmware disassembly.Affected if The firmware uses a software-based AES-CCM implementation and does not utilize available hardware crypto acceleration for these operations.
A system is affected if it runs Ember ZNet version 7.2.0 through 7.2.4, has AES-CCM encryption enabled, and relies on software-based crypto rather than hardware acceleration for AES-CCM operations.
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 · scopedUpgrade Ember ZNet to a version beyond v7.4.0 that uses hardware cryptographic accelerators for AES-CCM operations, or implement additional side-channel countermeasures if hardware acceleration is unavailable.
v7.4.0 or later (any version that enables hardware cryptographic accelerators)
- 1. Identify all Ember ZNet deployments running versions 7.2.0 through 7.2.4
- 2. Review the Silicon Labs community.silabs.com reference for migration guidance to v7.4.0 or later
- 3. Schedule a maintenance window for the upgrade
- 4. Upgrade Ember ZNet to version 7.4.0 or later which includes hardware cryptographic accelerator support
- 5. Verify the hardware crypto is properly initialized and functioning post-upgrade
- 6. Confirm AES-CCM operations now utilize the integrated hardware cryptographic accelerators rather than software implementation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-51392 — 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-51392 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