Security context
What an agent needs to avoid regressing past fixes and find the next vuln in this repo.
tritonvm/triton-vm
master @ 8cd9a0e
5
Fixes
0
CVEs
HIGH
Peak severity
Highlights
Auth Bypass: 2 prior fixes. Scrutinize any change in this area.
triton-vm: most-fixed (3 issues). Treat as high-risk during review.
5 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: Attackers could bypass STARK proof validation by exploiting implicit or untrusted fields within the proof structure rather than validating against an explicit, caller-provided Claim, or by manipulating untrusted padded_height values.
Cryptographic Issues: Omitting critical structural parameters (like the Claim itself) from the Fiat-Shamir transcript enables proof forgeability and substitution attacks during STARK verification.
Cryptographic Vulnerability: Excluding the FRI polynomial from the Fiat-Shamir transcript state allows a dishonest prover to modify the polynomial after random challenges are sampled, undermining soundness.