The burn(uint256 _tokenId) function currently allows any external caller to burn any token, regardless of ownership or approval status:
Since the function does not verify that msg.sender is either the owner of the token or an approved operator, attackers can arbitrarily destroy NFTs belonging to other users. This undermines the integrity of the NFT collection and directly impacts holders.
Risk: High – trivial to exploit, does not require special privileges.
Impact: High – attackers can permanently destroy NFTs of other users.
Severity: High – immediate loss of assets with no recovery possible.
Victim owns NFT with tokenId = 1.
Attacker calls:
The contract executes _burn(TOKEN_ID) without checking permissions.
Victim’s NFT is permanently destroyed, even though they never approved or initiated the action.
Restrict the burn function to the token owner or an approved operator by adding an ownership check:
In the BidBeasts ERC721 implementation, the burn function is publicly accessible, allowing any external user to burn NFTs they do not own. This exposes all tokens to unauthorized destruction and results in permanent asset loss.
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.