The protocol exposes functionality to split an NFT to ERC20s, which we call pieces. Each NFT can later be claimed back if a user decides to collect all the pieces and exchange them back for the NFT.
The vulnerable part is that the claimNft
function will only take nftAddress
as a parameter. This means that the user can't specify the tokenId
, which he'd like to claim. Considering that the nftToErc20Info
storage variable is never cleared of the claimed NFTs, this would cause previously divided NFTs with the same address, but different tokenIds
to be forever stuck in the protocol.
NFTs with the same address, but different tokenIds
will be forever stuck in the protocol.
Manual Review
Add the parameter of tokenId
to claimNft
function.
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.