# GHSA-47ww-ff84-4jrg: Cosmos SDK: x/group can halt when erroring in EndBlocker > Malicious proposals in the x/group module can trigger errors in the EndBlocker, causing a chain halt for validators and full nodes. - **Severity:** Not scored - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 12 Mar 2025 - **Also known as:** GO-2025-3516 ## What is GHSA-47ww-ff84-4jrg? GHSA-47ww-ff84-4jrg is a denial of service vulnerability in github.com/cosmos/cosmos-sdk, published on 12 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Name: ISA-2025-002: x/group can halt when erroring in EndBlocker Component: CosmosSDK Criticality: High (Considerable Impact; Likely Likelihood per [ACMv1.2](https://github.com/interchainio/security/blob/main/resources/CLASSIFICATION_MATRIX.md)) Affected versions: <= v0.47.16, <= 0.50.12 Affected users: Validators, Full nodes, Users on chains that utilize the groups module Cosmos SDK chains in unpatched releases that use the `x/group` module are affected. ### Description An issue was discovered in the groups module where malicious proposals would result in an errors triggered in the module's end blocker that could result in a chain halt. Any set of users that can interact with the groups module could introduce this state. ### Patches _Has the problem been patched? What versions should users upgrade to?_ The new Cosmos SDK release [v0.50.13](https://github.com/cosmos/cosmos-sdk/releases/tag/v0.50.13) and [v0.47.17](https://github.com/cosmos/cosmos-sdk/releases/tag/v0.47.17) fix this issue. ### Testing Testing we have done to gain more confidence in this release: In addition to testing Cosmos SDK we also did the following: - Ran a patched node in a local `v0.50` testnet with the failing state and did not halt (an unpatched network confirmed to halt) - Ran a patched node on Xion Mainnet (uses `x/group`) - Ran a patched node on Zetachain Mainnet (uses `x/xgroup`) ### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_ There are no known workarounds for this issue. It is advised that chains apply the update. This issue was reported to the Cosmos Bug Bounty Program by [wbowling](https://github.com/wbowling) on HackerOne on February 28, 2025. 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. If you have questions about Interchain security efforts, please reach out to our official communication channel at [security@interchain.io](mailto:security@interchain.io). For more information about the Interchain Foundation’s engagement with Amulet, and to sign up for security notification emails, please see https://github.com/interchainio/security. ## Which versions are affected by GHSA-47ww-ff84-4jrg? 5 open source packages ship an affected version, including github.com/cosmos/cosmos-sdk. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/cosmos/cosmos-sdk` | Go | All versions | 0.47.17, 0.50.13 | | `github.com/cosmos/cosmos-sdk` | Go | All versions | 0.47.17 | | `github.com/cosmos/cosmos-sdk` | Go | All versions | 0.47.17 | | `github.com/cosmos/cosmos-sdk` | Go | From 0.50.0-alpha.0 | 0.50.13 | | `github.com/cosmos/cosmos-sdk` | Go | From 0.50.0-alpha.0 | 0.50.13 | ## How do I fix GHSA-47ww-ff84-4jrg? Upgrade github.com/cosmos/cosmos-sdk to a fixed version for your release line: 0.47.17 or 0.50.13. ## Is GHSA-47ww-ff84-4jrg being exploited? There is no known exploitation of GHSA-47ww-ff84-4jrg in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for GHSA-47ww-ff84-4jrg and fix it if it is affected. What it is: GHSA-47ww-ff84-4jrg is a denial of service vulnerability in github.com/cosmos/cosmos-sdk, published on 12 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of GHSA-47ww-ff84-4jrg in the wild and no public exploit code. Affected packages and fixed versions: - github.com/cosmos/cosmos-sdk (Go): affected all versions; fixed in 0.47.17, 0.50.13 - github.com/cosmos/cosmos-sdk (Go): affected all versions; fixed in 0.47.17 - github.com/cosmos/cosmos-sdk (Go): affected all versions; fixed in 0.47.17 - github.com/cosmos/cosmos-sdk (Go): affected from 0.50.0-alpha.0; fixed in 0.50.13 - github.com/cosmos/cosmos-sdk (Go): affected from 0.50.0-alpha.0; fixed in 0.50.13 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/GHSA-47ww-ff84-4jrg/ (Markdown: https://insights.sbomify.com/GHSA-47ww-ff84-4jrg/index.md) ``` ## Sources - OSV: https://osv.dev/vulnerability/GHSA-47ww-ff84-4jrg --- From sbomify Insights: https://insights.sbomify.com/GHSA-47ww-ff84-4jrg/ Summaries are generated and may contain mistakes; the official description above is the record.