Submitted by nemveer, also found by 0xBeirao, Hama, n33k, and Madalad
https://github.com/code-423n4/2023-08-goodentry/blob/71c0c0eca8af957202ccdbf5ce2f2a514ffe2e24/contracts/GeVault.sol#L271-L278 
https://github.com/code-423n4/2023-08-goodentry/blob/71c0c0eca8af957202ccdbf5ce2f2a514ffe2e24/contracts/GeVault.sol#L420-L424
In GeVault, while depositing tokens in the pool, liquidity tokens are minted to the users.
Calculation of liquidity tokens to mint uses balanceOf(address(this)) which makes it susceptible to first deposit share price manipulation attack.
deposit calls getTVL, which calls getTickBalance.
GeVault.deposit#L271-L278
GeVault.getTVL#L392-L398
GeVault.getTickBalance#L420-L424
Although there is a condition on line 281 that liquidity to be minted must be greater than 0, Users funds can be at risk.
When totalSupply is zero, an attacker can go ahead and execute following steps.
So, now 1 wei of share worths X underlying tokens.
Attacker wont have any problem making this X as big as possible. Because hell always be able to redeem it with 1 wei of share.
Impact
Burn some MINIMUM_LIQUIDITY during first deposit.
Keref (Judge) confirmed, but disagreed with severity and commented:
gzeon (Judge) decreased severity to Medium
