You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 5, 2023. It is now read-only.
sherlock-admin opened this issue
Apr 30, 2023
· 0 comments
Labels
DuplicateA valid issue that is a duplicate of an issue with `Has Duplicates` labelHighA valid High severity issueRewardA payout will be made for this issue
No slippage control when closing position in ConvexSpell
Summary
No slippage control when closing position in ConvexSpell
Vulnerability Detail
No slippage control when closing position in ConvexSpell, specifically remove_liquidity_one_coin can output almost 0 tokens, if the attacker sandwich attack so the desired is very very expensive (low liquidity in the underlying pool).
Impact
Attacker can sandwich attack users when they want to close position in ConvexSpell, leading to users getting nothing out (0 tokens).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
DuplicateA valid issue that is a duplicate of an issue with `Has Duplicates` labelHighA valid High severity issueRewardA payout will be made for this issue
n1punp
high
No slippage control when closing position in ConvexSpell
Summary
No slippage control when closing position in ConvexSpell
Vulnerability Detail
No slippage control when closing position in ConvexSpell, specifically
remove_liquidity_one_coin
can output almost 0 tokens, if the attacker sandwich attack so the desired is very very expensive (low liquidity in the underlying pool).Impact
Attacker can sandwich attack users when they want to close position in ConvexSpell, leading to users getting nothing out (0 tokens).
Code Snippet
https://github.com/sherlock-audit/2023-04-blueberry/blob/main/blueberry-core/contracts/spell/ConvexSpell.sol#L147-L230
Tool used
Manual Review
Recommendation
Duplicate of #121
The text was updated successfully, but these errors were encountered: