-
Notifications
You must be signed in to change notification settings - Fork 0
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
WardenPledge.sol recoverERC20() can be used as a backdoor by the owner to retrieve RewardToken #84
Labels
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
duplicate-68
satisfactory
satisfies C4 submission criteria; eligible for awards
Comments
Duplicate of #17 |
kirk-baird marked the issue as not a duplicate |
kirk-baird marked the issue as duplicate |
kirk-baird marked the issue as satisfactory |
kirk-baird marked the issue as not a duplicate |
kirk-baird marked the issue as duplicate of #17 |
Simon-Busch marked the issue as duplicate of #68 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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
duplicate-68
satisfactory
satisfies C4 submission criteria; eligible for awards
Lines of code
https://github.com/code-423n4/2022-10-paladin/blob/main/contracts/WardenPledge.sol#L653-L661
Vulnerability details
Impact
Users can lose all the rewards to the malicious/compromised owner.
Proof of Concept
https://github.com/code-423n4/2022-10-paladin/blob/main/contracts/WardenPledge.sol#L653-L661
Tools Used
Recommended Mitigation Steps
Change to:
The text was updated successfully, but these errors were encountered: