Skip to content
Noroxi
OSV ecosystem advisory

GHSA-v6rw-hhgg-wc4x: Evmos vulnerable to DOS and transaction fee expropiation through Authz exploit

CriticalCVSS 9.1 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 36/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: github.com/evmos/evmos/v11 (Go) 12.0.0; github.com/evmos/evmos/v12 (Go) 12.0.0.

Low priority for now. Upgrade to github.com/evmos/evmos/v11 (Go) 12.0.0; github.com/evmos/evmos/v12 (Go) 12.0.0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: OSV

## Impact _What kind of vulnerability is it? Who is impacted?_ An attacker can use this bug to bypass the block gas limit and gas payment completely to perform a full Denial-of-Service against the chain. ## Disclosure Evmos versions below `v11.0.1` do not check for `MsgEthereumTx` messages that are nested under other messages. This allows a malicious actor to perform EVM transactions that do not meet the checks performed under `newEthAnteHandler`. This opens the possibility for the DOS of validators and consequently halt the chain through an infinite EVM execution. ### Additional details The attack scenario is as follows: 1. The attacker deploys a simple smart contract with an infinite loop to the chain. 2. The attacker calls the smart contract using an embedded transaction with an extremely high gas value (`uint64` max or similar). 3. Once the transaction is included in a block, nodes will try to execute the EVM transaction with almost infinite gas and get stuck. **This stops new block creation and effectively halts the chain, requiring a manual restart of all nodes.** ## Users Impacted All Evmos users are impacted by this vulnerability as it has the potential to halt the chain. Users' funds and chain state are safe but when under attack, the chain could be deemed unusable. ## Patches _Has the problem been patched? What versions should users upgrade to?_ The vulnerability has been patched on Evmos versions ≥v12.0.0. ### Details As a temporary workaround, the fix blocks `MsgEthereumTxs` messages from being sent under the `authz` module's `MsgExec` message. It also covers the scenario in which `MsgEthereumTx` are deeply nested by: - Doing a recursive check over the nested messages of `MsgExec` - Limiting the amount of possible nested messages (inner messages) in `MsgExec` This is done by adding an additional `AnteHandler` decorator (`AuthzLimiterDecorator`) for Cosmos and EIP-712 transactions. This is a state machine-breaking change as it restricts previously allowed messages and thus requires a hard-fork upgrade. ## References __Are there any links users can visit to find out more?__ ### For more information If you have any questions or comments about this advisory: - Reach out to the Core Team in [Discord](https://discord.gg/evmos) - Open a discussion in [evmos/evmos](https://github.com/evmos/evmos/discussions) - Email us at [security@evmos.org](mailto:security@evmos.org) for security questions - For Press, email us at [evmos@west-comms.com](mailto:evmos@west-comms.com).

Published
Apr 17, 2024
Updated
Jun 5, 2024
EPSS
—
CWE
—

Report tools

JSON

Action score

36

Monitor

Low priority for now.

CVSS
36 / 40 · 9.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · —

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow GHSA-v6rw-hhgg-wc4x

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
Gogithub.com/evmos/evmos/v11

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Gogithub.com/evmos/evmosfrom 0—
Gogithub.com/evmos/evmos/v10from 0—
Gogithub.com/evmos/evmos/v11from 0—
Gogithub.com/evmos/evmos/v11before 12.0.012.0.0
Gogithub.com/evmos/evmos/v12before 12.0.012.0.0
Gogithub.com/evmos/evmos/v2from 0—
Gogithub.com/evmos/evmos/v3from 0—
Gogithub.com/evmos/evmos/v4from 0—
Gogithub.com/evmos/evmos/v5from 0—
Gogithub.com/evmos/evmos/v6from 0—
Gogithub.com/evmos/evmos/v7from 0—
Gogithub.com/evmos/evmos/v8from 0—
Gogithub.com/evmos/evmos/v9from 0—

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Go:github.com/evmos/evmos/v1112.0.0Package registry (OSV)
Go:github.com/evmos/evmos/v1212.0.0Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

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

osv

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

Show all references (1 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records