CVE-2023-41095
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 · uneditedMissing Encryption of Security Keys vulnerability in Silicon Labs OpenThread SDK on 32 bit, ARM (SecureVault High modules) allows potential modification or extraction of network credentials stored in flash. This issue affects Silicon Labs OpenThread SDK: 2.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 · high confidenceMissing encryption vulnerability in Silicon Labs OpenThread SDK allows extraction or modification of network credentials stored in plaintext flash memory on 32-bit ARM SecureVault High modules. Attackers with physical access or code execution can read/modify unencrypted security keys, compromising the entire Thread network.
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<= 2.3.1.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
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the OpenThread SDK version in useCheck the SDK version manifest, release notes, or build artifacts in your deployment. This may be found in a version file, git tags, or the SDK directory name used in your build system.Affected if The SDK version is 2.3.1.0 or any earlier version within the <= 2.3.1.0 range
-
Confirm hardware uses 32-bit ARM SecureVault HighReview your device specifications, hardware BOM, or module documentation to identify the processor architecture and security subsystem. Look for 'SecureVault High' and '32-bit ARM' designations.Affected if The device implements a 32-bit ARM processor with SecureVault High security subsystem and stores credentials locally
-
Inspect flash storage for credential encryptionExamine the flash memory layout or configuration files that define where network credentials (network keys, passphrases, certificates) are stored. Check if an encryption wrapper or secure storage API is used for these sensitive values.Affected if Network credentials are stored in flash without encryption applied, appearing as plaintext or in raw binary form
-
Verify storage encryption is disabled or not configuredReview the security configuration settings, bootloader settings, or MFG tokens in your build. Check if 'storage encryption', 'secure storage', or 'encrypted flash' options are present and enabled.Affected if Storage encryption for network credentials is not enabled, not configured, or is explicitly disabled in the security settings
A system is affected if it uses OpenThread SDK version 2.3.1.0 or earlier, runs on 32-bit ARM SecureVault High hardware, and stores Thread network credentials in plaintext flash without encryption enabled.
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.
From vendor dataUpgrade to a patched OpenThread SDK version beyond 2.3.1 and verify that storage encryption is properly enabled for all network credentials in flash.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41095 — 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-41095 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