Skip to content
high Logic / State SWC-109 CWE-824

Uninitialized Storage Pointer (legacy)

SAFE-0095 Logic / State Checked automatically by the scanner
1

What goes wrong

In older Solidity, an uninitialized local storage struct/array pointer defaults to slot 0, so writes overwrite critical early storage variables (like owner).

2

How to fix it

the pattern that is safe
StructT storage s = items[id]; s.x = 1; // explicit target
◆
SWC-109. Initialize storage pointers (legacy compilers).
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 Logic / State

SAFE-0071Incorrect Accounting / Internal Balance Drift high · Logic / State SAFE-0146msg.value Reused Across a Loop / Multicall high · Logic / State SAFE-0249Missing Claimed Flag — Double Claim high · Logic / State SAFE-0070State Desync Between Related Variables medium · Logic / State SAFE-0081Storage vs Memory Misuse Causing State Bug medium · Logic / State SAFE-0093Selfdestruct Dependency / Forced Removal Assumption medium · Logic / State SAFE-0094Predictable Contract Address / CREATE2 Reorg Risk medium · Logic / State SAFE-0142Uninitialised Storage Pointer medium · Logic / State
← PreviousPredictable Contract Address / CREATE2 Reorg Risk
Check your own contract for this

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