Web3AITool

This issue deals with how the contract can lose 10% of its supply if the owner gets compromised.Scenario 1: Via early token unlock The releaseTime is checked to confirm it’s not zero but does not check to see if releaseTime is greater than contractCreatedTime.This means the claim function can be manipulated to dispense tokens much earlier than expected if the owner forgets to set releaseTime or uses a value too little.For small values of releaseTime (which could be zero before initialization) less than (contractCreatedTime + one quarter), quartersPassed can get greater than 10 and as such would make claimableQuarters to be equal to 10, thus allowing to withdraw all tokens allocated (10% of total supply) in the very first quarter. Scenario 2: Malicious/Compromised owner The erc20 withdraw function in the contract allows any address to be passed in, including the token’s contract address. If that happens, withdraw() would check for the ether balance of the contract (another low severity issue described below) and then transfer the available balance of the contract - 10% of the totalSupply - to the owner which could have been compromised. The tokens can then be sold on the open market without any restrictions.

The erc20 withdraw function checks for an ether balance in the contract using        require(address(this).balance > 0, 'Pre-Sale: Contract has no money'); instead of checking for the ERC20 token balance to be withdrawn.