LiveActive security incident?Get immediate response
CVE Record

CVE-2023-51392: Silicon Labs EFR32xxx parts with classic key storage do not use hardware accelerated AES-CCM

Ember 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.

MediumCVSS 6.2Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE concerns Silicon Labs Ember ZNet firmware using software AES-CCM instead of hardware crypto on EFR32xxx devices with classic key storage. The main business risk is exposure of cryptographic secrets through physical side-channel analysis, not remote compromise.

Executive priority

Treat as a targeted embedded-device confidentiality risk. It is not currently supported as internet-scale exploitation, but products in hostile or physically accessible environments should be assessed promptly.

Technical view

Ember ZNet v7.2.0 to v7.4.0 reportedly used software AES-CCM rather than integrated hardware accelerators, increasing electromagnetic and differential power analysis risk. CVSS is 6.2 with local attack vector and high confidentiality impact. The bundle explicitly lists Ember ZNet SDK 7.2.0 as affected.

Likely exposure

Organizations with deployed EFR32xxx-based products using affected Ember ZNet SDK builds and classic key storage have plausible exposure, especially where attackers can physically access devices.

Exploitation context

No KEV listing or cited evidence of active exploitation is provided. Exploitation appears to require local physical access and side-channel capability, making it more relevant to device capture, lab analysis, and targeted attacks.

Researcher notes

Evidence is limited to the provided CVE data and Silicon Labs reference URL. The exact fixed version or vendor mitigation is not included in the bundle, so avoid assuming a patch path without advisory confirmation.

Mitigation direction

  • Check Silicon Labs guidance for fixed SDK versions or approved mitigations.
  • Inventory EFR32xxx products and firmware built with Ember ZNet 7.2.0 through 7.4.0.
  • Prioritize devices using classic key storage in physically exposed environments.
  • Ask suppliers or integrators for written affected-version and remediation status.
  • Limit physical access to exposed devices until vendor guidance is applied.

Validation and detection

  • Review firmware build manifests for Ember ZNet SDK version evidence.
  • Confirm whether products use EFR32xxx parts with classic key storage.
  • Compare deployed firmware against Silicon Labs advisory scope.
  • Request vendor attestation for AES-CCM implementation and SDK version.
  • Track remediation evidence in vulnerability management records.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-1240: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-51392 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.2CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N2.53.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.2Medium
CVSS 3.1 vector shape for CVE-2023-51392Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
silabs.comEmber ZNet SDKEmber ZNet SDK, 7.2.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-1240 · source CWE mapping

Use of a Cryptographic Primitive with a Risky Implementation

Use of a Cryptographic Primitive with a Risky Implementation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.