CVE-2024-39696: Evmos vulnerable to exploit of smart contract account and vesting
Summary This advisory board aims to describe two vulnerabilities found in the Evmos codebase: - Authorization check on the fundVestingAccount: unauthorized spend of funds. Details Authorization check on the fundVestingAccount With the current implementation, a user can create a vesting account with a 3rd party account (EOA or contract) as funder.
Published Jul 10, 2024 · Updated Aug 9, 2024
Affected packages
github.com/evmos/evmos/v18
- Ecosystem
- Go
- Affected
- <= 18.0.1
- Fixed in
- 19.0.0
- Check
go list -m github.com/evmos/evmos/v18
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
This advisory board aims to describe two vulnerabilities found in the Evmos codebase:
- _Authorization check on the fundVestingAccount_: unauthorized spend of funds.
Details
Authorization check on the fundVestingAccount
With the current implementation, a user can create a vesting account with a 3rd party account (EOA or contract) as funder. Then, this user can create an authorization for the contract.CallerAddress, this is the authorization checked in the code. But the funds are taken from the funder address provided in the message. Consequently, the user can fund a vesting account with a 3rd party account without its permission. The funder address can be any address, so this vulnerability can be used to drain all the accounts in the chain.
Severity
Based on ImmuneFi Severity Classification System the severity was evaluated to Critical since the attack could have lead to direct loss of funds.
Patches
The issue has been patched in versions >=V19.0.0
Credited to GAtom22.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
