https://github.com/code-423n4/2022-12-caviar/blob/main/src/Pair.sol#L359-L373
Position.sol contract has no Re-Entrancy protection in withdraw function
If the mint was initiated by a contract, then the contract is checked for its ability to receive ERC721 tokens. Without reentrancy guard, onERC721Received will allow an attacker controlled contract to call the mint again, which may not be desirable to some parties, like allowing minting more than allowed.
https://www.paradigm.xyz/2021/08/the-dangers-of-surprising-code
If withdraw is msg.sender contract, it can do re-entrancy by overriding onERC721Received function, it doesnt seem to be a serious problem since it conforms to check-effect-interaction pattern, but this is a clear re-entry due to access to other functions and pre-emit processing. is the entracy
Use Openzeppelin or Solmate Re-Entrancy pattern.
Here is a example of a re-entrancy guard
