Security context

What an agent needs to avoid regressing past fixes and find the next vuln in this repo.

risc0/risc0-ethereum
main @ 3aa1378
5
Fixes
0
CVEs
HIGH
Peak severity
Highlights
Auth Bypass: 2 prior fixes. Scrutinize any change in this area.
contracts/src/RiscZeroSetVerifier.sol: most-fixed (1 issue). Treat as high-risk during review.
3 high-severity fixes in this history; regressions here are high-impact.
Recurring patterns

The bug types that recur here, drawn from past fixes, not open vulnerabilities.

Auth Bypass: Missing or insufficient validation of the configuration ID (configID) allowed commitments generated under mismatched or malicious configuration parameters to successfully pass verification. Future modifications to verification engines must guarantee config IDs are structurally validated and strictly verified.
Auth Bypass: Commitments previously omitted chain configuration parameters from the commitment journal, allowing proofs to be replayed or executed across different chain configurations. The configuration hash must be directly bound to the commitment payload.
Logic Error: Allowing user-supplied indices in Merkle paths during Beacon Chain inclusion proof verification enabled spoofing. Verification must be anchored to a fixed, expected block hash Merkle leaf index with strict path canonicalization.