Evmos's contract balance not updating correctly after interchain transaction
cve-program · CVE-2024-37153
PublishedEvmos is the Ethereum Virtual Machine (EVM) Hub on the Cosmos Network. There is an issue with how to liquid stake using Safe which itself is a contract. The bug only appears when there is a local state change together with an ICS20 transfer in the same function and uses the contract's balance, that is using the contract address as the sender parameter in an ICS20 transfer using the ICS20 precompile. This is in essence the "infinite money glitch" allowing contracts to double the supply of Evmos after each transaction.The issue has been patched in versions >=V18.1.0.
Read the publisher's advisoryeuvd · EUVD-2024-2214
PublishedEvmos is the Ethereum Virtual Machine (EVM) Hub on the Cosmos Network. There is an issue with how to liquid stake using Safe which itself is a contract. The bug only appears when there is a local state change together with an ICS20 transfer in the same function and uses the contract's balance, that is using the contract address as the sender parameter in an ICS20 transfer using the ICS20 precompile. This is in essence the "infinite money glitch" allowing contracts to double the supply of Evmos after each transaction.The issue has been patched in versions >=V18.1.0.
Read the publisher's advisorynvd · CVE-2024-37153
PublishedEvmos is the Ethereum Virtual Machine (EVM) Hub on the Cosmos Network. There is an issue with how to liquid stake using Safe which itself is a contract. The bug only appears when there is a local state change together with an ICS20 transfer in the same function and uses the contract's balance, that is using the contract address as the sender parameter in an ICS20 transfer using the ICS20 precompile. This is in essence the "infinite money glitch" allowing contracts to double the supply of Evmos after each transaction.The issue has been patched in versions >=V18.1.0.
Read the publisher's advisoryosv · GHSA-xgr7-jgq3-mhmc
Published### Summary _Short summary of the problem. Make the impact and severity as clear as possible. For example: An unsafe deserialization vulnerability allows any unauthenticated user to execute arbitrary code on the server._ ### Details We discovered a bug walking through how to liquid stake using Safe which itself is a contract. The bug only appears when there is a local state change together with an ICS20 transfer in the same function and uses the contract's balance, that is using the contract address as the `sender` parameter in an ICS20 transfer using the ICS20 precompile ### Proof of Concept ```solidity // 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 ); } ``` ### Impact This is in essence the "infinite money glitch" allowing contracts to double the supply of Evmos after each transaction. ### Severity Based on [ImmuneFi Severity Classification System](https://immunefisupport.zendesk.com/hc/en-us/articles/13332717597585-Severity-Classification-System) the severity was evaluated to `Critical` since the attack could have lead to create new supply of EVMOS and therefore lead to Direct loss of funds's value. ### Patches The issue has been patched in versions >=V18.1.0. ## For more information If you have any questions or comments about this advisory: Reach out to the Core Team in [Discord](https://discord.gg/evmos) Open a discussion in [evmos/evmos](https://github.com/evmos/evmos/discussions) Email us at [[email protected]](mailto:[email protected]) for security questions
Read the publisher's advisoryosv · GO-2024-2903
PublishedContract balance not updating correctly after interchain transaction in github.com/evmos/evmos
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2024-37153 · CVE overview and exploitation status
cve-program · CVE-2024-37153
- https://github.com/evmos/evmos/security/advisories/GHSA-xgr7-jgq3-mhmc
- https://github.com/evmos/evmos/commit/478b7a62e7af57a70cf3a01126c7f5a89bee69d7
euvd · EUVD-2024-2214
- https://github.com/evmos/evmos/security/advisories/GHSA-xgr7-jgq3-mhmc
- https://github.com/evmos/evmos/commit/478b7a62e7af57a70cf3a01126c7f5a89bee69d7
nvd · CVE-2024-37153
- https://github.com/evmos/evmos/commit/478b7a62e7af57a70cf3a01126c7f5a89bee69d7
- https://github.com/evmos/evmos/security/advisories/GHSA-xgr7-jgq3-mhmc
osv · GHSA-xgr7-jgq3-mhmc
- https://github.com/evmos/evmos/security/advisories/GHSA-xgr7-jgq3-mhmc
- https://nvd.nist.gov/vuln/detail/CVE-2024-37153
- https://github.com/evmos/evmos/commit/478b7a62e7af57a70cf3a01126c7f5a89bee69d7
- https://github.com/evmos/evmos
- https://pkg.go.dev/vuln/GO-2024-2903
osv · GO-2024-2903
Related changes
Linked by CVE identifierNo related changes are available here.