Skip to content
Fencer Intel
low 3.5

CVE-2024-32873 json

evmos allows transferring unvested tokens after delegations

published 2y ago modified 2mo ago also CVE-2024-37158 , CVE-2024-37159 , EUVD-2024-2129 , GHSA-pxv8-qhrh-jc7v , GO-2024-2891 , GO-2024-2926 , GO-2024-2927

cvss
3.5
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. The spendable balance is not updated properly when delegating vested tokens. The issue allows a clawback vesting account to anticipate the release of unvested tokens. This vulnerability is fixed in 18.0.0.

Patch / fix

  • go github.com/evmos/evmos/v17 18.0.0
  • go github.com/evmos/evmos/v16 18.0.0
  • go github.com/evmos/evmos/v15 18.0.0
  • go github.com/evmos/evmos/v14 18.0.0
  • go github.com/evmos/evmos/v13 18.0.0
  • go github.com/evmos/evmos/v12 18.0.0
  • go github.com/evmos/evmos/v11 18.0.0
  • go github.com/evmos/evmos/v10 18.0.0
  • go github.com/evmos/evmos/v9 18.0.0
  • go github.com/evmos/evmos/v8 18.0.0
  • go github.com/evmos/evmos/v7 18.0.0
  • go github.com/evmos/evmos/v6 18.0.0
  • go github.com/evmos/evmos/v18 18.0.0
  • evmos evmos 18.0.0

Is CVE-2024-32873 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 Fencer

CISA SSVC

Exploitation
none
Automatable
no
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 3.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L
GitHub 3.1 3.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L
NVD 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
go github.com/evmos/evmos/v17
<18.0.0
all versions
18.0.0
go github.com/evmos/evmos/v16
<18.0.0
all versions
18.0.0
go github.com/evmos/evmos/v15
<18.0.0
all versions
18.0.0
go github.com/evmos/evmos/v14
<18.0.0
all versions
18.0.0
go github.com/evmos/evmos/v13
<18.0.0
all versions
18.0.0
go github.com/evmos/evmos/v12
<18.0.0
all versions
18.0.0
go github.com/evmos/evmos/v11
<18.0.0
all versions
18.0.0
go github.com/evmos/evmos/v10
<18.0.0
all versions
18.0.0
go github.com/evmos/evmos/v9
<18.0.0
all versions
18.0.0
go github.com/evmos/evmos/v8
<18.0.0
all versions
18.0.0
go github.com/evmos/evmos/v7
<18.0.0
all versions
18.0.0
go github.com/evmos/evmos/v6
<18.0.0
all versions
18.0.0
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
go github.com/evmos/evmos/v18
<18.0.0
18.0.0

Affected products

  • evmos evmos

Classification

Weakness

References

Sources

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.