GHSA-v6rw-hhgg-wc4x: Github.com/evmos/evmos/v11 Denial of Service Vulnerability

CRITICAL
CVSS 9.1
Published
Advisory Summary

GHSA-v6rw-hhgg-wc4x is a CRITICAL (CVSS 9.1) denial of service vulnerability (General Security Weakness) affecting Github.com/evmos/evmos/v11 libraries in the Go ecosystem. The issue involves evmos vulnerable to dos and transaction fee expropiation through authz exploit. Remediation is available by upgrading affected packages to version 12.0.0.

GHSA-v6rw-hhgg-wc4x at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-v6rw-hhgg-wc4x
Severity CRITICAL
CVSS v3.1 Base Score 9.1
CWE Classification General Security Weakness
Affected Product Github.com/evmos/evmos/v11
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 9.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity High (I:H)
Availability High (A:H)

How to Fix GHSA-v6rw-hhgg-wc4x

To remediate this vulnerability, upgrade all affected Github.com/evmos/evmos/v11 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/evmos/evmos/v11 fixed: 12.0.0
Upgrade github.com/evmos/evmos/v11 to 12.0.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/evmos/evmos/v11

How to Check if You Are Affected

To determine whether your application is affected by GHSA-v6rw-hhgg-wc4x, inspect your project dependencies for Github.com/evmos/evmos/v11:

inspect dependencies for github.com/evmos/evmos/v11

Analyze the terminal output to locate any version of Github.com/evmos/evmos/v11 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 12.0.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Github.com/evmos/evmos/v11, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## 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).

GHSA-v6rw-hhgg-wc4x Affected Github.com/evmos/evmos/v11 Versions

1 component(s)
Fixed Versions:
12.0.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/evmos/evmos/v11
Go
< 12.0.0
12.0.0

References

Frequently Asked Questions

What is GHSA-v6rw-hhgg-wc4x?
GHSA-v6rw-hhgg-wc4x is a security vulnerability in Github.com/evmos/evmos/v11 involving Evmos vulnerable to DOS and transaction fee expropiation through Authz exploit under General Security Weakness.
Which Github.com/evmos/evmos/v11 versions are affected?
Affected versions include releases prior to 12.0.0 across affected packages: github.com/evmos/evmos/v11.
What version fixes GHSA-v6rw-hhgg-wc4x?
Upgrading to 12.0.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/evmos/evmos/v11 affected?
Yes, github.com/evmos/evmos/v11 is affected in releases prior to 12.0.0. Upgrade your dependency to 12.0.0 or later.
What is the CVSS score of GHSA-v6rw-hhgg-wc4x?
GHSA-v6rw-hhgg-wc4x has a CVSS v3.1 base score of 9.1 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H.
What CWE is associated with GHSA-v6rw-hhgg-wc4x?
GHSA-v6rw-hhgg-wc4x is classified under General Security Weakness.
How can I check Go dependencies for GHSA-v6rw-hhgg-wc4x?
Run the dependency tree command: 'inspect dependencies for github.com/evmos/evmos/v11'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-v6rw-hhgg-wc4x",
  "modified" : "2024-06-05T20:27:12Z",
  "published" : "2024-04-17T17:35:21Z",
  "aliases" : [ ],
  "summary" : "Evmos vulnerable to DOS and transaction fee expropiation through Authz exploit",
  "details" : "## Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nAn 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.\n\n## Disclosure\n\nEvmos 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.\n\n### Additional details\n\nThe attack scenario is as follows:\n\n1. The attacker deploys a simple smart contract with an infinite loop to the chain.  \n2. The attacker calls the smart contract using an embedded transaction with an extremely high gas value (`uint64` max or similar). \n3. 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.**\n\n## Users Impacted\nAll 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. \n\n## Patches\n\n_Has the problem been patched? What versions should users upgrade to?_\n\nThe vulnerability has been patched on Evmos versions ≥v12.0.0.\n\n### Details\n\nAs 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:\n\n- Doing a recursive check over the nested messages of `MsgExec`\n- Limiting the amount of possible nested messages (inner messages) in `MsgExec`\n\nThis is done by adding an additional `AnteHandler` decorator (`AuthzLimiterDecorator`) for Cosmos and EIP-712 transactions.\n\nThis is a state machine-breaking change as it restricts previously allowed messages and thus requires a hard-fork upgrade.\n\n## References\n__Are there any links users can visit to find out more?__\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n- Reach out to the Core Team in [Discord](https://discord.gg/evmos)\n- Open a discussion in [evmos/evmos](https://github.com/evmos/evmos/discussions)\n- Email us at [security@evmos.org](mailto:security@evmos.org) for security questions\n- For Press, email us at [evmos@west-comms.com](mailto:evmos@west-comms.com).\n",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/evmos/evmos/v11"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "12.0.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/evmos/evmos/security/advisories/GHSA-v6rw-hhgg-wc4x"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/evmos/evmos"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-04-17T17:35:21Z",
    "nvd_published_at" : null
  }
}