Skip to content
high Token Standards SWC-105 CWE-284

Burn Authorization / Burn-From Missing Checks

SAFE-0055 Token Standards Checked automatically by the scanner
1

What goes wrong

A burn or burnFrom function does not verify allowance/ownership, letting an attacker burn other users' tokens, or burns without updating dependent accounting (rewards, shares).

2

How to fix it

the pattern that is safe
function burnFrom(address from, uint256 amt) external {
    _spendAllowance(from, msg.sender, amt);
    _burn(from, amt);
}
◆
Enforce allowance/ownership on burns.
3

Related vulnerabilities in Token Standards

SAFE-0053Unsafe / Unprotected Minting critical · Token Standards SAFE-0051Missing SafeERC20 / Non-Standard Token Handling high · Token Standards SAFE-0052Fee-on-Transfer / Rebasing Token Accounting Mismatch high · Token Standards SAFE-0107Fee-on-Transfer / Rebasing Token Mis-Accounting high · Token Standards SAFE-0208Non-Standard ERC20 Return Value Not Handled high · Token Standards SAFE-0050ERC-20 Approval Race Condition medium · Token Standards SAFE-0054ERC-721/1155 Missing Receiver Validation (Safe Transfer) medium · Token Standards SAFE-0056EIP-2612 Permit Misuse / Front-Running medium · Token Standards
← PreviousERC-721/1155 Missing Receiver Validation (Safe Transfer)
Check your own contract for this

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