Skip to content
Noroxi
NVD / CVE Program· CNA openssl

CVE-2024-13176: Timing side-channel in ECDSA signature computation

Noroxi assessment

Priority: Monitor (action score 18/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.64% (FIRST EPSS); higher than 51.1% of all records.
  • Physical access to the device is required. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: OpenSSL OpenSSL 3.0.16, 3.1.8, 3.2.4; azl3 edk2 20240524git3e722403cd16-6 on Azure Linux 3.0 20240524git3e722403cd16-6; azl3 edk2 20240524git3e722403cd16-8 on Azure Linux 3.0 20240524git3e722403cd16-6.

Low priority for now. Upgrade to OpenSSL OpenSSL 3.0.16, 3.1.8, 3.2.4; azl3 edk2 20240524git3e722403cd16-6 on Azure Linux 3.0 20240524git3e722403cd16-6; azl3 edk2 20240524git3e722403cd16-8 on Azure Linux 3.0 20240524git3e722403cd16-6 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 4.6 · v3.1—Proof of concept Fix available
Published
Jan 20, 2025
Updated
Nov 6, 2026
EPSS
0.6% · 51th percentile

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
18 / 40 · 4.6 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.6%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-13176

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Check your server's TLS configuration

The OpenSSL version can't be seen from outside; the free SSL checker tests your certificate, enabled TLS versions and weak ciphers. Confirm the version on your server with the package manager.

Run the SSL check

Versions reported by the vendor

Affected version ranges reported by the assigning authority (openssl). Independent of NVD's CPE analysis and usually ahead of it.

  • OpenSSL OpenSSL

    • 3.4.0 and later · before 3.4.1affected · semver
    • 3.3.0 and later · before 3.3.3affected · semver
    • 3.2.0 and later · before 3.2.4affected · semver
    • 3.1.0 and later · before 3.1.8affected · semver
    • 3.0.0 and later · before 3.0.16affected · semver
    • 1.1.1 and later · before 1.1.1zbaffected
    • 1.0.2 and later · before 1.0.2zlaffected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10mysql-selinuxbefore 1.0.14-1.el10_01.0.14-1.el10_0
AlmaLinux:10mysql8.4-commonbefore 8.4.6-2.el10_08.4.6-2.el10_0
AlmaLinux:10mysql8.4-errmsgbefore 8.4.6-2.el10_08.4.6-2.el10_0
AlmaLinux:10mysql8.4-test-databefore 8.4.6-2.el10_08.4.6-2.el10_0
AlmaLinux:9mecabbefore 0.996-3.module_el9.6.0+152+8cbce00c.40.996-3.module_el9.6.0+152+8cbce00c.4
AlmaLinux:9mecab-develbefore 0.996-3.module_el9.6.0+152+8cbce00c.40.996-3.module_el9.6.0+152+8cbce00c.4
AlmaLinux:9mecab-ipadicbefore 2.7.0.20070801-24.module_el9.6.0+152+8cbce00c2.7.0.20070801-24.module_el9.6.0+152+8cbce00c
AlmaLinux:9mecab-ipadic-EUCJPbefore 2.7.0.20070801-24.module_el9.6.0+152+8cbce00c2.7.0.20070801-24.module_el9.6.0+152+8cbce00c
AlmaLinux:9mysqlbefore 8.4.6-1.module_el9.6.0+180+a4e757e58.4.6-1.module_el9.6.0+180+a4e757e5
AlmaLinux:9mysql-commonbefore 8.4.6-1.module_el9.6.0+180+a4e757e58.4.6-1.module_el9.6.0+180+a4e757e5
AlmaLinux:9mysql-develbefore 8.4.6-1.module_el9.6.0+180+a4e757e58.4.6-1.module_el9.6.0+180+a4e757e5
AlmaLinux:9mysql-errmsgbefore 8.4.6-1.module_el9.6.0+180+a4e757e58.4.6-1.module_el9.6.0+180+a4e757e5
AlmaLinux:9mysql-libsbefore 8.4.6-1.module_el9.6.0+180+a4e757e58.4.6-1.module_el9.6.0+180+a4e757e5
AlmaLinux:9mysql-serverbefore 8.4.6-1.module_el9.6.0+180+a4e757e58.4.6-1.module_el9.6.0+180+a4e757e5
AlmaLinux:9mysql-testbefore 8.4.6-1.module_el9.6.0+180+a4e757e58.4.6-1.module_el9.6.0+180+a4e757e5
AlmaLinux:9mysql-test-databefore 8.4.6-1.module_el9.6.0+180+a4e757e58.4.6-1.module_el9.6.0+180+a4e757e5
AlmaLinux:9rapidjson-develbefore 1.1.0-19.module_el9.6.0+152+8cbce00c1.1.0-19.module_el9.6.0+152+8cbce00c
AlmaLinux:9rapidjson-docbefore 1.1.0-19.module_el9.6.0+152+8cbce00c1.1.0-19.module_el9.6.0+152+8cbce00c
Alpine:v3.17opensslbefore 3.0.19-r03.0.19-r0
Alpine:v3.18opensslbefore 3.1.8-r03.1.8-r0
Alpine:v3.20opensslbefore 3.3.2-r23.3.2-r2
Alpine:v3.21opensslbefore 3.3.2-r53.3.2-r5
Debian:11opensslbefore 1.1.1w-0+deb11u31.1.1w-0+deb11u3
Debian:12edk2from 0—

+24

Other highest-scoring records for the same primary product.

  • CVE-2014-0160The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows remKEV
    90Now
  • CVE-2021-3711SM2 Decryption Buffer Overflow
    65This week
  • CVE-2003-0545Double free vulnerability in OpenSSL 0.9.7 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code
    65This week

Published before and after this one in the same product

  • ← EarlierCVE-2024-9143Oct 16, 2024 · Low-level invalid GF(2^m) parameters lead to OOB memory access
    38Monitor
  • ← EarlierCVE-2024-4741Nov 13, 2024 · Use After Free with SSL_free_buffers
    40Plan
  • Later →CVE-2024-12797Feb 11, 2025 · RFC7250 handshakes with unauthenticated servers don't abort as expected
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
OpenSSL OpenSSL3.0.16Vendor (CNA)
OpenSSL OpenSSL3.1.8Vendor (CNA)
OpenSSL OpenSSL3.2.4Vendor (CNA)
OpenSSL OpenSSL3.3.3Vendor (CNA)
OpenSSL OpenSSL3.4.1Vendor (CNA)
azl3 edk2 20240524git3e722403cd16-6 on Azure Linux 3.020240524git3e722403cd16-6 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 edk2 20240524git3e722403cd16-8 on Azure Linux 3.020240524git3e722403cd16-6 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 openssl 3.3.2-2 on Azure Linux 3.03.3.3-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 openssl 3.3.3-1 on Azure Linux 3.03.3.3-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 openssl 1.1.1k-36 on CBL Mariner 2.01.1.1k-36 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 openssl 1.1.1k-36 on CBL-Mariner 2.01.1.1k-36 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:mecab0.996-3.module_el9.6.0+152+8cbce00c.4 · AlmaLinux:9Package registry (OSV)
almalinux:mecab-devel0.996-3.module_el9.6.0+152+8cbce00c.4 · AlmaLinux:9Package registry (OSV)
almalinux:mecab-ipadic2.7.0.20070801-24.module_el9.6.0+152+8cbce00c · AlmaLinux:9Package registry (OSV)
almalinux:mecab-ipadic-EUCJP2.7.0.20070801-24.module_el9.6.0+152+8cbce00c · AlmaLinux:9Package registry (OSV)
almalinux:mysql8.4.6-1.module_el9.6.0+180+a4e757e5 · AlmaLinux:9Package registry (OSV)
almalinux:mysql-common8.4.6-1.module_el9.6.0+180+a4e757e5 · AlmaLinux:9Package registry (OSV)
almalinux:mysql-devel8.4.6-1.module_el9.6.0+180+a4e757e5 · AlmaLinux:9Package registry (OSV)
almalinux:mysql-errmsg8.4.6-1.module_el9.6.0+180+a4e757e5 · AlmaLinux:9Package registry (OSV)
almalinux:mysql-selinux1.0.14-1.el10_0 · AlmaLinux:10Package registry (OSV)
almalinux:mysql8.4-common8.4.6-2.el10_0 · AlmaLinux:10Package registry (OSV)
almalinux:mysql8.4-errmsg8.4.6-2.el10_0 · AlmaLinux:10Package registry (OSV)
almalinux:mysql8.4-test-data8.4.6-2.el10_0 · AlmaLinux:10Package registry (OSV)
alpine:openssl3.0.19-r0 · Alpine:v3.17Package registry (OSV)
debian:edk22025.02-8+deb13u1 · Debian:13Package registry (OSV)
debian:openssl3.0.16-1~deb12u1 · Debian:12Package registry (OSV)
opensuse:openssl-1_11.1.1w-150600.5.12.2 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:openssl-33.1.4-150600.5.24.1 · openSUSE:Leap 15.6Package registry (OSV)
rocky linux:mysql-selinux0:1.0.14-1.el10_0 · Rocky Linux:10Package registry (OSV)
rocky linux:mysql8.40:8.4.6-2.el10_0 · Rocky Linux:10Package registry (OSV)

+6

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:02026-08-19

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+575 d
  3. TodayNov 9, 2026+658 d

No history yet (it accumulates with the daily EPSS job).

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2025-9231253 days apartTiming side-channel in SM2 algorithm on 64 bit ARM
    23Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Physical access to the device is required.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Physical
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. CVSS4.1 → 4.6
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records