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

sa9933 - The UUPS proxie standard is implemented incorrectly, making the protocol not upgradeable #168

Open
sherlock-admin2 opened this issue Oct 27, 2024 · 0 comments
Labels
Sponsor Disputed The sponsor disputed this issue's validity

Comments

@sherlock-admin2
Copy link
Contributor

sherlock-admin2 commented Oct 27, 2024

sa9933

High

The UUPS proxie standard is implemented incorrectly, making the protocol not upgradeable

Summary

SolConnector.sol contracts inherit OappUpgrrdeble and it inherits UUPSUpgradeable contract from Openzepelin, indicating that the devs of the protocol want to have the possibility of upgrading the above mentioned contracts at some point in the future.

the contracts also implement the OwnableUpgradeable contract, and the _authorizeUpgrade() function in both contracts has the onlyOwner modifer. This function is used to check whether the person who tries to update the implementation contract in the Proxy has the required access.

Root Cause

No response

Internal pre-conditions

No response

External pre-conditions

No response

Attack Path

No response

Impact

Contracts that are expected to be upgradable, can't be upgraded due to missing functionality

PoC

No response

Mitigation

Implement a call to the upgradeToAndCall() function

@sherlock-admin3 sherlock-admin3 added the Sponsor Disputed The sponsor disputed this issue's validity label Nov 3, 2024
@sherlock-admin4 sherlock-admin4 changed the title Bent Eggshell Sidewinder - The UUPS proxie standard is implemented incorrectly, making the protocol not upgradeable sa9933 - The UUPS proxie standard is implemented incorrectly, making the protocol not upgradeable Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Sponsor Disputed The sponsor disputed this issue's validity
Projects
None yet
Development

No branches or pull requests

2 participants