Security context
What an agent needs to avoid regressing past fixes and find the next vuln in this repo.
binance/zkmerkle-proof-of-solvency
main @ 9a3e5b7
3
Fixes
0
CVEs
HIGH
Peak severity
66.7%
Coverage
Highlights
Auth Bypass: 3 prior fixes. Scrutinize any change in this area.
circuit/batch_create_user_circuit.go: 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: Parallel proof verification committed proofs to the valid-proof cache ('safeProofMap') before the Groth16 verification actually completed, allowing unverified proofs to be treated as valid. This creates a complete verification bypass.
Auth Bypass: The batch creation user circuit lacked overflow and range constraints on the BasePrice field during api.Mul operations. This allowed inputs that overflow the field modulus to bypass intended pricing logic and constraint validation.
Auth Bypass: Validation of system tier ratios failed to enforce strict monotonic progression on parsed boundaries. This allows out-of-order or corrupt boundaries to bypass logical consistency guarantees.