GHSA-23qp-3c2m-xx6w: wasmvm Malicious Smart Contract Can Crash Vulnerability

MODERATE
CWE-476
Published
Advisory Summary

GHSA-23qp-3c2m-xx6w is a MODERATE malicious smart contract can crash vulnerability (CWE-476: NULL Pointer Dereference) affecting wasmvm libraries in the Go ecosystem. The issue involves malicious smart contract can crash the chain. Remediation is available by upgrading affected packages to version 1.5.8, 2.0.6, 2.1.5, 2.2.2.

GHSA-23qp-3c2m-xx6w at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-23qp-3c2m-xx6w
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-476: NULL Pointer Dereference
Affected Product wasmvm
Package Ecosystem Go
Published Date
Last Updated

How to Fix GHSA-23qp-3c2m-xx6w

To remediate this vulnerability, upgrade all affected wasmvm 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/CosmWasm/wasmvm fixed: 1.5.8
Upgrade github.com/CosmWasm/wasmvm to 1.5.8
github.com/CosmWasm/wasmvm/v2 fixed: 2.0.6
Upgrade github.com/CosmWasm/wasmvm/v2 to 2.0.6
github.com/CosmWasm/wasmvm/v2 fixed: 2.1.5
Upgrade github.com/CosmWasm/wasmvm/v2 to 2.1.5
github.com/CosmWasm/wasmvm/v2 fixed: 2.2.2
Upgrade github.com/CosmWasm/wasmvm/v2 to 2.2.2
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/CosmWasm/wasmvm

How to Check if You Are Affected

To determine whether your application is affected by GHSA-23qp-3c2m-xx6w, inspect your project dependencies for wasmvm:

inspect dependencies for github.com/CosmWasm/wasmvm

Analyze the terminal output to locate any version of wasmvm in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.5.8), 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 CWE-476: NULL Pointer Dereference, where the product dereferences a pointer that it expects to be valid but is null. In wasmvm, 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

# CWA-2025-001 **Severity** Medium (Moderate + Likely)[^1] **Affected versions:** - wasmvm >= 2.2.0, < 2.2.2 - wasmvm >= 2.1.0, < 2.1.5 - wasmvm >= 2.0.0, < 2.0.6 - wasmvm < 1.5.8 **Patched versions:** - wasmvm 1.5.8, 2.0.6, 2.1.5, 2.2.2 ## Description of the bug The vulnerability can be used to crash the chain. The underlying bug that causes this is present on both permissioned and premissionless chains, but it can only be triggered _reliably_ with a malicious contract, so permissioned chains are much less likely to be affected. (We'll add more detail once chains had a chance to upgrade.) ## Patch - 1.5: https://github.com/CosmWasm/wasmvm/commit/1151bc6df7d02d1889b8da37cf8510eaf4198eea - 2.0: https://github.com/CosmWasm/wasmvm/commit/d4ff2adee44e6b9f7415a5dfbb3de745ab9b7678 - 2.1: https://github.com/CosmWasm/wasmvm/commit/8d44a286fabc793a2fba93752e58cd0fd5b88a2d - 2.2: https://github.com/CosmWasm/wasmvm/commit/0aefa4c378457aeb3c07e7975b875be38872c56d ## Applying the patch The patch will be shipped in releases of wasmvm. You can update more or less as follows: 1. Check the current wasmvm version: `go list -m github.com/CosmWasm/wasmvm` 2. Bump the `github.com/CosmWasm/wasmvm` dependency in your go.mod to one of the patched version depending on which minor version you are on; `go mod tidy`; commit. 3. If you use the static libraries `libwasmvm_muslc.aarch64.a`/`libwasmvm_muslc.x86_64.a`, update them accordingly. 4. Check the updated wasmvm version: `go list -m github.com/CosmWasm/wasmvm` and ensure you see 1.5.8, 2.0.6, 2.1.5 or 2.2.2. 5. Follow your regular practices to deploy chain upgrades. While the fix for this issue is not consensus breaking, the patch contains another consensus breaking fix and requires a coordinated upgrade. ## Acknowledgement This issue was found by meadow101 who reported it to the Cosmos Bug Bounty Program on HackerOne. If you believe you have found a bug in the Interchain Stack or would like to contribute to the program by reporting a bug, please see <https://hackerone.com/cosmos>. ## Timeline - 2024-11-25: Confio receives a report through the Cosmos bug bounty program maintained by Amulet. - 2024-11-28: Confio security contributors confirm the report. - 2024-11-28: Confio developed the patch internally. - 2025-02-04: Patch gets released. [^1]: following Amulet's Severity Classification Framework ACMv1.2: https://github.com/interchainio/security/blob/0295254e8645301ccb606d46108a45cede0a73e0/resources/CLASSIFICATION_MATRIX.md

GHSA-23qp-3c2m-xx6w Affected wasmvm Versions

4 component(s)
Fixed Versions:
1.5.82.0.62.1.52.2.2
Product / Package Ecosystem Affected Versions Fixed Version
github.com/CosmWasm/wasmvm
Go
< 1.5.8
1.5.8
github.com/CosmWasm/wasmvm/v2
Go
≥ 2.0.0
< 2.0.6
2.0.6
github.com/CosmWasm/wasmvm/v2
Go
≥ 2.1.0
< 2.1.5
2.1.5
github.com/CosmWasm/wasmvm/v2
Go
≥ 2.2.0
< 2.2.2
2.2.2

References

Frequently Asked Questions

What is GHSA-23qp-3c2m-xx6w?
GHSA-23qp-3c2m-xx6w is a security vulnerability in wasmvm involving Malicious smart contract can crash the chain under CWE-476: NULL Pointer Dereference.
Which wasmvm versions are affected?
Affected versions include releases prior to 1.5.8, 2.0.6, 2.1.5, 2.2.2 across affected packages: github.com/CosmWasm/wasmvm, github.com/CosmWasm/wasmvm/v2.
What version fixes GHSA-23qp-3c2m-xx6w?
Upgrading to 1.5.8, 2.0.6, 2.1.5, 2.2.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/CosmWasm/wasmvm affected?
Yes, github.com/CosmWasm/wasmvm is affected in releases prior to 1.5.8. Upgrade your dependency to 1.5.8 or later.
Is github.com/CosmWasm/wasmvm/v2 affected?
Yes, github.com/CosmWasm/wasmvm/v2 is affected in releases prior to 2.0.6, 2.1.5, 2.2.2. Upgrade your dependency to 2.0.6, 2.1.5, 2.2.2 or later.
What CWE is associated with GHSA-23qp-3c2m-xx6w?
GHSA-23qp-3c2m-xx6w is classified under CWE-476: NULL Pointer Dereference (The product dereferences a pointer that it expects to be valid but is NULL.).
How can I check Go dependencies for GHSA-23qp-3c2m-xx6w?
Run the dependency tree command: 'inspect dependencies for github.com/CosmWasm/wasmvm'. 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-23qp-3c2m-xx6w",
  "modified" : "2025-02-06T18:03:00Z",
  "published" : "2025-02-04T18:54:13Z",
  "aliases" : [ ],
  "summary" : "wasmvm: Malicious smart contract can crash the chain",
  "details" : "# CWA-2025-001\n\n**Severity**\n\nMedium (Moderate + Likely)[^1]\n\n**Affected versions:**\n\n- wasmvm >= 2.2.0, < 2.2.2\n- wasmvm >= 2.1.0, < 2.1.5\n- wasmvm >= 2.0.0, < 2.0.6\n- wasmvm < 1.5.8\n\n**Patched versions:**\n\n- wasmvm 1.5.8, 2.0.6, 2.1.5, 2.2.2\n\n## Description of the bug\n\nThe vulnerability can be used to crash the chain. The underlying bug that causes this is present on both permissioned and premissionless chains, but it can only be triggered _reliably_ with a malicious contract, so permissioned chains are much less likely to be affected.\n\n(We'll add more detail once chains had a chance to upgrade.)\n\n## Patch\n\n- 1.5: https://github.com/CosmWasm/wasmvm/commit/1151bc6df7d02d1889b8da37cf8510eaf4198eea\n- 2.0: https://github.com/CosmWasm/wasmvm/commit/d4ff2adee44e6b9f7415a5dfbb3de745ab9b7678\n- 2.1: https://github.com/CosmWasm/wasmvm/commit/8d44a286fabc793a2fba93752e58cd0fd5b88a2d\n- 2.2: https://github.com/CosmWasm/wasmvm/commit/0aefa4c378457aeb3c07e7975b875be38872c56d\n\n## Applying the patch\n\nThe patch will be shipped in releases of wasmvm. You can update more or less as follows:\n\n1. Check the current wasmvm version: `go list -m github.com/CosmWasm/wasmvm`\n2. Bump the `github.com/CosmWasm/wasmvm` dependency in your go.mod to one of the patched version\n   depending on which minor version you are on; `go mod tidy`; commit.\n3. If you use the static libraries `libwasmvm_muslc.aarch64.a`/`libwasmvm_muslc.x86_64.a`, update them accordingly.\n4. Check the updated wasmvm version: `go list -m github.com/CosmWasm/wasmvm` and ensure you see 1.5.8, 2.0.6, 2.1.5 or 2.2.2.\n5. Follow your regular practices to deploy chain upgrades.\n\nWhile the fix for this issue is not consensus breaking, the patch contains another\nconsensus breaking fix and requires a coordinated upgrade.\n\n## Acknowledgement\n\nThis issue was found by meadow101 who reported it to the Cosmos Bug Bounty Program on HackerOne.\n\nIf you believe you have found a bug in the Interchain Stack or would like to contribute to the\nprogram by reporting a bug, please see <https://hackerone.com/cosmos>.\n\n## Timeline\n\n- 2024-11-25: Confio receives a report through the Cosmos bug bounty program maintained by Amulet.\n- 2024-11-28: Confio security contributors confirm the report.\n- 2024-11-28: Confio developed the patch internally.\n- 2025-02-04: Patch gets released.\n\n[^1]: following Amulet's Severity Classification Framework ACMv1.2: https://github.com/interchainio/security/blob/0295254e8645301ccb606d46108a45cede0a73e0/resources/CLASSIFICATION_MATRIX.md",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/CosmWasm/wasmvm"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.5.8"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/CosmWasm/wasmvm/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.0.0"
      }, {
        "fixed" : "2.0.6"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/CosmWasm/wasmvm/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.1.0"
      }, {
        "fixed" : "2.1.5"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/CosmWasm/wasmvm/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.2.0"
      }, {
        "fixed" : "2.2.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/CosmWasm/wasmvm/security/advisories/GHSA-23qp-3c2m-xx6w"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/CosmWasm/wasmvm/commit/0aefa4c378457aeb3c07e7975b875be38872c56d"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/CosmWasm/wasmvm/commit/1151bc6df7d02d1889b8da37cf8510eaf4198eea"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/CosmWasm/wasmvm/commit/8d44a286fabc793a2fba93752e58cd0fd5b88a2d"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/CosmWasm/wasmvm/commit/d4ff2adee44e6b9f7415a5dfbb3de745ab9b7678"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/CosmWasm/advisories/blob/main/CWAs/CWA-2025-001.md"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/CosmWasm/wasmvm"
  }, {
    "type" : "WEB",
    "url" : "https://pkg.go.dev/vuln/GO-2025-3448"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-476" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-02-04T18:54:13Z",
    "nvd_published_at" : null
  }
}