In bridge.sol, the depostTokens() function does not implement a zero address check for the ownerL2 field. If a user provides a zero address for this field, this may result in the user's NFT being burned as it is sent to the zero address on starknet.
In bridge.sol, there is a check to ensure that the ownerL2 field provided is a valid staknet address. However, this check would still be passed even if a zero address is provided.
This could result in users unintentionally burning their NFT during the bridging process, if they pass in a zero address as the ownerL2 field. Thier NFT would be lost forever and irrecoverable.
Implement a check to ensure that zero address is not provided for the ownerL2 field.
Manual review
Please, do not suppose impacts, think about the real impact of the bug and check the CodeHawks documentation to confirm: https://docs.codehawks.com/hawks-auditors/how-to-determine-a-finding-validity A PoC always helps to understand the real impact possible.
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.