# GO-2023-1860: IBC protocol "Huckleberry" vulnerability in github.com/cosmos/ibc-go

> The IBC protocol vulnerability in the Go library allows attackers to exploit inter-blockchain communication flaws, requiring library upgrades.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Jun 2023

## What is GO-2023-1860?

GO-2023-1860 is a vulnerability in github.com/cosmos/ibc-go/v4, published on 15 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The ibc-go module is affected by the Inter-Blockchain Communication (IBC) protocol "Huckleberry" vulnerability.

## Which versions are affected by GO-2023-1860?

4 open source packages ship an affected version, including github.com/cosmos/ibc-go/v4, github.com/cosmos/ibc-go/v5 and github.com/cosmos/ibc-go/v6.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/cosmos/ibc-go/v4` | Go | All versions | 4.1.3, 4.2.2, 4.3.1, 4.4.1 |
| `github.com/cosmos/ibc-go/v5` | Go | All versions | 5.2.1, 5.3.1 |
| `github.com/cosmos/ibc-go/v6` | Go | All versions | 6.1.1 |
| `github.com/cosmos/ibc-go/v7` | Go | All versions | 7.0.1 |

## How do I fix GO-2023-1860?

Upgrade github.com/cosmos/ibc-go/v4 to a fixed version for your release line: 4.1.3, 4.2.2, 4.3.1 or 4.4.1.

## Is GO-2023-1860 being exploited?

There is no known exploitation of GO-2023-1860 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GO-2023-1860 and fix it if it is affected.

What it is: GO-2023-1860 is a vulnerability in github.com/cosmos/ibc-go/v4, published on 15 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GO-2023-1860 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/cosmos/ibc-go/v4 (Go): affected all versions; fixed in 4.1.3, 4.2.2, 4.3.1, 4.4.1
- github.com/cosmos/ibc-go/v5 (Go): affected all versions; fixed in 5.2.1, 5.3.1
- github.com/cosmos/ibc-go/v6 (Go): affected all versions; fixed in 6.1.1
- github.com/cosmos/ibc-go/v7 (Go): affected all versions; fixed in 7.0.1

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/GO-2023-1860/ (Markdown: https://insights.sbomify.com/GO-2023-1860/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GO-2023-1860

---
From sbomify Insights: https://insights.sbomify.com/GO-2023-1860/
Summaries are generated and may contain mistakes; the official description above is the record.