In SmartVaultManagerV5.sol
, tokenURI()
does not check if the _tokenId
is valid NFT and violates EIP-721 specification
In SmartVaultManagerV5.sol
, tokenURI()
is used to get the tokenURI of input tokenId. The issue is that, it does not check whether the passed tokenId as input argument exists or not. This violates the ERC721-Metadata part standard.
SmartVaultManagerV5.sol
inherits the ERC721Upgradeable
in contract.
As seen below, it violates the EIP-721 standard tokenURI
implementation,
EIP-721 specfically states,
The issue is identified as Medium severity since the functionality breaks the EIP721 specification and there is no funds are at risk.
tokenURI() function implementation deviates from the ERC-721 standard. According to the standard, the tokenURI method must revert if a non-existent tokenId is passed. In SmartVaultManagerV5
contract, this requirement was overlooked, leading to a violation of the EIP-721 specification.
Manual review
Throw an error if the _tokenId
is not a valid NFT.
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.