# GHSA-q73f-w3h7-7wcc: Nervos CKB Transaction which calls syscall load_cell_data_hash has nondeterministic result

> Nondeterministic transaction verification in Nervos CKB tx-pool can cause consensus failures or 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-q73f-w3h7-7wcc?

GHSA-q73f-w3h7-7wcc is a 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
Tx-pool verify transaction which inputs' script contains `load_cell_data_hash` is nondeterministic

### Workarounds
Enforce tx-pool ResolvedTrascation inputs' load data is none.

## Which versions are affected by GHSA-q73f-w3h7-7wcc?

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-q73f-w3h7-7wcc?

Upgrade ckb to 0.34.2 or later.

## Is GHSA-q73f-w3h7-7wcc being exploited?

There is no known exploitation of GHSA-q73f-w3h7-7wcc in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-q73f-w3h7-7wcc and fix it if it is affected.

What it is: GHSA-q73f-w3h7-7wcc is a 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-q73f-w3h7-7wcc 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-q73f-w3h7-7wcc/ (Markdown: https://insights.sbomify.com/GHSA-q73f-w3h7-7wcc/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-q73f-w3h7-7wcc

---
From sbomify Insights: https://insights.sbomify.com/GHSA-q73f-w3h7-7wcc/
Summaries are generated and may contain mistakes; the official description above is the record.