CVE-2024-37153

Contract balance not updating correctly after interchain transaction

// This function does not reduce the contract balance correctly but liquid stakes correctly 
function transfer(
        string memory sourcePort,
        string memory sourceChannel,
        string memory denom,
        uint256 amount,
        string memory receiver,
        string memory evmosReceiver
    ) external returns (uint64 nextSequence) {
        counter += 1; # Only happens when there is a local state update together with an ICS20 Transfer
        Height memory timeoutHeight =  Height(100, 100);
        string memory memo = buildLiquidStakeMemo(receiver, evmosReceiver);
        return ICS20_CONTRACT.transfer(
            sourcePort, 
            sourceChannel,
            denom,
            amount,
            address(this), # this is the sender address which is the contract
            receiver,
            timeoutHeight,
            0,
            memo
        );
    }

This is in essence the "infinite money glitch" allowing contracts to double the supply of Evmos after each transaction.

CVE-2024-37153 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (18.1.0); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

The issue has been patched in versions >=V18.1.0.

1. What is CVE-2024-37153? CVE-2024-37153 is a high-severity security vulnerability in github.com/evmos/evmos/v18 (go), affecting versions <= 18.0.0. It is fixed in 18.1.0.
2. How severe is CVE-2024-37153? CVE-2024-37153 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2024-37153?
   • github.com/evmos/evmos/v18 (go) (versions <= 18.0.0)
   • github.com/evmos/evmos/v17 (go) (versions <= 17.0.1)
   • github.com/evmos/evmos/v16 (go) (versions <= 16.0.4)
   • github.com/evmos/evmos/v15 (go) (versions <= 15.0.0)
   • github.com/evmos/evmos/v14 (go) (versions <= 14.1.0)
   • github.com/evmos/evmos/v13 (go) (versions <= 13.0.2)
   • github.com/evmos/evmos/v12 (go) (versions <= 12.1.6)
   • github.com/evmos/evmos/v11 (go) (versions <= 11.0.2)
   • github.com/evmos/evmos/v10 (go) (versions <= 10.0.1)
   • github.com/evmos/evmos/v9 (go) (versions <= 9.1.0)
   • github.com/evmos/evmos/v8 (go) (versions <= 8.2.3)
   • github.com/evmos/evmos/v7 (go) (versions <= 7.0.0)
   • github.com/evmos/evmos/v6 (go) (versions <= 6.0.4)
4. Is there a fix for CVE-2024-37153? Yes. CVE-2024-37153 is fixed in 18.1.0. Upgrade to this version or later.
5. Is CVE-2024-37153 exploitable, and should I be worried? Whether CVE-2024-37153 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-37153 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-37153?
   • Upgrade github.com/evmos/evmos/v18 to 18.1.0 or later
   • Upgrade github.com/evmos/evmos/v17 to 18.1.0 or later
   • Upgrade github.com/evmos/evmos/v16 to 18.1.0 or later
   • Upgrade github.com/evmos/evmos/v15 to 18.1.0 or later
   • Upgrade github.com/evmos/evmos/v14 to 18.1.0 or later
   • Upgrade github.com/evmos/evmos/v13 to 18.1.0 or later
   • Upgrade github.com/evmos/evmos/v12 to 18.1.0 or later
   • Upgrade github.com/evmos/evmos/v11 to 18.1.0 or later
   • Upgrade github.com/evmos/evmos/v10 to 18.1.0 or later
   • Upgrade github.com/evmos/evmos/v9 to 18.1.0 or later
   • Upgrade github.com/evmos/evmos/v8 to 18.1.0 or later
   • Upgrade github.com/evmos/evmos/v7 to 18.1.0 or later
   • Upgrade github.com/evmos/evmos/v6 to 18.1.0 or later

Other vulnerabilities in github.com/evmos/evmos/v18