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

Missing Slippage Protection on Liquidity/Swap Ops

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

What goes wrong

Add/remove-liquidity or multi-hop operations accept no minimum amounts, exposing users to sandwiching and unfavorable execution.

2

How to fix it

the pattern that is safe
router.removeLiquidity(a, b, lp, minA, minB, to, deadline); // enforce minimums
◆
Always set minimum outputs on AMM operations.
3

Related vulnerabilities in MEV / Ordering

SAFE-0057Front-Running / Transaction Ordering Dependence high · MEV / Ordering SAFE-0058Sandwich Attack via Missing Slippage Protection 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
← PreviousIncorrect Decimal / Token Unit Handling
Check your own contract for this

The SaferICO scanner runs 201 detectors over your Solidity source, SAFE-0085 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