dbcve.org
EmberznetApplication · Silabs

CVE-2023-51393

HIGH · 7.5 CVSS v3.1 Published 2024-02-23
Fix available
A fix is available. Upgrade to 7.4.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Due to an allocation of resources without limits, an uncontrolled resource consumption vulnerability exists in Silicon Labs Ember ZNet SDK prior to v7.4.0.0 (delivered as part of Silicon Labs Gecko SDK v4.4.0) which may enable attackers to trigger a bus fault and crash of the device, requiring a reboot in order to rejoin the network.

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 confidence

An uncontrolled resource consumption vulnerability in Silicon Labs Ember ZNet SDK prior to v7.4.0.0 allows attackers to trigger a bus fault and crash the device by exploiting unbounded resource allocation. The flaw enables denial of service, requiring a device reboot to rejoin the network.

MitigationUpgrade Silicon Labs Ember ZNet SDK to v7.4.0.0 (or Gecko SDK v4.4.0) or later to patch the resource exhaustion vulnerability. If immediate patching is not feasible, implement network-level rate limiting or access controls to reduce attack surface.

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
EmberznetApplication
Affected:< 7.4.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if the device uses Silicon Labs Ember ZNet stack
    Examine the firmware, product documentation, or software bill of materials (SBOM) for references to 'Ember ZNet', 'EmberZNet', or Silicon Labs wireless stack components
    Affected if The product implements Silicon Labs Ember ZNet protocol stack for Zigbee or Thread connectivity
  2. Determine the Ember ZNet SDK version
    Check the firmware metadata, SDK manifest file, build logs, or firmware version string for the Silicon Labs Ember ZNet component version number
    Affected if The installed Ember ZNet version is below 7.4.0.0 (any pre-v7.4.0 release)
  3. Verify network connectivity is enabled
    Inspect the device network configuration or runtime settings to confirm the device has active Zigbee/Thread network interface capabilities
    Affected if The device has an active network interface and can receive unsolicited inbound packets
  4. Check for crash or resource exhaustion indicators
    Review device logs, watchdog reset records, or fault logs for unexplained bus faults, memory allocation failures, or unexpected reboots
    Affected if The device exhibits symptoms of resource exhaustion crashes without other identified causes

If the device runs Silicon Labs Ember ZNet SDK version prior to 7.4.0 and has active network connectivity, it is vulnerable to CVE-2023-51393 resource exhaustion attacks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 7.4.0 or later
Fixed in 7.4.0
Interim mitigation

Upgrade Silicon Labs Ember ZNet SDK to v7.4.0.0 (or Gecko SDK v4.4.0) or later to patch the resource exhaustion vulnerability. If immediate patching is not feasible, implement network-level rate limiting or access controls to reduce attack surface.

Recommended fix High confidence

Ember ZNet SDK v7.4.0.0 (Gecko SDK v4.4.0)

  1. Obtain Ember ZNet SDK v7.4.0.0 (or later) from Silicon Labs, delivered as part of Gecko SDK v4.4.0
  2. Follow Silicon Labs standard procedures for upgrading the Ember ZNet SDK in your development environment
  3. Rebuild your application firmware with the updated SDK
  4. Test the firmware in a non-production environment to verify normal operation
  5. Deploy the updated firmware to production devices

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Emberznet Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-51393 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-51393 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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