Unintentionally causing users to lose their bond #105
Labels
2 (Med Risk)
Assets not at direct risk, but function/availability of the protocol could be impacted or leak value
bug
Warden finding
duplicate
Another warden found this issue
sponsor confirmed
Sponsor agrees this is a problem and intends to fix it (OK to use w/ "disagree with severity")
Handle
itsmeSTYJ
Vulnerability details
Impact
Normally I would classify this as low but because of how widespread USDT is, I believe it is important to handle this case simply for USDT. USDT doesn't allow you to approve allowance unless you first set it to 0.
If your basket contains USDT initially and the publisher tries to publishNewIndex with USDT (regardless of weighting), any bonder that tries to settle the auction will always fail because
basket.setNewWeights
will always fail when it comes to approving max allowance for USDT.The publisher might not be malicious but the publisher not knowing about this is not an excuse for users losing their bond.
Recommended Mitigation Steps
The text was updated successfully, but these errors were encountered: