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

event PromotionCancelled should also emit the _to address #127

Open
code423n4 opened this issue Dec 12, 2021 · 0 comments
Open

event PromotionCancelled should also emit the _to address #127

code423n4 opened this issue Dec 12, 2021 · 0 comments
Assignees
Labels
1 (Low Risk) Assets are not at risk. State handling, function incorrect as to spec, issues with comments bug Something isn't working sponsor confirmed Sponsor agrees this is a problem and intends to fix it (OK to use w/ "disagree with severity")

Comments

@code423n4
Copy link
Contributor

Handle

hubble

Vulnerability details

Impact

Since there is an option for the promoter to provide an alternate address while issuing cancelPromotion apart from the creator(promoter address)
It is good to track the _to address where the remainingRewards are sent on cancelPromotion

Proof of Concept

contract : TwabRewards
line 50 : event PromotionCancelled(uint256 indexed promotionId, uint256 amount);

function : cancelPromotion(uint256 _promotionId, address _to)
line 135 : emit PromotionCancelled(_promotionId, _remainingRewards);

Tools Used

Manual review

Recommended Mitigation Steps

Add the 'to address' in the event, as below

line 50 : event PromotionCancelled(uint256 indexed promotionId, address to, uint256 amount);

function : cancelPromotion(uint256 _promotionId, address _to)
line 135 : emit PromotionCancelled(_promotionId, _to, _remainingRewards);

@code423n4 code423n4 added 1 (Low Risk) Assets are not at risk. State handling, function incorrect as to spec, issues with comments bug Something isn't working labels Dec 12, 2021
code423n4 added a commit that referenced this issue Dec 12, 2021
@PierrickGT PierrickGT self-assigned this Dec 13, 2021
@PierrickGT PierrickGT added the sponsor confirmed Sponsor agrees this is a problem and intends to fix it (OK to use w/ "disagree with severity") label Dec 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 (Low Risk) Assets are not at risk. State handling, function incorrect as to spec, issues with comments bug Something isn't working sponsor confirmed Sponsor agrees this is a problem and intends to fix it (OK to use w/ "disagree with severity")
Projects
None yet
Development

No branches or pull requests

2 participants