Submitted by Limbooo, also found by ahmedaghadi, pontifex, Evo, MiniGlome, favelanky, Infect3d, ArmedGoose, AM, SpicyMeatball, 0xleadwizard, HChang26, TheSchnilch, Jorgect, and 0xabhay
Users withdrawals will be prevented from success and an attacker can keep it up without a cost by using a fake vault and a fake token.
There is a mechanisms for a flash loan protection that saves the current block number in a mapping of dNft token id; and then prevents it from withdrawing at the same block number. As we can see in the VaultManagerV2::deposit() function, this can be called by anyone with a valid dNft id:
The attacker can use this to prevent any withdrawals in the current block, since it will be checked whenever an owner of dNft token try to withdraw:
Foundry
Consider limiting anyone with any token vaults to update idToBlockOfLastDeposit. One of these mitigations can be used:
Invalid Validation
Koolex (judge) increased severity to High
shafu0x (DYAD) confirmed
