Security context
What an agent needs to avoid regressing past fixes and find the next vuln in this repo.
ipsilon/evmone
master @ 3616ba6
15
Fixes
0
CVEs
HIGH
Peak severity
38.5%
Coverage
Highlights
Memory Corruption: 5 prior fixes. Scrutinize any change in this area.
lib/evmone/execution.cpp: most-fixed (9 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.
Memory Safety: The EVM execution loop consistently suffered from undefined behavior and potential out-of-bounds access when opcodes (such as SHA3, CODECOPY, and LOG) attempted to index potentially empty memory vectors using subscript syntax instead of safe pointer interfaces like data().
Memory Corruption: Reusing the execution state without fully resetting container stacks, transaction-specific metadata, and EOF fields allows state contamination across distinct EVM runs.
Auth Bypass: Failure to check for EVMC_STATIC mode flag within instructions allowed state-modifying opcodes to run in static contexts, violating EVM isolation properties.