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
Can create minipool without staking #439
Labels
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
downgraded by judge
Judge downgraded the risk level of this issue
duplicate-569
partial-50
Incomplete articulation of vulnerability; eligible for partial credit only (50%)
Comments
code423n4
added
3 (High Risk)
Assets can be stolen/lost/compromised directly
bug
Something isn't working
labels
Jan 2, 2023
C4-Staff
added a commit
that referenced
this issue
Jan 6, 2023
Dup of #484 but without Front-run aspect, awarding half |
GalloDaSballo marked the issue as duplicate of #484 |
GalloDaSballo marked the issue as partial-50 |
c4-judge
added
the
partial-50
Incomplete articulation of vulnerability; eligible for partial credit only (50%)
label
Jan 10, 2023
GalloDaSballo marked the issue as duplicate of #569 |
c4-judge
added
duplicate-569
2 (Med Risk)
Assets not at direct risk, but function/availability of the protocol could be impacted or leak value
downgraded by judge
Judge downgraded the risk level of this issue
and removed
duplicate-484
3 (High Risk)
Assets can be stolen/lost/compromised directly
labels
Feb 3, 2023
GalloDaSballo changed the severity to 2 (Med Risk) |
c4-judge
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
Feb 9, 2023
GalloDaSballo changed the severity to QA (Quality Assurance) |
Simon-Busch
added
2 (Med Risk)
Assets not at direct risk, but function/availability of the protocol could be impacted or leak value
and removed
QA (Quality Assurance)
Assets are not at risk. State handling, function incorrect as to spec, issues with clarity, syntax
labels
Feb 9, 2023
Changed the severity back to M as requested by @GalloDaSballo |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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
downgraded by judge
Judge downgraded the risk level of this issue
duplicate-569
partial-50
Incomplete articulation of vulnerability; eligible for partial credit only (50%)
Lines of code
https://github.com/code-423n4/2022-12-gogopool/blob/aec9928d8bdce8a5a4efe45f54c39d4fc7313731/contracts/contract/MinipoolManager.sol#L442-L478
Vulnerability details
Impact
minipool can be created without staking AVAX with recreateMinipool(). recreateMinipool() function doesn't check if the owner withdrew or not.
Proof of Concept
I just added withdrawMinipoolFunds() to the original test.
Tools Used
Foundry
Recommended Mitigation Steps
recreateMinipool() needs check staking balance before increaseAVAXStake().
The text was updated successfully, but these errors were encountered: