# CVE-2025-3301: DPA Countermeasures Unavailable for Certain Cryptographic Operations on Series 2 Devices

> Missing DPA countermeasures in Silicon Labs Series 2 SoCs allow attackers to potentially expose confidential keys via side-channel attacks.

- **Severity:** Low 1.0 (`CVSS:4.0/AV:P/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Apr 2025
- **Updated:** 29 Apr 2025
- **Also known as:** GHSA-h3wr-2jpv-p235

## What is CVE-2025-3301?

CVE-2025-3301 is a low-severity vulnerability in silabs.com Series 2 SoCs and associated modules, published on 29 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

DPA countermeasures are unavailable for ECDH key agreement and EdDSA signing operations on Curve25519 and Curve448 on all Series 2 modules and SoCs due to a lack of hardware and software support. A successful DPA attack may result in exposure of confidential information. The best practice is to use the impacted crypto curves and operations with ephemeral keys to reduce the number of DPA traces that can be collected.

Weakness: CWE-1255 (Comparison Logic is Vulnerable to Power Side-Channel Attacks)

## Which versions are affected by CVE-2025-3301?


## How do I fix CVE-2025-3301?

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

## Is CVE-2025-3301 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3301 and fix it if it is affected.

What it is: CVE-2025-3301 is a low-severity vulnerability in silabs.com Series 2 SoCs and associated modules, published on 29 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-3301 in the wild and no public exploit code.

Affected product: silabs.com Series 2 SoCs and associated modules. 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-2025-3301/ (Markdown: https://insights.sbomify.com/CVE-2025-3301/index.md)
```

## Sources

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

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