How severe is CVE-2019-25003?

CVE-2019-25003 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2019-25003 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (70th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2019-25003?

CVE-2019-25003 affects Parity Libsecp256k1. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2019-25003?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2019-25003 published?

CVE-2019-25003 was published on 2020-12-31 and last updated on 2026-06-17.

CVE-2019-25003

CVE-2019-25003 is a high-severity vulnerability in Parity Libsecp256k1 with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v2: 5.0
EPSS exploit prediction: 1% (70th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Parity Libsecp256k1
Published: 2020-12-31
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is 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.
How severe is CVE-2019-25003?: CVE-2019-25003 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2019-25003 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (70th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2019-25003?: CVE-2019-25003 affects Parity Libsecp256k1. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2019-25003?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2019-25003 published?: CVE-2019-25003 was published on 2020-12-31 and last updated on 2026-06-17.

References

https://rustsec.org/advisories/RUSTSEC-2019-0027.html

Affected products (1)

cpe:2.3:a:parity:libsecp256k1:*:*:*:*:*:rust:*:*

More vulnerabilities in Parity Libsecp256k1

CVE-2021-38195 — Critical (CVSS 9.8): An issue was discovered in the libsecp256k1 crate before 0.5.0 for Rust. It can verify an invalid signature because it…
CVE-2019-20399 — Medium (CVSS 5.9): A timing vulnerability in the Scalar::check_overflow function in Parity libsecp256k1-rs before 0.3.1 potentially allows…

All CVEs affecting Parity Libsecp256k1 →