Reentrancy attacks
The OWASP framing of the same failure as SWC-107, including the cross-contract variants.
What it is
Beyond the single-function case, the OWASP entry covers cross-function reentrancy through shared state, cross-contract reentrancy through a shared accounting contract, and read-only reentrancy, where your view function is read mid-update by another protocol.
Why it matters
Fund drainage in the direct cases; in the read-only case, losses land on a protocol that did nothing wrong except trust your price feed.
How to fix it
- Checks-effects-interactions everywhere, guards on every function touching shared state.
- Consider what other protocols read from you, and whether those views are consistent mid-update.
A full walkthrough of this bug class, including the variants that catch teams who thought they had fixed it, is in the long-form guide.
How it is detected
Every audit on EVM Smart Audit checks for SC05 and reports it as passed or flagged in the standards coverage grid — so the report tells you it was checked even when nothing was found. See the detector suite for what else runs alongside it, or the full database for the other 21 checks.
Check your contract for reentrancy attacks
The engine runs this check and 21 others on every audit, and shows what passed as well as what failed.
Start audit