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

Divide by 0 error as totalSupply() can be equal to 0 #102

Closed
code423n4 opened this issue Jan 31, 2022 · 2 comments
Closed

Divide by 0 error as totalSupply() can be equal to 0 #102

code423n4 opened this issue Jan 31, 2022 · 2 comments
Labels
1 (Low Risk) Assets are not at risk. State handling, function incorrect as to spec, issues with comments bug Something isn't working duplicate This issue or pull request already exists

Comments

@code423n4
Copy link
Contributor

Handle

Dravee

Vulnerability details

Impact

Divide by 0 panic error.

Proof of Concept

The check exists in the _mint() function to prevent a divide by 0 error:

File: sNOTE.sol
348:         if (_totalSupply == 0) {

However, sNote.sol:getPoolTokenShare() doesn't check for totalSupply() != 0:

File: sNOTE.sol
257:     function getPoolTokenShare(uint256 sNOTEAmount) public view returns (uint256 bptClaim) {
258:         uint256 bptBalance = BALANCER_POOL_TOKEN.balanceOf(address(this));
259:         // BPT and sNOTE are both in 18 decimal precision so no conversion required
260:         return (bptBalance * sNOTEAmount) / totalSupply();
261:     }

Neither does getVotingPower():

File: sNOTE.sol
292:         return (noteAmount * sNOTEAmount) / totalSupply();

Tools Used

VS Code

Recommended Mitigation Steps

Check that totalSupply() != 0 before division

@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 Jan 31, 2022
code423n4 added a commit that referenced this issue Jan 31, 2022
@jeffywu jeffywu added the duplicate This issue or pull request already exists label Feb 6, 2022
@jeffywu
Copy link
Collaborator

jeffywu commented Feb 6, 2022

Duplicate #170

@pauliax
Copy link
Collaborator

pauliax commented Feb 14, 2022

#170

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 duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

4 participants