CVE-2024-32873 is a low-severity (CVSS 3.5) CWE-682 vulnerability in github.com/evmos/evmos/v17. A fix is available for github.com/evmos/evmos/v17 — see the affected versions and patch details below.
evmos allows transferring unvested tokens after delegations
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-32873.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2024-32873 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/evmos/evmos/v17🐹github.com/evmos/evmos/v16🐹github.com/evmos/evmos/v15🐹github.com/evmos/evmos/v14🐹github.com/evmos/evmos/v13🐹github.com/evmos/evmos/v12🐹github.com/evmos/evmos/v11🐹github.com/evmos/evmos/v10+4 moreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Impact
This advisory has been created to address the following vulnerabilities found in the Evmos codebase and affecting vesting accounts.
Wrong spendable balance computation
The spendable balance is not updated properly when delegating vested tokens. The following example help in describing the issue:
- Given a clawback vesting account with a starting
15Mvesting schedule. The initial spendable balance is0. - Time passes and
5Mare vested. The spendable balance is now5M. - The account delegate
5M. The spendable balance should be0, but returns5M - The account can send
5Mto another account.
The issue allowed a clawback vesting account to anticipate the release of unvested tokens.
Missing precompile checks
Preliminary checks on actions computed by the clawback vesting accounts are performed in the ante handler. Evmos core, implements two different ante handlers: one for Cosmos transactions and one for Ethereum transactions. Checks performed on the two implementation are different.
The vulnerability discovered allowed a clawback account to bypass Cosmos ante handler checks by sending an Ethereum transaction targeting a precompile used to interact with a Cosmos SDK module.
Missing create validator check
This vulnerability allowed a user to create a validator using vested tokens to deposit the self-bond.
Patches
- The spendable balance function has been fixed correcting the
TrackDelegationfunction. - The checks for the staking module, for the delegation and the create validator, has been moved into the
MsgServerof a wrapper around the Cosmos SDK staking module.
The issues have been patched in versions >=V18.0.0.
References
For more information
If you have any questions or comments about this advisory:
Reach out to the Core Team in Discord Open a discussion in evmos/evmos Email us at [email protected] for security questions
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/evmos/evmos/v17 | all versions | 18.0.0go get github.com/evmos/evmos/v17@v18.0.0 |
| 🐹Go | github.com/evmos/evmos/v16 | all versions | 18.0.0go get github.com/evmos/evmos/v16@v18.0.0 |
| 🐹Go | github.com/evmos/evmos/v15 | all versions | 18.0.0go get github.com/evmos/evmos/v15@v18.0.0 |
| 🐹Go | github.com/evmos/evmos/v14 | all versions | 18.0.0go get github.com/evmos/evmos/v14@v18.0.0 |
| 🐹Go | github.com/evmos/evmos/v13 | all versions | 18.0.0go get github.com/evmos/evmos/v13@v18.0.0 |
| 🐹Go | github.com/evmos/evmos/v12 | all versions | 18.0.0go get github.com/evmos/evmos/v12@v18.0.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/evmos/evmos/v17, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/evmos/evmos/v17 to 18.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-32873 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-32873 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2024-32873. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2024-32873 in your dependencies?
O3 Security finds CVE-2024-32873 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.