CVE-2024-22473
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 · uneditedTRNG is used before initialization by ECDSA signing driver when exiting EM2/EM3 on Virtual Secure Vault (VSE) devices. This defect may allow Signature Spoofing by Key Recreation.This issue affects Gecko SDK through v4.4.0.
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 confidenceOn Virtual Secure Vault (VSE) devices, the ECDSA signing driver uses the True Random Number Generator (TRNG) before it has been properly initialized when waking from low-power modes EM2 or EM3. This causes non-random values to be used in ECDSA key generation, potentially allowing attackers to recreate signing keys and forge signatures.
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<= 4.4.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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 installed Gecko SDK versionCheck the SDK version installed in your development environment by examining the SDK release notes, version file, or project properties that reference the Gecko SDK. This is typically found in Simplicity Studio project settings or the SDK installation directory.Affected if The installed Gecko SDK version is 4.4.0 or earlier.
-
Verify ECDSA signing driver is in useReview your project source code and build configuration to determine if the ECDSA signing driver or any digital signature functionality from the Gecko SDK security library is being used for key generation or signing operations.Affected if Your application code or project dependencies include ECDSA key generation or signature operations using the Gecko SDK security modules.
-
Check for EM2/EM3 low-power mode configurationInspect your device initialization code, power management configuration, or board support package settings to determine if the device is configured to enter EM2 or EM3 low-power modes during operation.Affected if The device firmware or project configuration enables EM2 or EM3 low-power states.
-
Inspect ECDSA key generation timing relative to low-power wakeupExamine the code flow for ECDSA key generation operations to determine if key generation can occur immediately after the device wakes from EM2/EM3 sleep states without additional TRNG readiness verification.Affected if ECDSA keys are generated after waking from sleep without checking if TRNG initialization has completed.
You are affected if your Gecko SDK version is 4.4.0 or earlier AND your device uses ECDSA key generation in conjunction with EM2/EM3 low-power modes without verifying TRNG readiness.
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 dataUpdate Gecko SDK to a version beyond v4.4.0 that ensures TRNG initialization is completed before the ECDSA signing driver uses it after exiting EM2/EM3, or implement a software check to verify TRNG readiness before any cryptographic operation.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-22473 — 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-2024-22473 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