Skip to content
high MEV / Ordering No SWC entry CWE-682

Sandwich Attack via Missing Slippage Protection

SAFE-0058 MEV / Ordering Checked automatically by the scanner
1

What goes wrong

A swap sets amountOutMin to 0 (or no slippage bound), so an attacker brackets the trade with buy/sell to force maximum slippage and extract value.

2

How to fix it

the pattern that is safe
router.swapExactTokensForTokens(amtIn, minOut, path, to, deadline);
// minOut from a trusted quote with slippage tolerance
◆
Always set minOut and a deadline.
3

Related vulnerabilities in MEV / Ordering

SAFE-0057Front-Running / Transaction Ordering Dependence high · MEV / Ordering SAFE-0085Missing Slippage Protection on Liquidity/Swap Ops high · MEV / Ordering SAFE-0104Swap Without Slippage Protection (minAmountOut = 0) high · MEV / Ordering SAFE-0059Missing Deadline on Swaps / Stale Execution medium · MEV / Ordering SAFE-0086Swap Path / Route Validation Missing medium · MEV / Ordering SAFE-0105Swap Deadline Set to block.timestamp medium · MEV / Ordering SAFE-0252Front-Runnable Reveal (No Commit-Reveal) medium · MEV / Ordering
← PreviousFront-Running / Transaction Ordering Dependence
Check your own contract for this

The SaferICO scanner runs 201 detectors over your Solidity source, SAFE-0058 among them. Paste an address or the source itself — a small per-scan fee, shown before you sign, or unlimited on any plan.

Run the scanner See how it is attacked Read the docs