First note that per the scope of the audit any and all possible ERC20s are to be considered, i.e.:
Now when there is a need to deploy an interchain token, the ERC20 identification data for the token are inquired and stored, for e.g.:
https://github.com/code-423n4/2024-08-axelar-network/blob/69c4f2c3fcefb1b8eb2129af9c3685a44ae5b6fe/interchain-token-service/contracts/InterchainTokenFactory.sol#L171-L210
This function is used to deploy a remote interchain token on a specified destination chain. However, the problem is that this function assumes all ERC20 names are stored as strings on chain; this is wrong and would then cause for the attempt at deploying these tokens remotely to always fail for tokens that have non-string metadata.
Tokens with non-string metadata cant get deployed on the ITS.
Check the metadata data type of added tokens.
