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

Mint legendary gobbler with unrevealed gobblers #152

Closed
code423n4 opened this issue Sep 26, 2022 · 3 comments
Closed

Mint legendary gobbler with unrevealed gobblers #152

code423n4 opened this issue Sep 26, 2022 · 3 comments
Labels
bug Something isn't working duplicate This issue or pull request already exists QA (Quality Assurance) Assets are not at risk. State handling, function incorrect as to spec, issues with clarity, syntax

Comments

@code423n4
Copy link
Contributor

Lines of code

https://github.com/code-423n4/2022-09-artgobblers/blob/main/src/ArtGobblers.sol#L439
https://github.com/code-423n4/2022-09-artgobblers/blob/d2087c5a8a6a4f1b9784520e7fe75afa3a9cbdbe/src/ArtGobblers.sol#L650

Vulnerability details

Impact

Detailed description of the impact of this finding.

If a gobbler is not yet revealed and is used to mint a legendary gobbler then its potential emissionMultiple will not be accounted on the final emissionMultiple of the legendary gobbler LoC 439

Proof of Concept

Provide direct links to all referenced code in GitHub. Add screenshots, logs, or any other relevant proof that illustrates the concept.

The emissionMultiple of a gobbler is set during the reveal phase LoC 650

For example if a user uses a not revealed gobbler on the mintLegendaryGobbler(gobblerIds) function the potential emissionMultiple of this gobbler will not be accounted. Therefore, reducing the potential goo balance of the user.

Tools Used

Manual review

Recommended Mitigation Steps

Only allow revealed gobblers to be used for minting a legendary gobbler, for example adding a require( getGobblerData[id].emissionMultiple != 0 )

@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 Sep 26, 2022
code423n4 added a commit that referenced this issue Sep 26, 2022
@Shungy
Copy link
Member

Shungy commented Sep 28, 2022

Duplicate: #363

@GalloDaSballo GalloDaSballo added the duplicate This issue or pull request already exists label Sep 29, 2022
@GalloDaSballo
Copy link
Collaborator

#254

@GalloDaSballo GalloDaSballo added QA (Quality Assurance) Assets are not at risk. State handling, function incorrect as to spec, issues with clarity, syntax and removed 2 (Med Risk) Assets not at direct risk, but function/availability of the protocol could be impacted or leak value labels Oct 11, 2022
@GalloDaSballo
Copy link
Collaborator

L

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working duplicate This issue or pull request already exists QA (Quality Assurance) Assets are not at risk. State handling, function incorrect as to spec, issues with clarity, syntax
Projects
None yet
Development

No branches or pull requests

3 participants