vciy

CVE-2024-13176

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

Timing side-channel in ECDSA signature computation

CVE-2024-131763 of 4 sources documented this
15

rank 15 = 15 + 0 + 0 + 0 + 0

rank@v1 · backlog

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.00613  ·  without this subject the record ranks 0

What it costs you if it fires

NVD CVSS base score, then the CNA's own

no CVSS held by anyone  ·  without this subject the record ranks 15

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 15

How much of the world it touches

NVD CPE configurations

0 products in the CPE ranges  ·  without this subject the record ranks 15

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 15

Hindsight · the state

0.00613EPSSNOT IN KEVas of 2026-09-20
Severitynot scored
Harmnot stated
Exploitationpublic proof-of-conceptreceipt
Defensefix version namedreceipt
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2025-01-21, 575 days at 0.01, as of 2026-08-19. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Running OpenSSL? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

ReachNo CVSS vector in held sources, so no reach or impact can be stated.
Weakness classCWE-385 Covert Timing Channelreceipt
Published consequencesCWE-385: Confidentiality, Other: Read Application Data, Other[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed in3.4.1; 3.3.3; 3.2.4; 3.1.8; 3.0.16; 1.1.1zb; 1.0.2zlreceipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Proof-of-concept published · 1 public repository, 2026-08-19.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published · 1 public repository2026-08-19receipt
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

Exploit probability0.00613 · top 52% of all CVEsreceipt
Assigned byopensslreceipt
Recorded changes46 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productOpenSSLreceipt
Fixed in3.4.1; 3.3.3; 3.2.4; 3.1.8; 3.0.16; 1.1.1zb; 1.0.2zlreceipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

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

Read the rest of the CNA's description

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.

NVD's analysis a second authority

weakness
CWE-385
also scored by
4.1 CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

check it yourself openssl-library.org github.com github.com github.com github.com github.com +2 morereceipt

Movement the material steps

21 Jan 20250.00044
17 Mar 20250.00087 · scoring model v2025.03.14
15 Jun 20260.00598 · scoring model v2026.06.15
15 Aug 20260.00613

This score more than doubled inside 72 hours. Both observations are in the full history below.

Show all 43 observations
21 Jan 20250.00044
17 Mar 20250.00087
19 Mar 20250.00064
29 Mar 20250.00113
30 Mar 20250.00075
15 Apr 20250.00033
15 May 20250.00024
22 May 20250.0003
27 May 20250.00029
15 Jun 20250.00037
18 Jun 20250.0003
19 Jun 20250.00045
27 Jun 20250.00036
29 Jun 20250.00045
30 Jun 20250.00069
16 Jul 20250.00058
18 Jul 20250.00071
26 Aug 20250.0008
12 Sep 20250.00065
15 Sep 20250.0008
18 Sep 20250.00065
20 Sep 20250.0008
25 Sep 20250.00089
16 Oct 20250.00118
4 Nov 20250.00114
6 Nov 20250.00115
16 Nov 20250.00123
18 Nov 20250.00546
21 Nov 20250.001
24 Nov 20250.00123
27 Nov 20250.001
29 Nov 20250.00123
7 Jan 20260.001
9 Jan 20260.00123
28 Feb 20260.00073
21 Mar 20260.00075
1 Apr 20260.00073
22 May 20260.00075
10 Jun 20260.00073
11 Jun 20260.001
15 Jun 20260.00598
18 Jun 20260.00601
15 Aug 20260.00613

43 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.00613Published2025-01-20Public PoC2026-08-19Index as of2026-08-19

Exploit probability more than doubled between 2025-11-16 and 2025-11-18 (0.00123 → 0.00546) and the record had been public for 1 year, 6 months when this index was last written.

Published 2025-01-20 receipt · Public PoC 2026-08-19 receipt · Index as of 2026-08-19 derived

Siblings and hubs

Records related to this one

Its defect family

openssl

Of the 2 records in this family, this is the only one holding a stated fix version: 3.4.1; 3.3.3; 3.2.4; 3.1.8; 3.0.16; 1.1.1zb; 1.0.2zl.

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Family membership: held values

This record is one of a group, and the group's page describes all of them. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.

Browse the index from here

These are index-wide views, not findings about CVE-2024-13176.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.