Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
5 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
CWA-2025-006: Improper error handling may lead to IBC channel opening despite error Severity High (Considerable + Likely)[^1] Affected versions: - wasmd 0.60.0 - wasmd = 0.51.0 < 0.55.1 Patched versions: - wasmd 0.60.1, 0.55.1, 0.54.1, 0.53.3 Description of the bug A contract erroring during IBC channel opening does not prevent the channel from opening. Applying the patch The patch will be shipped in a wasmd release. You will also have to update libwasmvm if you build statically. If you already use the latest / close to latest wasmd, you can update more or less as follows: 1. Check the current wasmd version: go list -m github.com/CosmWasm/wasmd 2. Bump the github.com/CosmWasm/wasmd dependency in your go.mod to 0.60.1 (Cosmos SDK 0.53 compatible), 0.55.1 (Cosmos SDK 0.50 compatible), 0.54.1 or 0.53.3; go mod tidy; commit. 3. If you use the static libraries libwasmvmmuslc.aarch64.a/libwasmvmmuslc.x8664.a, make sure that you use the same version as your wasmvm version. 4. Check the…
Recommended action: Upgrade to 0.60.1, 0.55.1, 0.54.1 or 0.53.3 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
CWA-2024-009 Severity Low (Marginal + Likely)[^1] Affected versions: - wasmd < 0.53.1 Patched versions: - wasmd 0.53.2 (please note that wasmd 0.53.1 is broken and must not be used) Description of the bug (Blank for now. We'll add more detail once chains had a chance to upgrade.) Mitigations Apart from upgrading, it is recommended to not open the gRPC and REST APIs of validator nodes to the public internet. Use isolated and resource-constrained environments for running separate public RPC nodes instead. These can then easily be thrown away and replaced with new instances in case of problems. Applying the patch Official Wasmd patch The patch will be shipped in a wasmd release. You will also have to update libwasmvm if you build statically. If you already use the latest / close to latest wasmd, you can update more or less as follows: 1. Check the current wasmd version: go list -m github.com/CosmWasm/wasmd 2. Bump the github.com/CosmWasm/wasmd dependency in your go.mod to 0.53.2 (Cosmos…
Recommended action: Upgrade to 0.53.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Component: wasmd Criticality: Medium (ACMv1: I:Moderate; L:Likely) Patched versions: wasmd 0.53.0 See CWA-2024-006 for more details.
Recommended action: Upgrade to 0.53.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Go github.com/CosmWasm/wasmd >= 0.50.0, < 0.53.0; < 0.46.0
Fixed in
0.53.00.46.0· Vendor fix available
Issue
Component: wasmd Criticality: High (ACMv1: I:Critical; L:Likely) Patched versions: wasmd 0.53.0, 0.46.0 See CWA-2024-005 for more details.
Recommended action: Upgrade to 0.53.0 or 0.46.0 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Component: wasmd Criticality: Low (ACMv1: I:Moderate; L:Unlikely) Patched versions: wasmd 0.52.0 In multiple wasmd message types it was possible to add a large number of addresses which might lead to unexpected resource consumption in ValidateBasic. See CWA-2024-003 for more details.
Recommended action: Upgrade to 0.52.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.