CVE-2019-25003

An issue was discovered in the libsecp256k1 crate before 0.3.1 for Rust. Scalar::check_overflow allows a timing side-channel attack; consequently, attackers can obtain sensitive information.

Published: 2020-12-31 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2019-25003 is rated Moderate Risk (55.4/100): CVSS High severity, with medium exploitation likelihood (EPSS 1.42%). EPSS rose +1.21% over the last day, indicating growing attacker interest. Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2019-25003

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.21% 1.42% +1.21%
2 2026-02-13 0.29% 0.21% -0.08%
3 2025-03-30 — 0.29% —

Full EPSS history (9 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2019-25003

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]
5.0 2.0 MEDIUM
AV:N/AC:L/Au:N/C:P/I:N/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
 10.0 2.9 [email protected]

Weakness enumeration for CVE-2019-25003

GitHub Security Advisory for CVE-2019-25003

GHSA-hrjm-c879-pp86 · Severity: high · Ecosystem: rust — libsecp256k1 contains side-channel timing attack

OS Trackers for CVE-2019-25003

vendor priority summary link
alpine high CVE-2019-25003: 1 source package rows (libsecp256k1); 3 state rows across 2 repos (3.17-community, edge-community); fixed 3, open 0. https://security.alpinelinux.org/vuln/CVE-2019-25003

Affected software / configurations for CVE-2019-25003

Vendor Product Version Raw CPE
parity libsecp256k1 < 0.3.1 cpe:2.3:a:parity:libsecp256k1:*:*:*:*:*:rust:*:*

References for CVE-2019-25003

cvelogic Threat Intelligence