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

Upgraded Q -> 3 from #154 [1675567996775] #684

Closed
c4-judge opened this issue Feb 5, 2023 · 2 comments
Closed

Upgraded Q -> 3 from #154 [1675567996775] #684

c4-judge opened this issue Feb 5, 2023 · 2 comments
Labels
3 (High Risk) Assets can be stolen/lost/compromised directly duplicate-605 satisfactory satisfies C4 submission criteria; eligible for awards

Comments

@c4-judge
Copy link
Contributor

c4-judge commented Feb 5, 2023

Judge has assessed an item in Issue #154 as 3 risk. The relevant finding follows:

Erc20Quest.withdrawFee() can be called against a quest more than once
function withdrawFee() public onlyAdminWithdrawAfterEnd {
IERC20(rewardToken).safeTransfer(protocolFeeRecipient, protocolFee());
}
The withdrawFee() function does not update the state of the Quest in such a way as to track claims against a set of currently-redeemed receipts. As such, even if no new users call claim(), protocol fees can be withdrawn more than once.

In the event of future decentralization of the protocol, unscrupulous projects could use this to reclaim tokens and deny valid receipts.

This multiple-claim issue factors into the Medium finding concerning denial of valid receipts due to griefing by 3rd parties.

@c4-judge c4-judge added the 3 (High Risk) Assets can be stolen/lost/compromised directly label Feb 5, 2023
c4-judge added a commit that referenced this issue Feb 5, 2023
@c4-judge c4-judge closed this as completed Feb 5, 2023
@c4-judge
Copy link
Contributor Author

c4-judge commented Feb 5, 2023

kirk-baird marked the issue as duplicate of #23

@c4-judge c4-judge added the satisfactory satisfies C4 submission criteria; eligible for awards label Feb 14, 2023
@c4-judge
Copy link
Contributor Author

kirk-baird marked the issue as satisfactory

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3 (High Risk) Assets can be stolen/lost/compromised directly duplicate-605 satisfactory satisfies C4 submission criteria; eligible for awards
Projects
None yet
Development

No branches or pull requests

1 participant