# GHSA-j92c-mmf7-j5x5: Potential inter-blockchain communication (IBC) protocol compromise via "Dragonberry" vulnerability in cheqd

> Attackers can compromise inter-blockchain communication transfers in cheqd nodes, requiring operators to upgrade to the patched version.

- **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:** 18 Oct 2022
- **Also known as:** GO-2022-1066

## What is GHSA-j92c-mmf7-j5x5?

GHSA-j92c-mmf7-j5x5 is a vulnerability in github.com/cheqd/cheqd-node, published on 18 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

### Impact
This vulnerability affects IBC transfers due to a security vulnerability dubbed "Dragonberry" upstream in [Cosmos SDK](https://github.com/cosmos/cosmos-sdk/releases/tag/v0.45.9). The vulnerability could allow malicious attackers to compromise chain-to-chain IBC transfers.

There is no vulnerability in the DID/resource modules for cheqd-node.

### Patches
Node operators are requested to upgrade to [cheqd-node v0.6.9](https://github.com/cheqd/cheqd-node/releases/tag/0.6.9) as soon as possible. Installation instructions are in the release notes. Please do not install any beta/pre-release versions.

### Workarounds
No. The patch takes effect when more than 2/3rds of the voting power of the cheqd network has upgraded to this patch.

An emergency hotfix was released previously under v0.6.8 but this is now deprecated since [Cosmos SDK v0.45.9](https://github.com/cosmos/cosmos-sdk/releases/tag/v0.45.9) officially fixes this upstream.

### References
- [IBC Security Advisory on "Dragonberry"](https://forum.cosmos.network/t/ibc-security-advisory-dragonberry/7702/1) (and [associated security vulnerability "Dragonfruit"](https://forum.cosmos.network/t/cosmos-sdk-security-advisory-dragonfruit/7614))

### For more information
If you have any questions or comments about this advisory:
* Open an issue in [cheqd-node repo](https://github.com/cheqd/cheqd-node/issues)
* Email us at [security-github@cheqd.io](mailto:security-github@cheqd.io)
* Message us on our community [Slack](http://cheqd.link/join-cheqd-slack) or [Discord](http://cheqd.link/discord-github)

## Which versions are affected by GHSA-j92c-mmf7-j5x5?

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 | 0.6.9 |
| `github.com/cheqd/cheqd-node` | Go | All versions | 0.6.9 |
| `github.com/cheqd/cheqd-node` | Go | All versions | 0.6.9 |

## How do I fix GHSA-j92c-mmf7-j5x5?

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

## Is GHSA-j92c-mmf7-j5x5 being exploited?

There is no known exploitation of GHSA-j92c-mmf7-j5x5 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-j92c-mmf7-j5x5 and fix it if it is affected.

What it is: GHSA-j92c-mmf7-j5x5 is a vulnerability in github.com/cheqd/cheqd-node, published on 18 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-j92c-mmf7-j5x5 in the wild and no public exploit code.

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

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-j92c-mmf7-j5x5/ (Markdown: https://insights.sbomify.com/GHSA-j92c-mmf7-j5x5/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-j92c-mmf7-j5x5

---
From sbomify Insights: https://insights.sbomify.com/GHSA-j92c-mmf7-j5x5/
Summaries are generated and may contain mistakes; the official description above is the record.