Vulnerability in github.com/cosmos/cosmos-sdk (CVE-2021-41135)
Summary
Vulnerability in github.com/cosmos/cosmos-sdk (CVE-2021-41135). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.44.2 or later.
Original description
The description as published by the source.
The Cosmos-SDK is a framework for building blockchain applications in Golang. Affected versions of the SDK were vulnerable to a consensus halt due to non-deterministic behaviour in a ValidateBasic method in the x/authz module. The MsgGrant of the x/authz module contains a Grant field which includes a user-defined expiration time for when the authorization grant expires. In Grant.ValidateBasic(), that time is compared to the node’s local clock time. Any chain running an affected version of the SDK with the authz module enabled could be halted by anyone with the ability to send transactions on that chain. Recovery would require applying the patch and rolling back the latest block. Users are advised to update to version 0.44.2.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-41135 has been found in github.com/cosmos/cosmos-sdk.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/cosmos/cosmos-sdk to 0.44.2 or later.
If unsure, ask your IT team or search "github.com/cosmos/cosmos-sdk CVE-2021-41135" on the vendor's site.
CVE-2021-41135 (github.com/cosmos/cosmos-sdk) — CWE-754
Attack vector: remote (network-reachable) / no user interaction
Patched: 0.44.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-754) exists in github.com/cosmos/cosmos-sdk.
Check the vendor advisory for the affected versions of github.com/cosmos/cosmos-sdk.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.44.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/cosmos/cosmos-sdk' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/cosmos/cosmos-sdk' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/cosmos/cosmos-sdkを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/cosmos/cosmos-sdk to 0.44.2ステージング環境で 0.44.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- report forum.cosmos.network
- web github.com