GHSA-m99c-q26r-m7m7 Evmos vulnerable to unauthorized account creation with vesting module
Attackers can front-run contract deployments by creating vesting accounts at deterministic addresses, preventing smart contract uploads.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is GHSA-m99c-q26r-m7m7?
GHSA-m99c-q26r-m7m7 is a vulnerability in github.com/evmos/evmos, published on 17 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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?
Which versions are affected by GHSA-m99c-q26r-m7m7?
17 open source packages ship an affected version, including github.com/evmos/evmos/v13, github.com/evmos/evmos and github.com/evmos/evmos/v10.
| Package | Affected | Fixed in |
|---|---|---|
github.com/evmos/evmos/v13 Go | All versions | None |
github.com/evmos/evmos/v13 Go | All versions to 13.0.2 | None |
github.com/evmos/evmos/v13 Go | All versions to 13.0.2 | None |
github.com/evmos/evmos Go | All versions | None |
github.com/evmos/evmos/v10 Go | All versions | None |
github.com/evmos/evmos/v11 Go | All versions | None |
11 more packages
github.com/evmos/evmos/v12 Go | All versions | None |
github.com/evmos/evmos/v13/x/vesting Go | All versions to 13.0.2 | None |
github.com/evmos/evmos/v13/x/vesting Go | All versions to 13.0.2 | None |
github.com/evmos/evmos/v2 Go | All versions | None |
github.com/evmos/evmos/v3 Go | All versions | None |
github.com/evmos/evmos/v4 Go | All versions | None |
github.com/evmos/evmos/v5 Go | All versions | None |
github.com/evmos/evmos/v6 Go | All versions | None |
github.com/evmos/evmos/v7 Go | All versions | None |
github.com/evmos/evmos/v8 Go | All versions | None |
github.com/evmos/evmos/v9 Go | All versions | None |
How do I fix GHSA-m99c-q26r-m7m7?
No fix has been published for GHSA-m99c-q26r-m7m7 yet. Limit exposure of the affected software until one is available.
Is GHSA-m99c-q26r-m7m7 being exploited?
There is no known exploitation of GHSA-m99c-q26r-m7m7 in the wild and no public exploit code.
Sources
Also known as GO-2024-2731.