# Analysis of Storage Corruption Bug

DevFeed: [Analysis of Storage Corruption Bug](<https://devfeed.tech/articles/analysis-of-storage-corruption-bug-16787.md>)

Original publisher: [Read original article](<https://blog.ethereum.org/en/2016/11/09/analysis-storage-corruption-bug>)

Author: Christian Reitwiessner

Published: 2016-11-09T10:04:37Z

Content type: article

Language: en

Sources: [Ethereum Foundation Blog](<https://devfeed.tech/sources/ethereum-foundation-blog.md>)

Topics: [bug](<https://devfeed.tech/topics/bug.md>), [Exploit](<https://devfeed.tech/topics/exploit.md>), [Solidity](<https://devfeed.tech/topics/solidity.md>), [Compiler](<https://devfeed.tech/topics/compiler.md>)

Tags: [analysis](<https://devfeed.tech/tags/analysis.md>), [bug](<https://devfeed.tech/tags/bug.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [exploit](<https://devfeed.tech/tags/exploit.md>), [research-development](<https://devfeed.tech/tags/research-development.md>)

## AI overview

This article updates findings on a storage corruption bug in the Solidity compiler. Automated analysis reduced the potentially vulnerable contracts to 167, and manual review found ten vulnerable contracts. Most were exploitable only by owners, while the remaining cases offered limited advantages or affected only the user interface. The reviewed contracts could be fixed without upgrading the contracts themselves.

## Source excerpt

This blog post provides an update on our findings following the discovery of the storage corruption bug last week. In summary, the bug was much less severe than we initially thought. The small number of affected contracts we found is either only exploitable by the owner, or the exploit can only cause a disruption in...