Submitted by HollaDieWaldfee, also found by __141345__ and 0xdeadbeef0x
https://github.com/code-423n4/2022-12-tigris/blob/496e1974ee3838be8759e7b4096dbee1b8795593/contracts/Lock.sol#L110 
https://github.com/code-423n4/2022-12-tigris/blob/496e1974ee3838be8759e7b4096dbee1b8795593/contracts/BondNFT.sol#L215
When calling Lock.claimGovFees, assets that are set to be not allowed or assets that dont have any shares yet in the BondNFT contract will cause a silent failure in BondNFT.distribute.
The funds from the GovNFT contract will get transferred into the Lock contract and then will be stuck there. They cannot be recovered.
VS Code
A naive solution would be to use revert instead of return in BondNFT.distribute such that funds are either transferred from GovNFT to Lock and then to BondNFT or not at all.
This however is an incomplete fix because if there is a single bad asset, rewards for the other assets cannot be distributed either.
Moreover functions like Lock.lock and Lock.release rely on Lock.claimGovFees to not revert.
So you might allow the owner to rescue stuck tokens from the Lock contract. Of course only allow rescuing the balance of the Lock contract minus the totalLocked of the asset in the Lock contract such that the locked amount cannot be rescued.
Alex the Entreprenerd (judge) commented:
TriHaz (Tigris Trade) confirmed and commented:
Alex the Entreprenerd (judge) commented:
GainsGoblin (Tigris Trade) resolved:
