Skip to content
high Denial of Service SWC-132 CWE-664

Locked Ether / No Withdrawal Path

SAFE-0040 Denial of Service Checked automatically by the scanner
1

What goes wrong

A contract can receive Ether (payable / receive) but has no function to withdraw it, permanently locking any funds sent.

2

How to fix it

the pattern that is safe
receive() external payable {}
function withdraw() external onlyOwner {
    payable(owner).transfer(address(this).balance);
}
◆
Always provide a guarded withdrawal/sweep.
3

Related vulnerabilities in Denial of Service

SAFE-0037DoS via Unexpected Revert in Loop / Push Payments high · Denial of Service SAFE-0038DoS via Unbounded Loop / Gas Exhaustion high · Denial of Service SAFE-0080Out-of-Gas in Loop Causing Stuck Funds high · Denial of Service SAFE-0124Push-Payment DoS (Loop of External Transfers) high · Denial of Service SAFE-0039Gas Griefing via Subcall Gas Forwarding medium · Denial of Service SAFE-0041Forced Ether Reception Breaking Balance Invariants medium · Denial of Service SAFE-0098Insufficient Withdrawal / Pull Pattern Not Enforced medium · Denial of Service SAFE-0214Unbounded Batch Mint / Airdrop Loop medium · Denial of Service
← PreviousGas Griefing via Subcall Gas Forwarding
Check your own contract for this

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