# GHSA-fjj4-2q73-jvgc: Nervos CKB calculation of program load cycles may be missed when executing in resume mode

> An attacker can cause missed cycle calculations in resume mode, potentially leading to denial of service in Nervos CKB script execution.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Feb 2023

## What is GHSA-fjj4-2q73-jvgc?

GHSA-fjj4-2q73-jvgc 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

### Impact
The calculation of program load cycles may be missed when executing in resume mode. Since the script execution order is now determined, this issue does not cause network splitting.

## Which versions are affected by GHSA-fjj4-2q73-jvgc?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ckb` | crates.io | From 0.100.0 | None |
| `ckb` | crates.io | From 0.100.0 | None |

## How do I fix GHSA-fjj4-2q73-jvgc?

No fix has been published for GHSA-fjj4-2q73-jvgc yet. Limit exposure of the affected software until one is available.

## Is GHSA-fjj4-2q73-jvgc being exploited?

There is no known exploitation of GHSA-fjj4-2q73-jvgc in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-fjj4-2q73-jvgc and fix it if it is affected.

What it is: GHSA-fjj4-2q73-jvgc 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-fjj4-2q73-jvgc in the wild and no public exploit code.

Affected packages and fixed versions:
- ckb (crates.io): affected from 0.100.0; no fix listed
- ckb (crates.io): affected from 0.100.0; no fix listed

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-fjj4-2q73-jvgc/ (Markdown: https://insights.sbomify.com/GHSA-fjj4-2q73-jvgc/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-fjj4-2q73-jvgc

---
From sbomify Insights: https://insights.sbomify.com/GHSA-fjj4-2q73-jvgc/
Summaries are generated and may contain mistakes; the official description above is the record.