Solidity released version 0.8.39, fixing a silent destructible storage vulnerability
BIBIBI
AT A GLANCE
Solidity released version 0.8.39, fixing a vulnerability where recursive struct copying might silently corrupt storage.
Article
Solidity releases version 0.8.39, fixing a vulnerability that could silently corrupt storage
PANews November 20 reports, according to official sources, Solidity has released version 0.8.39, fixing a medium-severity vulnerability that could corrupt storage without throwing an error. The vulnerability occurs when recursively structured data in storage is copied into a storage structure containing it; multiple 0.8 versions are affected. The fix adds runtime overlap checks but increases gas consumption. After scanning verified contracts, the team found no deployed contracts affected.
According to PANews, Solidity has released version 0.8.39.
02
Reports indicate that this version fixes a serious vulnerability that could damage storage without causing errors.
03
Reports indicate that the vulnerability occurs when copying a recursive structure into another structure that contains it, and multiple 0.8 versions are affected.
04
Reports indicate that runtime overlap checks have been added for fixes, but this will increase gas consumption.
05
Reports indicate that after the team scanned the verified contracts, no affected deployed contracts were found.
AI-assisted interpretation
The following is analysis, separate from reported facts. Verify important claims independently.
The report describes a problem related to the storage duplication of recursive structures: damage to storage may occur during duplication without an error message. In 0.8.39, runtime overlap checks were added to fix this issue, but these checks increase gas consumption.
Why it matters to readers
If the contract uses the replication pattern described in the report, silent storage corruption may affect data correctness; the runtime checks for repair might incur additional gas costs. The report does not mention any verified instances of impact in the validated contracts.
Developers using Solidity can verify the version they are using and ensure that the code does not involve this copy pattern, and pay attention to the gas cost of runtime checks after an upgrade.
Risks and unknowns
The report does not provide a link to the official release announcement, vulnerability number, or specific version range affected.
The scanning scope and method for “Team Scan has verified contracts” is not specified, so it cannot be used to confirm that all deployed contracts are unaffected.
The actual gas overhead due to the added runtime overlap check is not provided.
Related Developments
Loading event timeline…
Related concepts
Recursive structure: A structure that may contain its own hierarchical structure.
This term is not in the glossary yet. Browse related concepts in the glossary.
View glossary →Runtime overlap check: The check added during repair; no specific implementation details are provided in the report.
This term is not in the glossary yet. Browse related concepts in the glossary.
View glossary →Gas: The unit of resource consumption for Ethereum operations.
This term is not in the glossary yet. Browse related concepts in the glossary.