https://github.com/code-423n4/2024-02-althea-liquid-infrastructure/blob/bd6ee47162368e1999a0a5b8b17b701347cf9a7d/liquid-infrastructure/contracts/LiquidInfrastructureERC20.sol#L394C1-L403C6
https://github.com/code-423n4/2024-02-althea-liquid-infrastructure/blob/bd6ee47162368e1999a0a5b8b17b701347cf9a7d/liquid-infrastructure/contracts/LiquidInfrastructureERC20.sol#L413C1-L434C6
https://github.com/code-423n4/2024-02-althea-liquid-infrastructure/blob/bd6ee47162368e1999a0a5b8b17b701347cf9a7d/liquid-infrastructure/contracts/LiquidInfrastructureERC20.sol#L359C1-L386C6
Minor impact is that gas will be burned during zero amount transfers. Major impact is a DOS upon calling the withdrawFromManagedNFTs function after the NFT is released.
The addManagedNFT function allows the owner to add the LiquidInfrastructureNFTs to the list of managed NFTs, upon which the NFT is added to the list of the protocolss NFTs. The function and the constructor lacks sanity checks, which can cause that NFTs can be duplicated.
For the minor impact, upon calling the withdrawFromAllManagedNFTs/withdrawFromManagedNFTs function, the withdrawBalancesTo function is called in the LiquidInfrastructureNFT contract:
After the withdrawal from the first duplicate, the ERC20 balance is 0, so the withdrawals from the second/subsequent duplicates are skipped.
For the more major impact, first the releaseManagedNFT is called. This transfers the NFT, then deletes the NFT from the array of managedNFTs. However, due to the use of the break functionality, it doesnt have a loop through the entire array of NFTs, but rather stops at the first discovered NFT (I.E., the first duplicate), leaving the remaining duplicates in the managedNFTs array. 
Now, its important to note that the NFT transfer transfers the ownership to the other address, causing the LiquidInfrastructureERC20 contract to no longer be the token owner.
Upon calling withdrawFromAllManagedNFTs/withdrawFromManagedNFTs function, the withdrawBalancesTo function is called in the LiquidInfrastructureNFT contract. The withdrawBalancesTo function can only be called by the owner or an approved user. Hence, the LiquidInfrastructureERC20 contract will not be able to call this contract, thus dossing the NFT balance withdrawal process. 
This duplicate token can also not be removed by calling the releaseManagedNFT function, as the transferFrom function has to be called by either the owner or an approved user. 
Ultimately, this depends on the owners mistake, but can have serious effects in the protocol, so Id leave this up to the judge.
Consider adding checks for duplications, or removing the break functionality from the releaseManagedNFT function, to allow for full looping and full removal of all duplicates.
