GHSA-m99c-q26r-m7m7: Evmos vulnerable to unauthorized account creation with vesting module
Impact What kind of vulnerability is it? Who is impacted? Using the vesting module, a malicious attacker can create a new vesting account at a given address, before a contract is created on that address. Addresses of smart contracts deployed to the EVM are deterministic. Therefore, it would be possible for an attacker to front-run a contract creation and create a vesting account at that address.
Published Apr 17, 2024 · Updated Jun 10, 2024
Affected packages
github.com/evmos/evmos/v13/x/vesting
- Ecosystem
- Go
- Affected
- <= 13.0.2
- Fixed in
- No patched version yet
- Check
go list -m github.com/evmos/evmos/v13/x/vesting
github.com/evmos/evmos/v13
- Ecosystem
- Go
- Affected
- <= 13.0.2
- Fixed in
- No patched version yet
- Check
go list -m github.com/evmos/evmos/v13
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
_What kind of vulnerability is it? Who is impacted?_
Using the vesting module, a malicious attacker can create a new vesting account at a given address, before a contract is created on that address.
Addresses of smart contracts deployed to the EVM are deterministic. Therefore, it would be possible for an attacker to front-run a contract creation and create a vesting account at that address. When an address has been initialized without any contract code deployed to it, it will not be possible to upload any afterwards. In the described attack, this would mean that a malicious actor could prevent smart contracts from being deployed correctly.
In order to remediate this, an alternative user flow is being implemented for the vesting module:
- only the account receiving the vesting funds will be able to create such an account by calling the
CreateClawbackVestingAccountmethod and defining a funder address - vesting and lockup periods can then be created by that funder address using
FundClawbackAccount
Patches
_Has the problem been patched? What versions should users upgrade to?_
Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
References
_Are there any links users can visit to find out more?_
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
