Valid ECDSA signatures erroneously rejected in Elliptic
Published 15 Oct 2024 · Updated 27 Nov 2025
Affected package
- Affected
- <6.6.0
- Fixed in
- 6.6.0
npm install elliptic@6.6.0Details
The Elliptic prior to 6.6.0 for Node.js, in its for ECDSA implementation, does not correctly verify valid signatures if the hash contains at least four leading 0 bytes and when the order of the elliptic curve's base point is smaller than the hash, because of an _truncateToN anomaly. This leads to valid signatures being rejected. Legitimate transactions or communications may be incorrectly flagged as invalid.
Is GHSA-fc9h-whq2-v747 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected elliptic, and gives you the command that fixes it.
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2024-48948
- Linkgithub.com/indutny/elliptic/issues/321
- Linkgithub.com/indutny/elliptic/pull/322
- Linkgithub.com/indutny/elliptic/commit/34c853478cec1be4e37260ed2cb12cdbdc6402cf
- Linkblog.trailofbits.com/2025/11/18/we-found-cryptography-bugs-in-the-elliptic-library-using-wycheproof
- Packagegithub.com/indutny/elliptic
- Linksecurity.netapp.com/advisory/ntap-20241220-0004
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.