Evmos up to 18.x contract.CallerAddress authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Evmos up to 18.x. It has been declared as critical. Affected by this vulnerability is an unknown functionality. The manipulation of the argument contract.CallerAddress results in authorization. This vulnerability is reported as CVE-2024-39696. The attack can be launched remotely. No exploit exists. It is recommended to upgrade the affected component.
Details
A vulnerability was found in Evmos up to 18.x. It has been classified as critical. Affected is some unknown processing. The manipulation of the argument contract.CallerAddress with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-863. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
Evmos is a decentralized Ethereum Virtual Machine chain on the Cosmos Network. Prior to version 19.0.0, a user can create a vesting account with a 3rd party account (EOA or contract) as funder. Then, this user can create an authorization for the contract.CallerAddress, this is the authorization checked in the code. But the funds are taken from the funder address provided in the message. Consequently, the user can fund a vesting account with a 3rd party account without its permission. The funder address can be any address, so this vulnerability can be used to drain all the accounts in the chain. The issue has been patched in version 19.0.0.
The advisory is available at github.com. This vulnerability is traded as CVE-2024-39696 since 06/27/2024. The exploitability is told to be easy. It is possible to launch the attack remotely. Technical details are known, but there is no available exploit.
Upgrading to version 19.0.0 eliminates this vulnerability. Applying the patch 0a620e176617a835ac697eea494afea09185dfaf is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
License
Website
- Product: https://github.com/evmos/evmos/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.4
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 8.8
CNA Vector (GitHub_M): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-863 / CWE-285 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Evmos 19.0.0
Patch: 0a620e176617a835ac697eea494afea09185dfaf
Timeline
06/27/2024 🔍07/05/2024 🔍
07/05/2024 🔍
07/09/2024 🔍
Sources
Product: github.comAdvisory: GHSA-q6hg-6m9x-5g9c
Status: Confirmed
CVE: CVE-2024-39696 (🔍)
GCVE (CVE): GCVE-0-2024-39696
GCVE (VulDB): GCVE-100-270402
Entry
Created: 07/05/2024 22:09Updated: 07/09/2024 04:15
Changes: 07/05/2024 22:09 (65), 07/09/2024 04:15 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.