GHSA-2q97-m5rc-p3gp: CosmWasm VM Incorrect metering
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Fixed version: cosmwasm-vm (crates.io) 2.0.7, 2.1.4, 1.5.8; github.com/CosmWasm/wasmvm (Go) 1.5.5; github.com/CosmWasm/wasmvm/v2 (Go) 2.0.4, 2.1.3.
Low priority for now. Upgrade to cosmwasm-vm (crates.io) 2.0.7, 2.1.4, 1.5.8; github.com/CosmWasm/wasmvm (Go) 1.5.5; github.com/CosmWasm/wasmvm/v2 (Go) 2.0.4, 2.1.3 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
# CWA-2024-007 **Severity** Medium (Moderate + Likely)[^1] **Affected versions:** - wasmvm >= 2.1.0, < 2.1.3 - wasmvm >= 2.0.0, < 2.0.4 - wasmvm < 1.5.5 - cosmwasm-vm >= 2.1.0, < 2.1.4 - cosmwasm-vm >= 2.0.0, < 2.0.7 - cosmwasm-vm < 1.5.8 **Patched versions:** - wasmvm 1.5.5, 2.0.4, 2.1.3 - cosmwasm-vm 1.5.8, 2.0.7, 2.1.4 ## Description of the bug (Blank for now. We'll add more detail once chains had a chance to upgrade.) ## Patch - 1.5: https://github.com/CosmWasm/cosmwasm/commit/16eabd681790508b13dac8e67f9e6e61045240ea - 2.0: https://github.com/CosmWasm/cosmwasm/commit/0e70bd83119b02f99a2c0397f0913e0803750fd9 - 2.1: https://github.com/CosmWasm/cosmwasm/commit/f5bf24f3acadca2892afd58cc3ce5fdeb932d492 ## 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 1.5.5, 2.0.4, 2.1.3 depending on which minor version you are; `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.5, 2.0.4, 2.1.3. 5. Follow your regular practices to deploy chain upgrades. To double check if the correct library version is loaded at runtime, use this query: `<appd> query wasm libwasmvm-version`. It must show 1.5.5, 2.0.4 or 2.1.3. The patch is consensus breaking 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-08-28: Confio receives a report through the Cosmos bug bounty program maintained by Amulet. - 2024-08-30: Confio security contributors confirm the report. - 2024-09-02: Confio developed the patch internally. - 2024-09-23: Patch is released. [^1]: following Amulet's Severity Classification Framework ACMv1: https://github.com/interchainio/security/blob/e0227a1fb4059144aab4f6003eeee7f09912db3a/resources/CLASSIFICATION_MATRIX.md
- Published
- Dec 10, 2024
- Updated
- Dec 10, 2024
- EPSS
- —
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- 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.
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| Go | github.com/CosmWasm/wasmvm/v2 | pkg:golang/github.com/CosmWasm/wasmvm/v2 |
| Go | github.com/CosmWasm/wasmvm | pkg:golang/github.com/CosmWasm/wasmvm |
| crates.io | cosmwasm-vm | pkg:cargo/cosmwasm-vm |
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| crates.io | cosmwasm-vm | from 2.0.0 · before 2.0.7 | 2.0.7 |
| crates.io | cosmwasm-vm | from 2.1.0 · before 2.1.4 | 2.1.4 |
| crates.io | cosmwasm-vm | before 1.5.8 | 1.5.8 |
| Go | github.com/CosmWasm/wasmvm | before 1.5.5 | 1.5.5 |
| Go | github.com/CosmWasm/wasmvm/v2 | from 2.0.0 · before 2.0.4 | 2.0.4 |
| Go | github.com/CosmWasm/wasmvm/v2 | from 2.1.0 · before 2.1.3 | 2.1.3 |
Same product
Go: all recordsOther highest-scoring records for the same primary product.
- GHSA-vmqh-5232-v43rPanic in wasmvm can slow down block production0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| crates.io:cosmwasm-vm | 1.5.8 | Package registry (OSV) |
| crates.io:cosmwasm-vm | 2.0.7 | Package registry (OSV) |
| crates.io:cosmwasm-vm | 2.1.4 | Package registry (OSV) |
| Go:github.com/CosmWasm/wasmvm | 1.5.5 | Package registry (OSV) |
| Go:github.com/CosmWasm/wasmvm/v2 | 2.0.4 | Package registry (OSV) |
| Go:github.com/CosmWasm/wasmvm/v2 | 2.1.3 | Package 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.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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.
Change log (2)
- Fix✗ → ✓
- CVSS5.5 → —
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- github.com/CosmWasm/cosmwasm/commit/0e70bd83119b02f99a2c0397f0913e0803750fd9
- github.com/CosmWasm/cosmwasm/commit/16eabd681790508b13dac8e67f9e6e61045240ea
- github.com/CosmWasm/cosmwasm/commit/f5bf24f3acadca2892afd58cc3ce5fdeb932d492
- github.com/CosmWasm/advisories/blob/main/CWAs/CWA-2024-007.md
- github.com/CosmWasm/wasmvm
Vendor advisories and official records. Exploit/PoC links are deliberately left out.