dbcve.org
Emberznet SdkApplication · Silabs

CVE-2023-41096

MEDIUM · 6.1 CVSS v3.1 Published 2023-10-26
Fix available
A fix is available. Upgrade to after 7.3.1.0 or later.
See remediation →
66/100
Remediation priority · Elevated
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
Missing Encryption of Security Keys vulnerability in Silicon Labs Ember ZNet SDK on 32 bit, ARM (SecureVault High modules) allows potential modification or extraction of network credentials stored in flash. This issue affects Silicon Labs Ember ZNet SDK: 7.3.1 and earlier.

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 confidence

The Ember ZNet SDK does not encrypt network credentials (security keys) stored in flash memory on 32-bit ARM SecureVault High modules. This allows attackers with physical access to potentially read or modify sensitive network credentials directly from the flash storage.

MitigationImplement encryption for security keys stored in flash memory; upgrade to a patched version of the Ember ZNet SDK (7.3.2 or later) if available, or implement application-level encryption of stored network credentials.

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
Emberznet SdkApplication
Affected:<= 7.3.1.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
Physical
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

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 the Ember ZNet SDK version
    Check the SDK version in your project build configuration, manifest file, or SDK installation directory. Look for a version file or check the EmberZNet SDK package metadata.
    Affected if The installed SDK version is 7.3.1.0 or earlier.
  2. Confirm target hardware is a 32-bit ARM SecureVault High module
    Verify the target device/board configuration specifies a 32-bit ARM processor with SecureVault High security. Check the hardware definition files or board configuration in your project.
    Affected if The target hardware is a 32-bit ARM SecureVault High module.
  3. Check if network credentials are stored in flash memory
    Inspect the application storage configuration or security key storage implementation to determine if network credentials (network keys, encryption keys, certificates) are persisted to flash storage.
    Affected if Network credentials are stored in flash memory on the device.
  4. Determine if flash-stored credentials have encryption enabled
    Review the security configuration or storage implementation to verify whether encryption is applied to the credential data before writing to flash. Check for any encryption module or cipher usage in the credential storage code.
    Affected if No encryption is applied to network credentials before flash storage, or encryption is explicitly disabled in the configuration.

You are affected if your Ember ZNet SDK version is 7.3.1.0 or earlier, you are using a 32-bit ARM SecureVault High module, and network credentials are stored in unencrypted flash memory.

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 a release after 7.3.1.0
Interim mitigation

Implement encryption for security keys stored in flash memory; upgrade to a patched version of the Ember ZNet SDK (7.3.2 or later) if available, or implement application-level encryption of stored network credentials.

Recommended fix Moderate confidence

Ember ZNet SDK version > 7.3.1.0 (contact Silicon Labs for the specific latest stable release)

  1. Identify the current Silicon Labs Ember ZNet SDK version in use by checking the SDK version in your project configuration or build system
  2. Download the latest stable Ember ZNet SDK version from Silicon Labs (typically available through Silicon Labs Simplicity Studio or their official developer portal)
  3. Update the SDK reference in your project to point to the newer SDK version
  4. Rebuild the firmware image with the updated SDK
  5. Verify that the new SDK version properly encrypts security keys stored in flash on your target SecureVault High module
  6. Test network credential storage and retrieval to confirm the encryption is functioning correctly
  7. Ensure any custom security implementations are compatible with the new SDK version
Caveat Review release notes for any API changes between your current version and the new version that may require code modifications

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

Fix this in Emberznet Sdk Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-41096 — 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-41096 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