StrategyManager.slashQueuedWithdrawal might not work as expected #338
Labels
bug
Something isn't working
downgraded by judge
Judge downgraded the risk level of this issue
grade-b
primary issue
Highest quality submission among a set of duplicates
Q-10
QA (Quality Assurance)
Assets are not at risk. State handling, function incorrect as to spec, issues with clarity, syntax
sponsor disputed
Sponsor cannot duplicate the issue, or otherwise disagrees this is an issue
Lines of code
https://github.com/code-423n4/2023-04-eigenlayer/blob/5e4872358cd2bda1936c29f460ece2308af4def6/src/contracts/core/StrategyManager.sol#L560-L578
Vulnerability details
Impact
Function StrategyManager.slashQueuedWithdrawal's param indicesToSkip is an array, according to the source code, the function can work only if the data stored in indicesToSkip is ascending order.
For example, if there are 15 strategies in queuedWithdrawal.strategies, and the StrategyManager needs to slash strategie 1, 3, 5, to make the slash success, he has to fill indicesToSkip with the indices in ascending order. as [1, 3, 5], otherwise he will fails
Proof of Concept
https://github.com/code-423n4/2023-04-eigenlayer/blob/5e4872358cd2bda1936c29f460ece2308af4def6/src/contracts/core/StrategyManager.sol#L560-L578
Tools Used
VS
Recommended Mitigation Steps
Assessed type
Error
The text was updated successfully, but these errors were encountered: