Skip to content

Authorization Through msg.data / Signature Confusion

SAFE-0013 Access Control Checked automatically by the scanner
1

What goes wrong

Access decisions rely on raw msg.data, function selectors, or loosely-parsed calldata that an attacker can craft to impersonate a privileged path or replay another method's intent.

2

How to fix it

the pattern that is safe
function adminThing() external onlyOwner { _doAdminThing(); }
// explicit, typed, access-controlled entrypoint
Prefer explicit typed functions with modifiers over msg.data routing.
Check your own contract for this

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