What is the CVSS score of CVE-2024-37158?

CVE-2024-37158 has a CVSS 3.1 base score of 8.1 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H. EPSS exploitation probability: 0.4%.

Is there a patch available for CVE-2024-37158?

Yes, a patch is available for CVE-2024-37158. Update the affected software to the latest version immediately.

Evmos CVE-2024-37158

HIGH

Insufficient Control Flow Management (CWE-691)

2024-06-17 security-advisories@github.com

Authentication Bypass Evmos

8.1

CVSS 3.1 · NVD

View

Vulnerability Assessment

Weakness	CWE CWE-691 ASVS 5.0 V15 - Secure Coding and Architecture Insufficient control flow management
Impact	CVSS score of 8.1 (HIGH). Attack characteristics: network attack vector, low complexity, low privileges required, no user interaction not required.
Exploit ScenarioDerived	This vulnerability can be exploited remotely over the network. Successful exploitation could compromise the high-severity affected system.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).

Patch available 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAI

Evmos is the Ethereum Virtual Machine (EVM) Hub on the Cosmos Network. Rated high severity (CVSS 8.1), this vulnerability is remotely exploitable, low attack complexity.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.

Affected Packages

go github.com/evmos/evmos no fix

go github.com/evmos/evmos/v10 fix: 18.0.0

go github.com/evmos/evmos/v11 fix: 18.0.0

go github.com/evmos/evmos/v12 fix: 18.0.0

go github.com/evmos/evmos/v13 fix: 18.0.0

go github.com/evmos/evmos/v14 fix: 18.0.0

go github.com/evmos/evmos/v15 fix: 18.0.0

go github.com/evmos/evmos/v16 fix: 18.0.0

go github.com/evmos/evmos/v17 fix: 18.0.0

go github.com/evmos/evmos/v18 fix: 18.0.0

go github.com/evmos/evmos/v2 no fix

go github.com/evmos/evmos/v3 no fix

go github.com/evmos/evmos/v4 no fix

go github.com/evmos/evmos/v5 no fix

go github.com/evmos/evmos/v6 fix: 18.0.0

go github.com/evmos/evmos/v7 fix: 18.0.0

go github.com/evmos/evmos/v8 fix: 18.0.0

go github.com/evmos/evmos/v9 fix: 18.0.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 18 packages in go

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

This vulnerability is classified under CWE-691. Evmos is the Ethereum Virtual Machine (EVM) Hub on the Cosmos Network. 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. This vulnerability is fixed in 18.0.0. Affected products include: Evmos.

Severity by source

NVD PRIMARY 8.1 HIGH

AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

High

DescriptionNVD

Evmos is the Ethereum Virtual Machine (EVM) Hub on the Cosmos Network. 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. This vulnerability is fixed in 18.0.0.

Threat Intelligence Overview

EPSS Score

0.4%

Top 65% exploitable

Data Quality

3 sources

Confidence: Low

NVD

CVE.org

EPSS

GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity HIGH

CISA KEV No

Public POC No

EPSS 0.4%

Patch available Yes

Active threat No

Deciding rule

HIGH severity (CVSS 7.0-8.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.