Galactix Zone v2

A reentrancy attack can occur when the contract creates a function that makes an external call to another untrusted contract before resolving any effects. If the attacker can control the untrusted contract, they can make a recursive call back to the original function, repeating interactions that would have otherwise not run after the external call resolved the effects. *This finding is considered minor because the state variable is only incremented or decremented. So, the effect of out-of-order increments may be unobservable after transaction. However, the reentrancy vulnerability may still cause other issues in the middle of transaction.* ### External call(s) ```solidity=148 antisnipe.assureCanTransfer(msg.sender, from, to, amount); ``` ### State variables written after the call(s) ```solidity=183 _balances[from] -= (ownerTax + commonTax); ``` ```solidity=188 _balances[taxRecipient] += commonTax; ``` ```solidity=196 _balances[taxRecipient] += ownerTax; ``` *Note: Only a sample of 3 assignments (out of 4) are shown above.*

The smart contract contains one or more state changes related to arithmetic operations that do not emit events to communicate the changes outside the blockchain, which can lead to difficulties in tracking or verifying these changes and may affect the contract's transparency and auditability. ```solidity=293 if (_isLPPool) { success = liquidityPoolAddresses.add(_lpPoolAddress); } else { success = liquidityPoolAddresses.remove(_lpPoolAddress); } if (!success) { revert('Address pool status is already set to this value.'); } ``` --- ```solidity=362 antisnipeDisable = true; ``` --- ```solidity=366 antisnipe = IAntisnipe(addr); ``` --- ```solidity=381 commonTaxRate = _newTaxRate; ``` --- ```solidity=386 ownerTaxRate = _newTaxRate; ```

The cited address input is missing a check that it is not `address(0)`.