# Minerva timing attack on P-256 in python-ecdsa

Advisory record · `GHSA-wj6h-64fc-37mp`

- **Identifiers:** `GHSA-wj6h-64fc-37mp` · `CVE-2024-23342` · `PYSEC-2026-1325`
- **State:** Confirmed
- **Severity:** CVSS 7.4 High
- **Critical:** No
- **Weakness (CWE):** [CWE-203](https://cwe.mitre.org/data/definitions/203.html) · [CWE-208](https://cwe.mitre.org/data/definitions/208.html) · [CWE-385](https://cwe.mitre.org/data/definitions/385.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [CWE-208](https://agentprime.io/advisories/tag/cwe-208.md) · [CWE-385](https://agentprime.io/advisories/tag/cwe-385.md)
- **Published:** 22 Jan 2024
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 22 Jan 2024, 21:35 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `ecdsa` (PyPI): affected `all versions`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The ecdsa package (python-ecdsa), in all versions, is affected by a Minerva timing attack on the P-256 curve. An attacker who can time signing operations made through SigningKey.sign_digest() may be able to recover the internal nonce and possibly the private key; ECDSA key generation and ECDH are also affected, while signature verification is not. No fixed version is listed, and the project considers side-channel attacks out of scope and has no planned fix.

Written 5 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.4 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0098, the 62nd percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:35 UTC: First seen by agentprime
- 31 Oct 2026, 14:35 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-wj6h-64fc-37mp)

## Sources

- [GitHub Advisory Database: GHSA-wj6h-64fc-37mp](https://github.com/advisories/GHSA-wj6h-64fc-37mp)
- [OSV: GHSA-wj6h-64fc-37mp](https://osv.dev/vulnerability/GHSA-wj6h-64fc-37mp)
- <https://github.com/tlsfuzzer/python-ecdsa/security/advisories/GHSA-wj6h-64fc-37mp>
- <https://nvd.nist.gov/vuln/detail/CVE-2024-23342>
- <https://github.com/tlsfuzzer/python-ecdsa>
- <https://github.com/tlsfuzzer/python-ecdsa/blob/master/SECURITY.md>
- <https://minerva.crocs.fi.muni.cz/>
- <https://securitypitfalls.wordpress.com/2018/08/03/constant-time-compare-in-python>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-wj6h-64fc-37mp>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-wj6h-64fc-37mp/>. Everything for agents: <https://agentprime.io/llms.txt>.