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

Improper event declaration #196

Open
code423n4 opened this issue Jan 6, 2022 · 2 comments
Open

Improper event declaration #196

code423n4 opened this issue Jan 6, 2022 · 2 comments
Labels
0 (Non-critical) Code style, clarity, syntax, versioning, off-chain monitoring (events etc), exclude gas optimisation bug Something isn't working resolved Finding has been patched by sponsor (sponsor pls link to PR containing fix) 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

Czar102

Vulnerability details

Impact

Proper event declaration eases off-chain monitoring.

Proof of Concept

In the case of qualitative variables, it is recommended to use indexed keyword.

Despite the uint duration argument seems to be a quantitative one, it is limited to few values, which specify the "locking mode".

Recommended Mitigation Steps

uint duration variable should be considered qualitative and be marked indexed in the following events:

event LockPeriodSet(uint256 duration, uint8 bonusMultiplier);
event LockPositionCreated(uint256 indexed tokenId, address indexed owner, uint256 amount, uint256 duration);
@code423n4 code423n4 added 0 (Non-critical) Code style, clarity, syntax, versioning, off-chain monitoring (events etc), exclude gas optimisation bug Something isn't working labels Jan 6, 2022
code423n4 added a commit that referenced this issue Jan 6, 2022
@deluca-mike deluca-mike added the sponsor confirmed Sponsor agrees this is a problem and intends to fix it (OK to use w/ "disagree with severity") label Jan 7, 2022
@deluca-mike
Copy link
Collaborator

deluca-mike commented Jan 7, 2022

Agreed. We will mark them indexed in both LockPeriodSet and LockPositionCreated.

@deluca-mike
Copy link
Collaborator

Fixed in release candidate contract interface for LockPeriodSet and LockPositionCreated.

@deluca-mike deluca-mike added the resolved Finding has been patched by sponsor (sponsor pls link to PR containing fix) label Jan 14, 2022
@Ivshti Ivshti closed this as completed Jan 16, 2022
@CloudEllie CloudEllie reopened this Jan 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0 (Non-critical) Code style, clarity, syntax, versioning, off-chain monitoring (events etc), exclude gas optimisation bug Something isn't working resolved Finding has been patched by sponsor (sponsor pls link to PR containing fix) 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

4 participants