RISC Zero zkVM Underconstrained Vulnerability
risc0
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| risc0-zkvm crates.io |
|
|
| risc0-circuit-rv32im crates.io |
|
|
risc0
| Product | Affected | Fixed in |
|---|---|---|
| risc0-zkvm crates.io |
|
|
| risc0-circuit-rv32im crates.io |
|
|
RISC Zero is a general computing platform based on zk-STARKs and the RISC-V microarchitecture. Due to a missing constraint in the rv32im circuit, any 3-register RISC-V instruction (including remu and divu) in risc0-zkvm 2.0.0, 2.0.1, and 2.0.2 are vulnerable to an attack by a malicious prover. The main idea for the attack is to confuse the RISC-V virtual machine into treating the value of the rs1 register as the same as the rs2 register due to a lack of constraints in the rv32im circuit. Rust applications using the risc0-zkvm crate at versions 2.0.0, 2.0.1, and 2.0.2 should upgrade to version 2.1.0. Smart contract applications using the official RISC Zero Verifier Router do not need to take any action: zkVM version 2.1 is active on all official routers, and version 2.0 has been disabled. Smart contract applications not using the verifier router should update their contracts to send verification calls to the 2.1 version of the verifier.
From the CVE record · GitHub_M
A missing constraint in the rv32im circuit affects three-register RISC-V instructions, including remu and divu. A malicious prover can cause the virtual machine to treat the rs1 register value as the rs2 register value. The input does not specify an authentication requirement or user interaction.
Check Rust applications using risc0-zkvm >=2.0.0 <2.1.0 or risc0-circuit-rv32im >=2.0.0 <2.0.4, and smart contracts that verify RISC Zero proofs without the official Verifier Router.