Potential DoS in SpiceAuction::bid
can deny bidders from placing bids
Since recipient address for any Spice token bid can be found by calling SpiceAuction::getAuctionConfig
function, malicious users can also send bidToken to the recipient address without going through the SpiceAuction::bid
function.
As a result of the strict statement in SpiceAuction::bid
found here
https://github.com/TempleDAO/temple/blob/c94bffdddb57990a71b41eeadbe78a1d49375b4c/protocol/contracts/templegold/SpiceAuction.sol#L197-L199
Bidders can be denied the opportunity to bid if malicious entities randomly and frequently send any amounts of bid tokens directly to the recipient address without calling SpiceAuction::bid
in between bidders calling SpiceAuction::bid
.
Manual Review
Perhaps use depositors
mapping for accounting purposes and exclude the token amount checks. So each bidder can see their total bid amounts, while you don't have to check for fee-on-transfer tokens, like in DaiGoldAuction::bid
.
Also consider that in DaiGoldAuction
, though DAI is believed to be the primary bid token, however, any bid token can be set by DaiGoldAuction::setBidToken
.Yet the DaiGoldAuction::bid
does not check for fee-on-transfer tokens.
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.