Filtered by vendor Indutny Subscriptions
Total 6 CVE
CVE Vendors Products Updated CVSS v3.1
CVE-2024-42459 3 Elliptic Project, Indutny, Redhat 5 Elliptic, Elliptic, Acm and 2 more 2025-06-20 5.3 Medium
In the Elliptic package 6.5.6 for Node.js, EDDSA signature malleability occurs because there is a missing signature length check, and thus zero-valued bytes can be removed or appended.
CVE-2024-42460 3 Elliptic Project, Indutny, Redhat 5 Elliptic, Elliptic, Acm and 2 more 2025-06-20 5.3 Medium
In the Elliptic package 6.5.6 for Node.js, ECDSA signature malleability occurs because there is a missing check for whether the leading bit of r and s is zero.
CVE-2024-48948 2 Indutny, Nodejs 2 Elliptic, Elliptic 2025-06-20 4.8 Medium
The Elliptic package 6.5.7 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.
CVE-2024-48949 2 Indutny, Redhat 7 Elliptic, Acm, Multicluster Engine and 4 more 2025-03-25 9.1 Critical
The verify function in lib/elliptic/eddsa/index.js in the Elliptic package before 6.5.6 for Node.js omits "sig.S().gte(sig.eddsa.curve.n) || sig.S().isNeg()" validation.
CVE-2020-28498 1 Indutny 1 Elliptic 2024-11-21 6.8 Medium
The package elliptic before 6.5.4 are vulnerable to Cryptographic Issues via the secp256k1 implementation in elliptic/ec/key.js. There is no check to confirm that the public key point passed into the derive function actually exists on the secp256k1 curve. This results in the potential for the private key used in this implementation to be revealed after a number of ECDH operations are performed.
CVE-2020-13822 2 Indutny, Redhat 3 Elliptic, Openshift, Red Hat Single Sign On 2024-11-21 7.7 High
The Elliptic package 6.5.2 for Node.js allows ECDSA signature malleability via variations in encoding, leading '\0' bytes, or integer overflows. This could conceivably have a security-relevant impact if an application relied on a single canonical signature.