CVE-2024-13176
Timing side-channel in ECDSA signature computation
Issue summary: A timing side-channel which could potentially allow recovering the private key exists in the ECDSA signature computation. Impact summary: A timing side-channel in ECDSA signature computations could allow recovering the private key by an attacker. However, measuring the timing would require either local access to the signing application or a very fast network connection with low latency. There is a timing signal of around 300 nanoseconds when the top word of the inverted ECDSA nonce value is zero. This can happen with significant probability only for some of the supported elliptic curves. In particular the NIST P-521 curve is affected. To be able to measure this leak, the attacker process must either be located in the same physical computer or must have a very fast network connection with low latency. For that reason the severity of this vulnerability is Low. The FIPS modules in 3.4, 3.3, 3.2, 3.1 and 3.0 are affected by this issue.
Fixes and workarounds
Fix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: opensslFix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: opensslFix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: opensslFix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: opensslFix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: opensslFix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: opensslFix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: opensslAffected products and versions
| Product | Versions | Authority |
|---|---|---|
| OpenSSL OpenSSL |
≥ 3.4.0; < 3.4.1 (affected, semver) ≥ 3.3.0; < 3.3.3 (affected, semver) ≥ 3.2.0; < 3.2.4 (affected, semver) ≥ 3.1.0; < 3.1.8 (affected, semver) ≥ 3.0.0; < 3.0.16 (affected, semver) ≥ 1.1.1; < 1.1.1zb (affected, custom) ≥ 1.0.2; < 1.0.2zl (affected, custom) Other versions: unaffected |
CNA: openssl |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.1 / 4.6 medium |
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | ADP: CISA-ADP |
| 3.1 / 4.1 medium |
CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L | NVD: 134c704f-9b21-4f2e-91b3-4a467353bcc0 |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://openssl-library.org/news/secadv/20250120.txtCNA: openssl · vendor-advisory
- https://github.com/openssl/openssl/commit/77c608f4c8857e63e98e66444e2e761c9627916fCNA: openssl · patch
- https://github.com/openssl/openssl/commit/392dcb336405a0c94486aa6655057f59fd3a0902CNA: openssl · patch
- https://github.com/openssl/openssl/commit/4b1cb94a734a7d4ec363ac0a215a25c181e11f65CNA: openssl · patch
- https://github.com/openssl/openssl/commit/2af62e74fb59bc469506bc37eb2990ea408d9467CNA: openssl · patch
- https://github.com/openssl/openssl/commit/07272b05b04836a762b4baa874958af51d513844CNA: openssl · patch
- https://github.openssl.org/openssl/extended-releases/commit/a2639000db19878d5d89586ae7b725080592ae86CNA: openssl · patch
- https://github.openssl.org/openssl/extended-releases/commit/0d5fd1ab987f7571e2c955d8d8b638fc0fb54dedCNA: openssl · patch
- http://www.openwall.com/lists/oss-security/2025/01/20/2ADP: CVE
- https://security.netapp.com/advisory/ntap-20250124-0005/ADP: CVE
- https://security.netapp.com/advisory/ntap-20250418-0010/ADP: CVE
- https://lists.debian.org/debian-lts-announce/2025/05/msg00028.htmlADP: CVE
- https://security.netapp.com/advisory/ntap-20250502-0006/ADP: CVE
- https://github.com/openssl/openssl/commit/07272b05b04836a762b4baa874958af51d513844[email protected]
- https://github.com/openssl/openssl/commit/2af62e74fb59bc469506bc37eb2990ea408d9467[email protected]
- https://github.com/openssl/openssl/commit/392dcb336405a0c94486aa6655057f59fd3a0902[email protected]
- https://github.com/openssl/openssl/commit/4b1cb94a734a7d4ec363ac0a215a25c181e11f65[email protected]
- https://github.com/openssl/openssl/commit/77c608f4c8857e63e98e66444e2e761c9627916f[email protected]
- https://github.openssl.org/openssl/extended-releases/commit/0d5fd1ab987f7571e2c955d8d8b638fc0fb54ded[email protected]
- https://github.openssl.org/openssl/extended-releases/commit/a2639000db19878d5d89586ae7b725080592ae86[email protected]
- https://openssl-library.org/news/secadv/20250120.txt[email protected]
- http://www.openwall.com/lists/oss-security/2025/01/20/2af854a3a-2127-422b-91ae-364da2661108
- https://lists.debian.org/debian-lts-announce/2025/05/msg00028.htmlaf854a3a-2127-422b-91ae-364da2661108
- https://security.netapp.com/advisory/ntap-20250124-0005/af854a3a-2127-422b-91ae-364da2661108
- https://security.netapp.com/advisory/ntap-20250418-0010/af854a3a-2127-422b-91ae-364da2661108
- https://security.netapp.com/advisory/ntap-20250502-0006/af854a3a-2127-422b-91ae-364da2661108
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.