Signature forgery via zero-value ECDSA parameters
Published Sep 24, 2022 · Updated May 22, 2025
Improper ECDSA signature verification in @lionello/secp256k1-js before 1.1.0 allows remote attackers to forge signatures. The ecverify function accepts zero for both r and s, causing a crafted (0, 0) signature to pass verification for arbitrary messages. Any application that submits attacker-controlled signatures to this function can accept unauthentic data as valid without privileges or user interaction.
Summary
What happened
Improper ECDSA signature verification in @lionello/secp256k1-js before 1.1.0 allows remote attackers to forge signatures. The ecverify function accepts zero for both r and s, causing a crafted (0, 0) signature to pass verification for arbitrary messages. Any application that submits attacker-controlled signatures to this function can accept unauthentic data as valid without privileges or user interaction.
The record
- CVE
- CVE-2022-41340
- Published
- Sep 24, 2022
- Updated
- May 22, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-347
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 24, 2022CVE publishedPublication date reported by the CVE source.
- May 22, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Zero-value ECDSA signature proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo