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

arbitraryCall allow inherited governance to steal incentives #200

Closed
code423n4 opened this issue Dec 6, 2021 · 3 comments
Closed

arbitraryCall allow inherited governance to steal incentives #200

code423n4 opened this issue Dec 6, 2021 · 3 comments
Labels
3 (High Risk) Assets can be stolen/lost/compromised directly bug Something isn't working duplicate This issue or pull request already exists

Comments

@code423n4
Copy link
Contributor

Handle

gzeon

Vulnerability details

Impact

arbitraryCall did not check the balances of incentives, which allow inherited governance to steal the incentives.

Proof of Concept

https://github.com/code-423n4/2021-11-streaming/blob/56d81204a00fc949d29ddd277169690318b36821/Streaming/src/Locke.sol#L733

Recommended Mitigation Steps

Keep track of incentive token addresses in createIncentive and check the balance of each token before and after the arbitrary call to ensure trustlessness

@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 Dec 6, 2021
code423n4 added a commit that referenced this issue Dec 6, 2021
@brockelmore
Copy link
Collaborator

@ judges, this report is lacking the actual functionality to do so - i am inclined to dispute this particular report to reward those that actually provided PoC.

@brockelmore brockelmore added the duplicate This issue or pull request already exists label Dec 8, 2021
@0xean
Copy link
Collaborator

0xean commented Jan 14, 2022

@brockelmore - it is certainly light on the details, but does recommend a mitigation. I am going to leave it as a duplicate, but appreciate the sentiment that is would be hard if other's hadn't reported this issue to be sure of the vulnerability.

@0xean 0xean added 3 (High Risk) Assets can be stolen/lost/compromised directly and removed 2 (Med Risk) Assets not at direct risk, but function/availability of the protocol could be impacted or leak value labels Jan 14, 2022
@0xean
Copy link
Collaborator

0xean commented Jan 14, 2022

dupe of #199

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 bug Something isn't working duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

3 participants