CVE-2022-41340 json
secp256k1-js implements ECDSA without required r and s validation, leading to signature forgery
published 2022-09-24 4 y ago modified 2026-06-17 4 mo ago also GHSA-q3f4-9h4p-vgr3 , EUVD-2022-6905
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 53%
- public exploits
- 0
- none known
Summary
The secp256k1-js package before 1.1.0 for Node.js implements ECDSA without required r and s validation, leading to signature forgery.
Patch / fix
- npm @lionello/secp256k1-js 1.1.0
- secp256k1-js_project secp256k1-js 1.1.0
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 17 mo ago
Exploit prediction
0.70% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | @lionello/secp256k1-js | <1.1.0 |
1.1.0 |
Classification
- Weakness
-
- CWE-347 Improper Verification of Cryptographic Signature
References
-
github.com
/lionello/secp256k1-js/commit/302800f0370b42e360a33774bb808274ac729c2e
web, patch, third-party-advisory
-
github.com
/lionello/secp256k1-js/compare/1.0.1...1.1.0
web, patch, third-party-advisory
-
github.com
/lionello/secp256k1-js/issues/11
web, issue-tracking, third-party-advisory
- npmjs.com /package/%40lionello/secp256k1-js
-
nvd.nist.gov
/vuln/detail/CVE-2022-41340
advisory
-
github.com
/lionello/secp256k1-js
package
-
npmjs.com
/package/@lionello/secp256k1-js
web
Sources
- CVE List CVE-2022-41340
- GitHub Advisory GHSA-q3f4-9h4p-vgr3
- NVD CVE-2022-41340
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.