Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No storage gap for upgradeable contracts #535

Closed
code423n4 opened this issue Oct 10, 2022 · 2 comments
Closed

No storage gap for upgradeable contracts #535

code423n4 opened this issue Oct 10, 2022 · 2 comments
Labels
bug Something isn't working duplicate This issue or pull request already exists invalid This doesn't seem right QA (Quality Assurance) Assets are not at risk. State handling, function incorrect as to spec, issues with clarity, syntax unsatisfactory does not satisfy C4 submission criteria; not eligible for awards

Comments

@code423n4
Copy link
Contributor

Lines of code

https://github.com/code-423n4/2022-10-blur/blob/2fdaa6e13b544c8c11d1c022a575f16c3a72e3bf/contracts/BlurExchange.sol#L30

Vulnerability details

Impact

BlurExchange.sol

BlurExchange is an upgradeable contract inheriting some other contract. In case the contract need to be upgraded and inheriting new contract that use storage, the current storage slot may be collising . To prevent overriden storage slot, the contract should added a storage gap.

if storage gap ain't added, the contract may not introduce new variable at the inheriting contract.

Proof of Concept

BlurExchange

    /// current inheritance 
    contract BlurExchange is IBlurExchange, ReentrancyGuarded, EIP712, OwnableUpgradeable, UUPSUpgradeable {
        ...
    }

    /// In case the contract need more inheritance 
    contract BlurExchange is MaybeSomethingContract, IBlurExchange, ReentrancyGuarded, EIP712, OwnableUpgradeable, UUPSUpgradeable {
        ...
    }

Tools Used

VSCode

Recommended Mitigation Steps

Consider adding a storage gap at the start of the upgradeable contract

@code423n4 code423n4 added 2 (Med Risk) Assets not at direct risk, but function/availability of the protocol could be impacted or leak value bug Something isn't working labels Oct 10, 2022
code423n4 added a commit that referenced this issue Oct 10, 2022
@GalloDaSballo
Copy link
Collaborator

Dup of #410

@GalloDaSballo GalloDaSballo added the duplicate This issue or pull request already exists label Oct 13, 2022
@GalloDaSballo GalloDaSballo added QA (Quality Assurance) Assets are not at risk. State handling, function incorrect as to spec, issues with clarity, syntax and removed 2 (Med Risk) Assets not at direct risk, but function/availability of the protocol could be impacted or leak value labels Oct 27, 2022
@GalloDaSballo
Copy link
Collaborator

L

@JeeberC4 JeeberC4 added invalid This doesn't seem right unsatisfactory does not satisfy C4 submission criteria; not eligible for awards labels Nov 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working duplicate This issue or pull request already exists invalid This doesn't seem right QA (Quality Assurance) Assets are not at risk. State handling, function incorrect as to spec, issues with clarity, syntax unsatisfactory does not satisfy C4 submission criteria; not eligible for awards
Projects
None yet
Development

No branches or pull requests

3 participants