# GHSA-x5vx-95h7-rv4p: Cosmos SDK: Groups module can halt chain when handling a malicious proposal > A malicious proposal in the Cosmos SDK groups module causes a division by zero, halting the blockchain for all validators and 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:** 20 Feb 2025 - **Also known as:** GO-2025-3476 ## What is GHSA-x5vx-95h7-rv4p? GHSA-x5vx-95h7-rv4p is a denial of service vulnerability in github.com/cosmos/cosmos-sdk, published on 20 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Name: ASA-2025-003: Groups module can halt chain when handling a malicious proposal 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.15, <= 0.50.11 Affected users: Validators, Full nodes, Users on chains that utilize the groups module ### Description An issue was discovered in the groups module where a malicious proposal would result in a division by zero, and subsequently halt a chain due to the resulting error. Any user that can interact with the groups module can introduce this state. ### Patches The new Cosmos SDK release [v0.50.12](https://github.com/cosmos/cosmos-sdk/releases/tag/v0.50.12) and [v0.47.16](https://github.com/cosmos/cosmos-sdk/releases/tag/v0.47.16) fix this issue. ### Workarounds There are no known workarounds for this issue. It is advised that chains apply the update. ### Timeline * February 9, 2025, 5:18pm PST: Issue reported to the Cosmos Bug Bounty program * February 9, 2025, 8:12am PST: Issue triaged by Amulet on-call, and distributed to Core team * February 9, 2025, 12:25pm PST: Core team completes validation of issue * February 18, 2025, 8:00am PST / 17:00 CET: Pre-notification delivered * February 20, 2025, 8:00am PST / 17:00 CET: Patch made available This issue was reported to the Cosmos Bug Bounty Program by [dongsam](https://github.com/dongsam) on HackerOne on February 9, 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. A Github Security Advisory for this issue is available in the Cosmos SDK [repository](https://github.com/cosmos/cosmos-sdk/security/advisories/GHSA-x5vx-95h7-rv4p). ## Which versions are affected by GHSA-x5vx-95h7-rv4p? 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.16-ics-lsm, 0.50.12 | | `github.com/cosmos/cosmos-sdk` | Go | All versions | 0.47.16-ics-lsm | | `github.com/cosmos/cosmos-sdk` | Go | All versions | 0.47.16-ics-lsm | | `github.com/cosmos/cosmos-sdk` | Go | From 0.50.0-alpha.0 | 0.50.12 | | `github.com/cosmos/cosmos-sdk` | Go | From 0.50.0-alpha.0 | 0.50.12 | ## How do I fix GHSA-x5vx-95h7-rv4p? Upgrade github.com/cosmos/cosmos-sdk to a fixed version for your release line: 0.47.16-ics-lsm or 0.50.12. ## Is GHSA-x5vx-95h7-rv4p being exploited? There is no known exploitation of GHSA-x5vx-95h7-rv4p in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for GHSA-x5vx-95h7-rv4p and fix it if it is affected. What it is: GHSA-x5vx-95h7-rv4p is a denial of service vulnerability in github.com/cosmos/cosmos-sdk, published on 20 Feb 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-x5vx-95h7-rv4p 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.16-ics-lsm, 0.50.12 - github.com/cosmos/cosmos-sdk (Go): affected all versions; fixed in 0.47.16-ics-lsm - github.com/cosmos/cosmos-sdk (Go): affected all versions; fixed in 0.47.16-ics-lsm - github.com/cosmos/cosmos-sdk (Go): affected from 0.50.0-alpha.0; fixed in 0.50.12 - github.com/cosmos/cosmos-sdk (Go): affected from 0.50.0-alpha.0; fixed in 0.50.12 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-x5vx-95h7-rv4p/ (Markdown: https://insights.sbomify.com/GHSA-x5vx-95h7-rv4p/index.md) ``` ## Sources - OSV: https://osv.dev/vulnerability/GHSA-x5vx-95h7-rv4p --- From sbomify Insights: https://insights.sbomify.com/GHSA-x5vx-95h7-rv4p/ Summaries are generated and may contain mistakes; the official description above is the record.