How severe is GHSA-7fw6-6mfj-g3q2?

No CVSS score has been assigned to GHSA-7fw6-6mfj-g3q2 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-7fw6-6mfj-g3q2?

GHSA-7fw6-6mfj-g3q2 affects the following packages: ckb (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-7fw6-6mfj-g3q2?

Update ckb to 0.101.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7fw6-6mfj-g3q2 is resolved across your whole dependency graph.

How do I detect GHSA-7fw6-6mfj-g3q2 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-7fw6-6mfj-g3q2 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.

How does O3 Security protect against GHSA-7fw6-6mfj-g3q2?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-7fw6-6mfj-g3q2 can be triaged on real exposure rather than presence alone.

Is GHSA-7fw6-6mfj-g3q2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-7fw6-6mfj-g3q2 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-7fw6-6mfj-g3q2 published, and has it been updated?

GHSA-7fw6-6mfj-g3q2 was published on November 2, 2022. 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

GHSA-7fw6-6mfj-g3q2 — ckb

Fix: nervosnetwork/ckb#1646

GHSA-7fw6-6mfj-g3q2 is a security vulnerability in ckb. A fix is available for ckb — see the affected versions and patch details below.

ckb: Transaction header_deps validation issue (network forking)

Published

Nov 2, 2022

Updated

Nov 2, 2022

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 2, 2022 · 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

fn HeaderChecker#check_valid skipped main chain checking after this PR: https://github.com/nervosnetwork/ckb/pull/1646/files#diff-c4e017b67c1b3005ca0c446a9b0879571aa36a858b1f7ddd1b9328a884e3214bR171-R176

It will cause network forking if one transaction is using a forked block header which is not exists in local node's storage.

Patches

0.101.1 and later versions

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`ckb`	all versions	0.101.1`cargo update -p ckb --precise 0.101.1`

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.
Fix
Update ckb to 0.101.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7fw6-6mfj-g3q2 is resolved across your whole dependency graph.
Workarounds
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-7fw6-6mfj-g3q2 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-7fw6-6mfj-g3q2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact fn `HeaderChecker#check_valid` skipped main chain checking after this PR: https://github.com/nervosnetwork/ckb/pull/1646/files#diff-c4e017b67c1b3005ca0c446a9b0879571aa36a858b1f7ddd1b9328a884e3214bR171-R176 It will cause network forking if one transaction is using a forked block header which is not exists in local node's storage. ### Patches 0.101.1 and later versions

O3 Security · Impact-Aware SCA

Is GHSA-7fw6-6mfj-g3q2 in your dependencies?

O3 Security finds GHSA-7fw6-6mfj-g3q2 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works