# GHSA-p2gm-ffr3-w2xw: Nervos CKB vulnerable to low-resource flood DDoS attacks through network message

> Attackers can cause denial of service in Nervos CKB nodes by sending low-resource flood network messages, requiring configuration changes to mitigate.

- **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:** 8 Feb 2023

## What is GHSA-p2gm-ffr3-w2xw?

GHSA-p2gm-ffr3-w2xw is a denial of service vulnerability in ckb, published on 8 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

### Workarounds
* forbid request genesis through network request
* forbid requesting duplicate data  through network request

## Which versions are affected by GHSA-p2gm-ffr3-w2xw?

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


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

## How do I fix GHSA-p2gm-ffr3-w2xw?

Upgrade ckb to 0.101.4 or later.

## Is GHSA-p2gm-ffr3-w2xw being exploited?

There is no known exploitation of GHSA-p2gm-ffr3-w2xw in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-p2gm-ffr3-w2xw and fix it if it is affected.

What it is: GHSA-p2gm-ffr3-w2xw is a denial of service vulnerability in ckb, published on 8 Feb 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 GHSA-p2gm-ffr3-w2xw in the wild and no public exploit code.

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

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-p2gm-ffr3-w2xw/ (Markdown: https://insights.sbomify.com/GHSA-p2gm-ffr3-w2xw/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-p2gm-ffr3-w2xw

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