Validator creation via unchecked vested self-bond
Published Jun 17, 2024 · Updated Aug 2, 2024
Improper authorization in Evmos before 18.0.0 allows remote authenticated users to create validators with vested self-bond tokens. The staking create-validator path accepted a vesting account's self-bond without enforcing vesting checks in the staking MsgServer. Exploitation requires control of a funded clawback vesting account and changes staking state by committing still-vested tokens to a validator.
Summary
What happened
Improper authorization in Evmos before 18.0.0 allows remote authenticated users to create validators with vested self-bond tokens. The staking create-validator path accepted a vesting account's self-bond without enforcing vesting checks in the staking MsgServer. Exploitation requires control of a funded clawback vesting account and changes staking state by committing still-vested tokens to a validator.
The record
- CVE
- CVE-2024-37159
- Published
- Jun 17, 2024
- Updated
- Aug 2, 2024
- Vendor
- Evmos
- Product
- Evmos
- Classifications
- CWE-285
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 17, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 18.0.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo