CVE-2024-32644
📋 TL;DR
This critical vulnerability in Evmos blockchain allows attackers to mint arbitrary tokens by exploiting a state synchronization issue between Cosmos SDK and EVM states. The non-atomic transaction execution enables creative smart contract interactions that could drain funds. All Evmos nodes running vulnerable versions are affected.
💻 Affected Systems
- Evmos blockchain
📦 What is this software?
Evmos by Evmos
⚠️ Risk & Real-World Impact
Worst Case
Complete draining of funds from vulnerable contracts and protocols built on Evmos through arbitrary token minting and manipulation.
Likely Case
Targeted exploitation of specific vulnerable smart contracts to mint tokens or manipulate DeFi protocols for financial gain.
If Mitigated
Limited impact if contracts have additional safeguards, but core vulnerability remains exploitable.
🎯 Exploit Status
Exploitation requires smart contract interaction knowledge but no authentication. Public details suggest sophisticated attackers could weaponize.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: V17.0.0 and later
Vendor Advisory: https://github.com/evmos/evmos/security/advisories/GHSA-3fp5-2xwh-fxm6
Restart Required: Yes
Instructions:
1. Stop Evmos node. 2. Backup configuration and data. 3. Update to V17.0.0 or later. 4. Restart node with updated binary.
🔧 Temporary Workarounds
No effective workarounds
allThis is a core blockchain protocol vulnerability requiring patching.
🧯 If You Can't Patch
- Monitor for suspicious token minting transactions and contract interactions
- Consider temporarily pausing vulnerable smart contracts or limiting interactions
🔍 How to Verify
Check if Vulnerable:
Check Evmos version: evmosd version
Check Version:
evmosd version
Verify Fix Applied:
Confirm version is V17.0.0 or later: evmosd version
📡 Detection & Monitoring
Log Indicators:
- Unexpected token minting events
- Unusual smart contract state changes
- Failed state synchronization errors
Network Indicators:
- Abnormal transaction patterns involving state manipulation
- Multiple contract calls in single transaction with state changes
SIEM Query:
transaction_logs WHERE contract_interaction_count > threshold AND token_minting_events > 0
🔗 References
- https://github.com/evmos/evmos/blob/b196a522ba4951890b40992e9f97aa610f8b5f9c/x/evm/statedb/statedb.go#L460-L465
- https://github.com/evmos/evmos/commit/08982b5ee726b97bc50eaf58d1914829648b6a5f
- https://github.com/evmos/evmos/security/advisories/GHSA-3fp5-2xwh-fxm6
- https://github.com/evmos/evmos/blob/b196a522ba4951890b40992e9f97aa610f8b5f9c/x/evm/statedb/statedb.go#L460-L465
- https://github.com/evmos/evmos/commit/08982b5ee726b97bc50eaf58d1914829648b6a5f
- https://github.com/evmos/evmos/security/advisories/GHSA-3fp5-2xwh-fxm6