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

claimExact() Missing Validation As In claim() #194

Open
code423n4 opened this issue Nov 10, 2021 · 2 comments
Open

claimExact() Missing Validation As In claim() #194

code423n4 opened this issue Nov 10, 2021 · 2 comments
Labels
0 (Non-critical) Code style, clarity, syntax, versioning, off-chain monitoring (events etc), exclude gas optimisation bug Something isn't working sponsor acknowledged Technically the issue is correct, but we're not going to resolve it for XYZ reasons

Comments

@code423n4
Copy link
Contributor

Handle

Meta0xNull

Vulnerability details

Impact

claim() and claimExact() Both Should Have Same Verification Requirements. But claimExact() Missing Validation Code as claim() in Line 524.

Code: require(validated[msg.sender] == 1, "Address not validated to claim.");

Proof of Concept

https://github.com/code-423n4/2021-11-bootfinance/blob/main/vesting/contracts/AirdropDistribution.sol#L524

Tools Used

Manual Review

Recommended

Insert Missing Validation Code Between Line 552 and 553 for claimExact()

https://github.com/code-423n4/2021-11-bootfinance/blob/main/vesting/contracts/AirdropDistribution.sol#L552-L553

@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 Nov 10, 2021
code423n4 added a commit that referenced this issue Nov 10, 2021
@chickenpie347 chickenpie347 added the sponsor acknowledged Technically the issue is correct, but we're not going to resolve it for XYZ reasons label Jan 3, 2022
@chickenpie347
Copy link
Collaborator

The check at claimexact require(airdrop[msg.sender].amount != 0); removes the need for the validation.

@0xean
Copy link
Collaborator

0xean commented Jan 8, 2022

I believe the sponsor is correct here, but would be good to standardize these checks across the functions to avoid confusion. Downgrading to 0 - Non Critical as a clarity issue.

@CloudEllie CloudEllie added 0 (Non-critical) Code style, clarity, syntax, versioning, off-chain monitoring (events etc), exclude gas optimisation and removed 1 (Low Risk) Assets are not at risk. State handling, function incorrect as to spec, issues with comments labels Jan 10, 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 sponsor acknowledged Technically the issue is correct, but we're not going to resolve it for XYZ reasons
Projects
None yet
Development

No branches or pull requests

4 participants