First published: Tue Mar 11 2025(Updated: )
# Description [An issue was discovered in IBC-Go's deserialization of acknowledgements](https://github.com/cosmos/ibc-go/security/advisories/GHSA-jg6f-48ff-5xrw) that results in non-deterministic behavior which can halt a chain. Any user that can open an IBC channel can introduce this state to the chain. This an upstream dependency used in cheqd-node, rather than a custom module. ## Impact Could result in a chain halt. ## Patches Validators, full nodes, and IBC relayers should upgrade to **[cheqd-node v3.1.7](https://github.com/cheqd/cheqd-node/releases/tag/v3.1.7)**. This upgrade does not require a software upgrade proposal on-chain and is meant to be non state-breaking. ## References See [ASA-2025-004: Non-deterministic JSON Unmarshalling of IBC Acknowledgement can result in a chain halt](https://github.com/cosmos/ibc-go/security/advisories/GHSA-jg6f-48ff-5xrw) upstream on IBC-Go.
Affected Software | Affected Version | How to fix |
---|---|---|
go/github.com/cheqd/cheqd-node | <3.1.7 | 3.1.7 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
GHSA-33cr-m232-xqch has been classified with a high severity due to its potential to cause non-deterministic behavior and halt a blockchain.
To fix GHSA-33cr-m232-xqch, update to version 3.1.7 or later of the affected IBC-Go package.
GHSA-33cr-m232-xqch affects the IBC-Go implementation, particularly in the version prior to 3.1.7.
The consequences of GHSA-33cr-m232-xqch include possible chain halting and non-deterministic state due to improper deserialization of acknowledgments.
Any user who can open an IBC channel can potentially exploit the vulnerability identified in GHSA-33cr-m232-xqch.