How severe is GHSA-fjj4-2q73-jvgc?

No CVSS score has been assigned to GHSA-fjj4-2q73-jvgc yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-fjj4-2q73-jvgc?

GHSA-fjj4-2q73-jvgc affects the following packages: ckb (crates.io). Ecosystems affected: crates.io.

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

The records we use list no patched version of ckb for GHSA-fjj4-2q73-jvgc. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-fjj4-2q73-jvgc in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ckb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-fjj4-2q73-jvgc if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-fjj4-2q73-jvgc actively exploited in the wild?

No public exploit code has been indexed for GHSA-fjj4-2q73-jvgc yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-fjj4-2q73-jvgc published, and has it been updated?

GHSA-fjj4-2q73-jvgc was published on February 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

Nervos CKB calculation of program load cycles may be missed when executing in resume modeGHSA-fjj4-2q73-jvgc

GHSA-fjj4-2q73-jvgc is a security vulnerability in ckb. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Published

Feb 8, 2023

Updated

Feb 8, 2023

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Feb 8, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀ckb

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`ckb`	≥ 0.100.0	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ckb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of ckb for GHSA-fjj4-2q73-jvgc. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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.

O3 Security · Impact-Aware SCA

Is GHSA-fjj4-2q73-jvgc in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works