Security context

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

zcash/halo2

              main @ 261faac
            

Fixes

CVEs

HIGH

Peak severity

80.0%

Coverage

Highlights

Cryptographic Issues: 4 prior fixes. Scrutinize any change in this area.

src/keys.rs: most-fixed (2 issues). Treat as high-risk during review.

2 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.

Cryptographic Issues: Incomplete addition in variable-base scalar multiplication allowed provers to choose arbitrary bases due to a lack of equality constraints, undermining the soundness of the proof system. This was fixed by anchoring the base using copy_advice.

Cryptographic Issues: A failure to reject the identity point representation when deserializing the Spend Validating Key (ak) could allow invalid or malicious keys to bypass spend verification logic.

Cryptographic Issues: Lack of validation for the sign of the y-coordinate during Spend Validating Key deserialization allowed non-canonical representation vulnerabilities.