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

0brxce - requireProposerOrAcceptor name differs from implementation #237

Closed
sherlock-admin3 opened this issue Jun 27, 2024 · 0 comments
Closed
Labels
Excluded Excluded by the judge without consulting the protocol or the senior Non-Reward This issue will not receive a payout Sponsor Disputed The sponsor disputed this issue's validity

Comments

@sherlock-admin3
Copy link
Contributor

sherlock-admin3 commented Jun 27, 2024

0brxce

High

requireProposerOrAcceptor name differs from implementation

Summary

In the Admin Proxy contract, the requireProposerOrAcceptor modifier expects the caller to have the proposer role or acceptor role but the code implementation requires them to have both

Vulnerability Detail

The following functions have the requireProposerOrAcceptor modifier: proposeBaseImplementation, propose. If a caller doesn't have both roles the function call will fail.

Impact

The admin proxy will be unable to propose new base implementations or create new proposals

Code Snippet

requireProposerOrAcceptor Modifier
https://github.com/sherlock-audit/2024-06-mellow/blob/main/mellow-lrt/src/security/AdminProxy.sol#L42-L46

Modifier in use for proposeBaseImplementation and propose
https://github.com/sherlock-audit/2024-06-mellow/blob/main/mellow-lrt/src/security/AdminProxy.sol#L103-L113
https://github.com/sherlock-audit/2024-06-mellow/blob/main/mellow-lrt/src/security/AdminProxy.sol#L116-L125

Tool used

Manual Review

Recommendation

Use || instead of && in the conditional line for the requireProposerOrAcceptor modifier
Change the name to requireProposerAndModifier

@sherlock-admin4 sherlock-admin4 changed the title Shaggy Holographic Tuna - Steth::transferfrom will transfer 1-2 wei less which will result in reverting of consequent functions because of not enough balance. requireProposerOrAcceptor name differs from implementation Jun 28, 2024
@sherlock-admin3 sherlock-admin3 added the Sponsor Disputed The sponsor disputed this issue's validity label Jun 30, 2024
@github-actions github-actions bot changed the title requireProposerOrAcceptor name differs from implementation Melodic Juniper Griffin - requireProposerOrAcceptor name differs from implementation Jul 6, 2024
@github-actions github-actions bot closed this as completed Jul 6, 2024
@github-actions github-actions bot added the Excluded Excluded by the judge without consulting the protocol or the senior label Jul 6, 2024
@sherlock-admin3 sherlock-admin3 changed the title Melodic Juniper Griffin - requireProposerOrAcceptor name differs from implementation 0brxce - requireProposerOrAcceptor name differs from implementation Jul 15, 2024
@sherlock-admin3 sherlock-admin3 added the Non-Reward This issue will not receive a payout label Jul 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Excluded Excluded by the judge without consulting the protocol or the senior Non-Reward This issue will not receive a payout Sponsor Disputed The sponsor disputed this issue's validity
Projects
None yet
Development

No branches or pull requests

1 participant