Affected versions
- Affected versions
- < 1.5.8
- Fixed version
- 1.5.8
- Affected versions
- >= 2.0.0, < 2.0.7
- Fixed version
- 2.0.7
- Affected versions
- >= 2.1.0, < 2.1.4
- Fixed version
- 2.1.4
- Affected versions
- >= 2.0.0, < 2.0.4
- Fixed version
- 2.0.4
- Affected versions
- >= 2.1.0, < 2.1.3
- Fixed version
- 2.1.3
- Affected versions
- < 1.5.5
- Fixed version
- 1.5.5
Description
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:
Check the current wasmvm version:
go list -m github.com/CosmWasm/wasmvmBump the
github.com/CosmWasm/wasmvmdependency 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.If you use the static libraries
libwasmvm_muslc.aarch64.a/libwasmvm_muslc.x86_64.a, update them accordingly.Check the updated wasmvm version:
go list -m github.com/CosmWasm/wasmvmand ensure you see 1.5.5, 2.0.4, 2.1.3.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
Links
- https://github.com/CosmWasm/advisories/blob/main/CWAs/CWA-2024-007.md
- https://github.com/CosmWasm/cosmwasm/commit/0e70bd83119b02f99a2c0397f0913e0803750fd9
- https://github.com/CosmWasm/cosmwasm/commit/16eabd681790508b13dac8e67f9e6e61045240ea
- https://github.com/CosmWasm/cosmwasm/commit/f5bf24f3acadca2892afd58cc3ce5fdeb932d492
- https://github.com/CosmWasm/wasmvm
- https://github.com/CosmWasm/wasmvm/security/advisories/GHSA-2q97-m5rc-p3gp
- https://github.com/advisories/GHSA-2q97-m5rc-p3gp

