elliptic vulnerabilities
EC cryptography
- Registry
- npm
- Latest
- 6.6.1
- License
- MIT
9 known advisories
The latest version, 6.6.1, is affected by 1 of them.
Security advisories for elliptic
Elliptic Uses a Cryptographic Primitive with a Risky Implementation
- Affected
- <=6.6.1
- Fixed in
- No fix released
Elliptic's private key extraction in ECDSA upon signing a malformed input (e.g. a string)
- Affected
- <6.6.1
- Fixed in
- 6.6.1
Valid ECDSA signatures erroneously rejected in Elliptic
- Affected
- <6.6.0
- Fixed in
- 6.6.0
Elliptic's verify function omits uniqueness validation
- Affected
- <6.5.6
- Fixed in
- 6.5.6
Elliptic allows BER-encoded signatures
- Affected
- >=5.2.1 <6.5.7
- Fixed in
- 6.5.7
Elliptic's ECDSA missing check for whether leading bit of r and s is zero
- Affected
- >=2.0.0 <6.5.7
- Fixed in
- 6.5.7
Elliptic's EDDSA missing signature length check
- Affected
- >=4.0.0 <6.5.7
- Fixed in
- 6.5.7
Elliptic Uses a Broken or Risky Cryptographic Algorithm
- Affected
- <6.5.4
- Fixed in
- 6.5.4
Signature Malleabillity in elliptic
- Affected
- <6.5.3
- Fixed in
- 6.5.3
Which of your client projects still run an old elliptic?
NPMscan reads the package-lock.json, yarn.lock and pnpm-lock.yaml in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other npm packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the npm registry.