# GHSA-wjxc-pjx9-4wvm: Nervos CKB Panic on malformed input

> Remote attackers can crash the Nervos CKB node by sending malformed P2P messages, causing a denial of service.

- **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:** 3 Feb 2024

## What is GHSA-wjxc-pjx9-4wvm?

GHSA-wjxc-pjx9-4wvm is a denial of service vulnerability in ckb, published on 3 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

### Impact
CKB process will panic when received malformed p2p message because of snappy, which is used to compress network messages

### References
https://github.com/BurntSushi/rust-snappy/issues/29

## Which versions are affected by GHSA-wjxc-pjx9-4wvm?

2 open source packages ship an affected version, including ckb.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ckb` | crates.io | All versions | 0.34.2 |
| `ckb` | crates.io | All versions | 0.34.2 |

## How do I fix GHSA-wjxc-pjx9-4wvm?

Upgrade ckb to 0.34.2 or later.

## Is GHSA-wjxc-pjx9-4wvm being exploited?

There is no known exploitation of GHSA-wjxc-pjx9-4wvm in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-wjxc-pjx9-4wvm and fix it if it is affected.

What it is: GHSA-wjxc-pjx9-4wvm is a denial of service vulnerability in ckb, published on 3 Feb 2024. 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-wjxc-pjx9-4wvm in the wild and no public exploit code.

Affected packages and fixed versions:
- ckb (crates.io): affected all versions; fixed in 0.34.2
- ckb (crates.io): affected all versions; fixed in 0.34.2

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-wjxc-pjx9-4wvm/ (Markdown: https://insights.sbomify.com/GHSA-wjxc-pjx9-4wvm/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-wjxc-pjx9-4wvm

---
From sbomify Insights: https://insights.sbomify.com/GHSA-wjxc-pjx9-4wvm/
Summaries are generated and may contain mistakes; the official description above is the record.