Skip to content
medium Input Validation No SWC entry CWE-20

Missing Input Validation / Parameter Bounds

SAFE-0073 Input Validation Checked automatically by the scanner
1

What goes wrong

User-supplied parameters (fees, ratios, durations, amounts) are used without sanity bounds, enabling extreme/abusive values (e.g. 100% fee, zero duration) that break invariants.

2

How to fix it

the pattern that is safe
function setFeeBps(uint b) external onlyOwner { require(b <= 1000, "max 10%"); feeBps=b; }
◆
Bound all configurable parameters.
3

Where this has happened

Largest recorded losses in the same failure class — related, not the same bug:

$586M · 2022 BNB Chain Token Hub Input validation · 2022 $326M · 2022 Wormhole Input validation · 2022 $197M · 2023 Euler Finance Input validation · 2023 $190M · 2022 Nomad Bridge Input validation · 2022
4

Related vulnerabilities in Input Validation

SAFE-0074Array Length Mismatch in Batch Operations medium · Input Validation SAFE-0072Missing Zero-Address Validation low · Input Validation SAFE-0089Short Address / Calldata Padding (legacy) low · Input Validation SAFE-0140Missing Zero-Address Validation on Critical Setter low · Input Validation SAFE-0255Array Index Used Without Bounds Assumption low · Input Validation SAFE-0304Missing Zero-Value Validation on Value-Moving Function low · Input Validation
← PreviousMissing Zero-Address Validation
Check your own contract for this

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