Double spending via unchecked public signal bounds
Published May 21, 2023 · Updated Jan 21, 2025
Improper input validation in iden3 snarkjs 0.6.11 and earlier allows remote attackers to double-spend via crafted Groth16 proofs. The Groth16 verifier in src/groth16_verify.js processes publicSignals without first enforcing the field-modulus bound, allowing an invalid proof input to pass verification. Exploitation requires a consuming application to accept an attacker-controlled proof and use successful verification as spend authorization, where repeated acceptance permits double spending.
Summary
What happened
Improper input validation in iden3 snarkjs 0.6.11 and earlier allows remote attackers to double-spend via crafted Groth16 proofs. The Groth16 verifier in src/groth16_verify.js processes publicSignals without first enforcing the field-modulus bound, allowing an invalid proof input to pass verification. Exploitation requires a consuming application to accept an attacker-controlled proof and use successful verification as spend authorization, where repeated acceptance permits double spending.
The record
- CVE
- CVE-2023-33252
- Published
- May 21, 2023
- Updated
- Jan 21, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-862
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 21, 2023CVE publishedPublication date reported by the CVE source.
- Jan 21, 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
No public exploit references are available in this record.
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