Skip to content
Fencer Intel
high —

GHSA-x5vx-95h7-rv4p json

Cosmos SDK: Groups module can halt chain when handling a malicious proposal

published last yr. modified last yr. also GO-2025-3476

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

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).

Patch / fix

  • go github.com/cosmos/cosmos-sdk 0.47.16-ics-lsm, 0.50.12

Is GHSA-x5vx-95h7-rv4p in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
go github.com/cosmos/cosmos-sdk
<0.47.16-ics-lsm
>=0.50.0-alpha.0, <0.50.12
0.47.16-ics-lsm
0.50.12

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.