# GHSA-33cr-m232-xqch: cheqd-node affected by Non-deterministic JSON Unmarshalling of IBC Acknowledgement

> Attackers can halt the blockchain by exploiting non-deterministic JSON unmarshalling in IBC acknowledgements, requiring node operators to upgrade.

- **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:** 11 Mar 2025
- **Also known as:** GO-2025-3514

## What is GHSA-33cr-m232-xqch?

GHSA-33cr-m232-xqch is an unsafe deserialization vulnerability in github.com/cheqd/cheqd-node, published on 11 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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

## Which versions are affected by GHSA-33cr-m232-xqch?

3 open source packages ship an affected version, including github.com/cheqd/cheqd-node.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/cheqd/cheqd-node` | Go | All versions | None |
| `github.com/cheqd/cheqd-node` | Go | All versions | 3.1.7 |
| `github.com/cheqd/cheqd-node` | Go | All versions | 3.1.7 |

## How do I fix GHSA-33cr-m232-xqch?

Upgrade github.com/cheqd/cheqd-node to 3.1.7 or later.

## Is GHSA-33cr-m232-xqch being exploited?

There is no known exploitation of GHSA-33cr-m232-xqch in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-33cr-m232-xqch and fix it if it is affected.

What it is: GHSA-33cr-m232-xqch is an unsafe deserialization vulnerability in github.com/cheqd/cheqd-node, published on 11 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-33cr-m232-xqch in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/cheqd/cheqd-node (Go): affected all versions; no fix listed
- github.com/cheqd/cheqd-node (Go): affected all versions; fixed in 3.1.7
- github.com/cheqd/cheqd-node (Go): affected all versions; fixed in 3.1.7

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-33cr-m232-xqch/ (Markdown: https://insights.sbomify.com/GHSA-33cr-m232-xqch/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-33cr-m232-xqch

---
From sbomify Insights: https://insights.sbomify.com/GHSA-33cr-m232-xqch/
Summaries are generated and may contain mistakes; the official description above is the record.