CVE-2024-13176

Timing side-channel in ECDSA signature computation

MEDIUM
4.1
CVSS Score
Published: January 20, 2025 at 01:29 PM UTC
Updated: June 17, 2026 at 07:01 AM UTC
1 product affected across 1 vendorOpenSSL

Using OpenSSL by OpenSSL?

Get instant alerts when new vulnerabilities affect OpenSSL - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM4.1
Exploit prediction
EPSS 0.6%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

1.0.2 ≤ v < 1.0.2zl1.1.1 ≤ v < 1.1.1zb3.0.0 ≤ v < 3.0.163.1.0 ≤ v < 3.1.83.2.0 ≤ v < 3.2.43.3.0 ≤ v < 3.3.33.4.0 ≤ v < 3.4.11.0.21.1.13.0.03.1.03.2.03.3.03.4.0
Affected range stops below 1.0.2zl, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.1.1zb, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.0.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.1.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.2.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.3.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.4.1, so it looks safe — our inference, not a vendor statement

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

4.1MEDIUMCISA-ADP
Attack Vector
PHYSICAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
LOW
Integrity
LOW
Availability
LOW
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-385

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card