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 was archived by the owner on Aug 3, 2025. It is now read-only.
Attacker who is not the winner can claimBid() of the winner.
Summary
insertSortedBid function depends on both sellCouponAmount and buyReserveAmount to determine bid placement in the auction. There is no check on the sellCouponAmount and buyReserveAmount to determine the highest bid. This can lead to uncertainty in the highest bid.
Root Cause
The root cause is the insertSortedBid where the highest bid is sorted there
Internal Pre-conditions
No response
External Pre-conditions
No response
Attack Path
Attacker can submit 10 ETH to place a bid
A user place the highest bid of 55 ETH
User calls the claimBid() first
Impact
No matter who placed the highest bid, anyone with a low bid can call claimBid and get the bid reward that is meant for the highest bidder(winner)