Security context
What an agent needs to avoid regressing past fixes and find the next vuln in this repo.
intersectmbo/plutus
master @ 965fef1
25
Fixes
0
CVEs
HIGH
Peak severity
72.2%
Coverage
Highlights
Auth Bypass: 9 prior fixes. Scrutinize any change in this area.
plutus-core/plutus-core/src/PlutusCore/Value.hs: most-fixed (4 issues). Treat as high-risk during review.
13 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: Flaws in transaction script checks, such as letting negative token values bypass checks or validating single tokens rather than whole currency symbol maps, allow malicious minting and balance bypasses. Developers must enforce strict map-wide checks and reject negative balances.
Input Validation: Failing to enforce canonical structure during deserialization allows malformed values to pass validation, potentially leading to consensus splitting or logic bypasses in Plutus Core.
Privilege Escalation: Over-privileged GITHUB_TOKEN permissions in GitHub Actions workflows pose a token-hijacking threat on runners. Restricting all workflow permissions to read-only by default is critical.