Dangerous require statement in BidBeastsNFTMarket:placeBid prevents any user from placing a bid 15 minutes after the first bidder places a bid.
When a seller lists an NFT, the Listing.auctionEnd is set to 0 until a first bidder places a bid on the nft, and if the bid places is less thank the Listing.buyNowPrice, the Bid struct is updated with the current bid, and Listing.auctionEnd is set to 15 minutes i.e S_AUCTION_EXTENSION_DURATION. However, because of the below require statement, any user that attempts to bid after the first 15 minutes has passed is blocked from making a bid.
This Implies that only the first bidder will be acknowledged and will be sold the NFT
Likelihood:
Reason 1: This happens if no other user place a bid on the NFT, 15 minutes after the auction starts.
Impact:
Severe disruption of functionality as it prevents users from placing a bid
Potential loss of funds as only first bid is acknowledged and users are prevented from placing a higher bid.
A user places a bid on an NFT and starts the auction
Another user tries to place a bid after the first 15 minutes, but is blocked from bidding.
Set the Listing.auctionEnd to 3 days after the first bid is placed outlined by the docs.
In BidBeastsNFTMarket:placeBid
Documentation for BidBeasts Marketplace is incomplete or inaccurate, potentially leading to misconfigurations or security misunderstandings.
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.