Submission Details
Impact:
Likelihood:
Unsafe `ERC721::_mint()`
Description: The contract calls '_mint(msg.sender, tokenId)' rather than '_safeMint', allowing tokens to be sent to contracts that don't implement 'onERC721Received'.
Impact: NFTs can be irrecoverably locked in non-compliant contracts.
Recommended Mitigation: Use the safe variant:
_safeMint(msg.sender, tokenId)
Updates
Appeal created
bube 4 months ago
Submission Judgement Published Reason: Non-acceptable severity
Assigned finding tags:
[Invalid] Use of `_mint` istead of `_safeMint`
The `fulfillMintRequest` function is external and anyone can call it. If the protocol uses `_safeMint` instead of `_mint`, this introduces a reentrancy risk. It is better to use `_mint` and the caller is responsible for being able to obtain the token.
Rewards breakdown
nSLOC
236This contest has a flat reward structure with the following payouts:
100 EXP
20 EXP
2 EXP
Live
The contest is live. Earn rewards by submitting a finding.
Appeals
This is your time to appeal against judgements on your submissions.
Appeals Review
Appeals are being carefully reviewed by our judges.