# GHSA-29c2-65rj-h343: Nervos CKB Permit load cell data from memory > Faulty nodes reject valid transactions and ban peers, causing network separation and denial of service for the Nervos CKB blockchain. - **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-29c2-65rj-h343? GHSA-29c2-65rj-h343 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 The faulty nodes will reject transactions which calls `load_cell_data` syscall but the input cell is still in the mempool. They also ban other nodes and cause the network separation. ### Patches 0.35.2, 0.36.1, 0.37.1, 0.38.2 ## Which versions are affected by GHSA-29c2-65rj-h343? 10 open source packages ship an affected version, including ckb. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `ckb` | crates.io | From 0.35.0-rc1 | 0.35.2 | | `ckb` | crates.io | From 0.35.0-rc1 | 0.35.2 | | `ckb` | crates.io | From 0.36.0-rc1 | 0.36.1 | | `ckb` | crates.io | From 0.36.0-rc1 | 0.36.1 | | `ckb` | crates.io | From 0.37.0-rc1 | 0.37.1 | | `ckb` | crates.io | From 0.37.0-rc1 | 0.37.1 | | `ckb` | crates.io | From 0.38.0-rc1 | 0.38.2 | | `ckb` | crates.io | From 0.38.0-rc1 | 0.38.2 | | `ckb` | crates.io | From 0.39.0-rc1 | 0.39.0 | | `ckb` | crates.io | From 0.39.0-rc1 | 0.39.0 | ## How do I fix GHSA-29c2-65rj-h343? Upgrade ckb to a fixed version for your release line: 0.35.2, 0.36.1, 0.37.1 or 0.38.2. ## Is GHSA-29c2-65rj-h343 being exploited? There is no known exploitation of GHSA-29c2-65rj-h343 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for GHSA-29c2-65rj-h343 and fix it if it is affected. What it is: GHSA-29c2-65rj-h343 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-29c2-65rj-h343 in the wild and no public exploit code. Affected packages and fixed versions: - ckb (crates.io): affected from 0.35.0-rc1; fixed in 0.35.2 - ckb (crates.io): affected from 0.35.0-rc1; fixed in 0.35.2 - ckb (crates.io): affected from 0.36.0-rc1; fixed in 0.36.1 - ckb (crates.io): affected from 0.36.0-rc1; fixed in 0.36.1 - ckb (crates.io): affected from 0.37.0-rc1; fixed in 0.37.1 - ckb (crates.io): affected from 0.37.0-rc1; fixed in 0.37.1 - ckb (crates.io): affected from 0.38.0-rc1; fixed in 0.38.2 - ckb (crates.io): affected from 0.38.0-rc1; fixed in 0.38.2 - ckb (crates.io): affected from 0.39.0-rc1; fixed in 0.39.0 - ckb (crates.io): affected from 0.39.0-rc1; fixed in 0.39.0 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-29c2-65rj-h343/ (Markdown: https://insights.sbomify.com/GHSA-29c2-65rj-h343/index.md) ``` ## Sources - OSV: https://osv.dev/vulnerability/GHSA-29c2-65rj-h343 --- From sbomify Insights: https://insights.sbomify.com/GHSA-29c2-65rj-h343/ Summaries are generated and may contain mistakes; the official description above is the record.