CVE-2024-37154 json
Evmos allows unvested token delegations
published 2y ago modified 4mo ago also EUVD-2024-1962 , GHSA-7hrh-v6wp-53vw , GO-2024-2904
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 32%
- public exploits
- 0
- none known
Summary
Evmos is the Ethereum Virtual Machine (EVM) Hub on the Cosmos Network. Users are able to delegate tokens that have not yet been vested. This affects employees and grantees who have funds managed via `ClawbackVestingAccount`. This affects 18.1.0 and earlier.
Is CVE-2024-37154 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/evmos/evmos/v18 | <=18.1.0 all versions |
no fix listed |
| go | github.com/evmos/evmos/v17 | <=17.0.1 all versions |
no fix listed |
| go | github.com/evmos/evmos/v16 | <=16.0.4 all versions |
no fix listed |
| go | github.com/evmos/evmos/v15 | <=15.0.0 all versions |
no fix listed |
| go | github.com/evmos/evmos/v14 | <=14.1.0 all versions |
no fix listed |
| go | github.com/evmos/evmos/v13 | <=13.0.2 all versions |
no fix listed |
| go | github.com/evmos/evmos/v12 | <=12.1.6 all versions |
no fix listed |
| go | github.com/evmos/evmos/v11 | <=11.0.2 all versions |
no fix listed |
| go | github.com/evmos/evmos/v10 | <=10.0.1 all versions |
no fix listed |
| go | github.com/evmos/evmos/v9 | <=9.1.0 all versions |
no fix listed |
| go | github.com/evmos/evmos/v8 | <=8.2.3 all versions |
no fix listed |
| go | github.com/evmos/evmos/v7 | <=7.0.0 all versions |
no fix listed |
| go | github.com/evmos/evmos/v6 | <=6.0.4 all versions |
no fix listed |
| go | github.com/evmos/evmos | all versions |
no fix listed |
| go | github.com/evmos/evmos/v2 | all versions |
no fix listed |
| go | github.com/evmos/evmos/v3 | all versions |
no fix listed |
| go | github.com/evmos/evmos/v4 | all versions |
no fix listed |
| go | github.com/evmos/evmos/v5 | all versions |
no fix listed |
Affected products
- evmos evmos
Classification
References
-
github.com
/evmos/evmos/security/advisories/GHSA-7hrh-v6wp-53vw
web, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2024-37154
advisory
-
github.com
/evmos/evmos
package
-
pkg.go.dev
/vuln/GO-2024-2904
web
Sources
- CVE List CVE-2024-37154
- GitHub Advisory GHSA-7hrh-v6wp-53vw
- NVD CVE-2024-37154
- OSV GO-2024-2904
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.