Unsound proof via missing inverse constraints
Published Aug 8, 2021 · Updated Aug 4, 2024
Incorrect calculation in ark-r1cs-std for Rust 0.2.0 through 0.3.0 allows remote attackers to produce unsound proofs via crafted constraints. The FieldVar::mul_by_inverse method omits all required R1CS constraints, allowing a malicious prover to submit assignments that verify despite invalid inverse relationships. Exploitation requires control of proof generation; the resulting proof can be accepted as valid, undermining soundness of affected zero-knowledge applications.
Summary
What happened
Incorrect calculation in ark-r1cs-std for Rust 0.2.0 through 0.3.0 allows remote attackers to produce unsound proofs via crafted constraints. The FieldVar::mul_by_inverse method omits all required R1CS constraints, allowing a malicious prover to submit assignments that verify despite invalid inverse relationships. Exploitation requires control of proof generation; the resulting proof can be accepted as valid, undermining soundness of affected zero-knowledge applications.
The record
- CVE
- CVE-2021-38194
- Published
- Aug 8, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-682
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 8, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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