# CVE-2024-22473: Uninitialized TRNG used for ECDSA after EM2/EM3 sleep for VSE devices

> Attackers can spoof signatures by recreating keys due to uninitialized TRNG usage in ECDSA signing on Silicon Labs VSE devices.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Feb 2024
- **Updated:** 27 Sep 2024
- **Also known as:** GHSA-xhg6-78jc-3cwf

## What is CVE-2024-22473?

CVE-2024-22473 is a medium-severity vulnerability in silabs.com GSDK, published on 21 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-331 (Insufficient Entropy), CWE-1279 (Cryptographic Operations are Run Before Supporting Units are Ready)

## Which versions are affected by CVE-2024-22473?

It affects 1 product.


Products: Silabs Gecko Software Development Kit.

## How do I fix CVE-2024-22473?

No fix has been published for CVE-2024-22473 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-22473 being exploited?

There is no known exploitation of CVE-2024-22473 in the wild and no public exploit code.

## Other vulnerabilities in silabs.com GSDK

- [CVE-2023-45318](https://insights.sbomify.com/CVE-2023-45318/): Memory corruption in Gecko Platform (critical 10.0)
- [CVE-2023-2686](https://insights.sbomify.com/CVE-2023-2686/): Memory corruption in Gecko Platform (critical 9.8)
- [CVE-2023-4280](https://insights.sbomify.com/CVE-2023-4280/): Unvalidated input in Silicon Labs TrustZone implementation leads to accessing Trusted memory region (critical 9.3)
- [CVE-2023-4020](https://insights.sbomify.com/CVE-2023-4020/): Unvalidated input in Silicon Labs PSA Attestation service leads to secure memory access from non-secure memory (critical 9.0)
- [CVE-2023-25181](https://insights.sbomify.com/CVE-2023-25181/): Memory corruption in Cesium NET (critical 9.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-22473 and fix it if it is affected.

What it is: CVE-2024-22473 is a medium-severity vulnerability in silabs.com GSDK, published on 21 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-22473 in the wild and no public exploit code.

Affected product: silabs.com GSDK. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-22473/ (Markdown: https://insights.sbomify.com/CVE-2024-22473/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-22473
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-22473
- OSV: https://osv.dev/vulnerability/CVE-2024-22473

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-22473/
Summaries are generated and may contain mistakes; the official description above is the record.