GHSA-4wf3-5qj9-368v: IBC-Go: Non-deterministic JSON Unmarshalling of IBC Acknowledgement can result in a chain halt
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Fixed version: github.com/cosmos/ibc-go (Go) 7.10.0; github.com/cosmos/ibc-go/v2 (Go) 7.10.0; github.com/cosmos/ibc-go/v3 (Go) 7.10.0.
Low priority for now. Upgrade to github.com/cosmos/ibc-go (Go) 7.10.0; github.com/cosmos/ibc-go/v2 (Go) 7.10.0; github.com/cosmos/ibc-go/v3 (Go) 7.10.0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: OSV
Name: ISA-2025-001: Non-deterministic JSON Unmarshalling of IBC Acknowledgement can result in a chain halt Component: IBC-Go Criticality: High (Considerable Impact; Likely Likelihood per [ACMv1.2](https://github.com/interchainio/security/blob/main/resources/CLASSIFICATION_MATRIX.md)) Affected versions: IBC-Go >= v7; Earlier IBC-Go versions MAY also be affected. Affected users: Validators, Full nodes, IBC Middleware authors ### Description An issue was discovered in IBC-Go's deserialization of acknowledgements 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. The following patch is in addition to the previous patch which now extends the same protection to all applications beyond transfer. ### Patches The new IBC-Go releases below address this issue: * [v7.10.0](https://github.com/cosmos/ibc-go/releases/tag/v7.10.0) * [v8.7.0](https://github.com/cosmos/ibc-go/releases/tag/v8.7.0) ### Workarounds To prevent this state from being introduced to a chain, it is possible to permission Channel Opening as a workaround. ### Notes on Re-Release This is an extension of the previous patch, please update to the latest patch to get full coverage against the reported issue. #### Is this state breaking? This patch is not state breaking unless an exploit is submitted before the patch is applied across the network in which case the chain will halt just as if it was unpatched. Thus, you can safely apply this patch in a rolling manner and encourage validators to patch as soon as possible in order to prevent any chain halts (and we've already cut new versions of these for you). #### Testing we have done to gain more confidence in this release * In addition to testing ibc-go, we also did the following: * Tested PFM v7 and v8 after bumping dependencies * Tested ibc-hooks v7 and v8 after bumping dependencies * Ran a patched node on Cosmos Hub Mainnet and triggered failing and successful transactions that used PFM * Ran a patched node on Osmosis mainnet and triggered failing and successful transactions that used ibc-hooks This is a more thorough process than before, so we have higher confidence. This issue was reported to the Cosmos Bug Bounty Program by swelf19 on HackerOne on February 18, 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 IBC-Go [repository](https://github.com/cosmos/ibc-go/security/advisories/GHSA-4wf3-5qj9-368v).
- Published
- Mar 12, 2025
- Updated
- Mar 18, 2025
- EPSS
- —
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| Go | github.com/cosmos/ibc-go | pkg:golang/github.com/cosmos/ibc-go |
| Go | github.com/cosmos/ibc-go/v8 | pkg:golang/github.com/cosmos/ibc-go/v8 |
| Go | github.com/cosmos/ibc-go/v2 | pkg:golang/github.com/cosmos/ibc-go/v2 |
| Go | github.com/cosmos/ibc-go/v3 | pkg:golang/github.com/cosmos/ibc-go/v3 |
| Go | github.com/cosmos/ibc-go/v4 | pkg:golang/github.com/cosmos/ibc-go/v4 |
| Go | github.com/cosmos/ibc-go/v5 | pkg:golang/github.com/cosmos/ibc-go/v5 |
| Go | github.com/cosmos/ibc-go/v6 | pkg:golang/github.com/cosmos/ibc-go/v6 |
| Go | github.com/cosmos/ibc-go/v7 | pkg:golang/github.com/cosmos/ibc-go/v7 |
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | github.com/cosmos/ibc-go | from 0 | — |
| Go | github.com/cosmos/ibc-go | before 7.10.0 | 7.10.0 |
| Go | github.com/cosmos/ibc-go/v2 | from 0 | — |
| Go | github.com/cosmos/ibc-go/v2 | before 7.10.0 | 7.10.0 |
| Go | github.com/cosmos/ibc-go/v3 | from 0 | — |
| Go | github.com/cosmos/ibc-go/v3 | before 7.10.0 | 7.10.0 |
| Go | github.com/cosmos/ibc-go/v4 | from 0 | — |
| Go | github.com/cosmos/ibc-go/v4 | before 7.10.0 | 7.10.0 |
| Go | github.com/cosmos/ibc-go/v5 | from 0 | — |
| Go | github.com/cosmos/ibc-go/v5 | before 7.10.0 | 7.10.0 |
| Go | github.com/cosmos/ibc-go/v6 | from 0 | — |
| Go | github.com/cosmos/ibc-go/v6 | before 7.10.0 | 7.10.0 |
| Go | github.com/cosmos/ibc-go/v7 | before 7.10.0 | 7.10.0 |
| Go | github.com/cosmos/ibc-go/v8 | from 8.0.0-alpha.1 · before 8.7.0 | 8.7.0 |
Same product
Go: all recordsOther highest-scoring records for the same primary product.
- GO-2025-3517Non-deterministic JSON Unmarshalling of IBC Acknowledgement can result in a chain halt in github.com/cosmos/ibc-go0Monitor
- GO-2025-3494IBC-Go has Non-deterministic JSON Unmarshalling of IBC Acknowledgement in github.com/cosmos/ibc-go0Monitor
- GHSA-jg6f-48ff-5xrwIBC-Go has Non-deterministic JSON Unmarshalling of IBC Acknowledgement0Monitor
Published before and after this one in the same product
- ← EarlierGO-2024-2694May 20, 2024 · Potential Reentrancy using Timeout Callbacks in ibc-hooks in github.com/cosmos/ibc-go0Monitor
- ← EarlierGO-2024-2874May 23, 2024 · Inter-Blockchain Communication (IBC) protocol "Huckleberry" vulnerability in github.com/cosmos/ibc-go0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go:github.com/cosmos/ibc-go | 7.10.0 | Package registry (OSV) |
| Go:github.com/cosmos/ibc-go/v2 | 7.10.0 | Package registry (OSV) |
| Go:github.com/cosmos/ibc-go/v3 | 7.10.0 | Package registry (OSV) |
| Go:github.com/cosmos/ibc-go/v4 | 7.10.0 | Package registry (OSV) |
| Go:github.com/cosmos/ibc-go/v5 | 7.10.0 | Package registry (OSV) |
| Go:github.com/cosmos/ibc-go/v6 | 7.10.0 | Package registry (OSV) |
| Go:github.com/cosmos/ibc-go/v7 | 7.10.0 | Package registry (OSV) |
| Go:github.com/cosmos/ibc-go/v8 | 8.7.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- Fix✗ → ✓
- CVSS9.5 → —
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.