Abstract: In some conditions, variables can overwrite different variables in storage.
Affected Solidity compiler variations: 0.1.6 to 0.4.3 (together with 0.4.4 pre-release variations)
Detailed description:
Storage variables which are smaller than 256 bits are packed collectively into the identical 256 bit slot if they’ll match. If a worth bigger than what’s allowed by the kind is assigned to the primary variable, that worth will overwrite the second variable.
This implies if an attacker may cause an overflow within the worth of the primary variable, then the second variable could be modified. Creating an overflow within the first variable is feasible utilizing arithmetics or by immediately passing in a worth from the decision knowledge (values in name knowledge are aligned to 32 bytes, and padding is neither verified nor enforced).
Contracts that solely use the kinds listed beneath for state variables are not affected. Arrays, mappings and structs (based mostly on these following sorts) are additionally not affected:
- signed integers, together with sizes smaller than 256 bits
- bytesNN sorts, together with sizes smaller than 256 bits
- unsigned integers (uint) of 256 bits
Contracts with sorts smaller than 256 bits which are by no means subsequent to one another (observe that state variables of base contracts are “pulled in”) are not affected.
The Ethereum multisignature pockets contract is not affected.
Word that addresses take up 160 bits, so contracts that solely use addresses and 256-bit sorts are protected. Moreover, addresses and booleans are virtually by no means manipulated through arithmetic operations in follow, so contracts utilizing solely addresses, booleans and 256 bit sorts must also be protected.
The next contracts could also be affected:
Contracts containing two or extra contiguous state variables the place the sum of their sizes is lower than 256 bits and the primary state variable shouldn’t be a signed integer and never of bytesNN sort.
Sorts smaller than 256 bits embrace:
bool, enums, uint8, …, uint248, int8, …, int248, deal with, any contract sort
Advisable motion:
- Recompile contracts that haven’t but been deployed utilizing at the very least Solidity launch 0.4.4 (not the pre-release or nightly model).
- Deactivate, take away funds from, or improve already deployed contracts.
This vulnerability was discovered by [github.com/catageek](https://github.com/catageek): [https://github.com/ethereum/solidity/issues/1306](https://github.com/ethereum/solidity/points/1306)