How severe is GHSA-9mfc-chwf-7whf?

No CVSS score has been assigned to GHSA-9mfc-chwf-7whf yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-9mfc-chwf-7whf?

GHSA-9mfc-chwf-7whf affects the following packages: ckb (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-9mfc-chwf-7whf?

Update ckb to 0.43.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9mfc-chwf-7whf is resolved across your whole dependency graph.

How do I detect GHSA-9mfc-chwf-7whf 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-9mfc-chwf-7whf 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-9mfc-chwf-7whf actively exploited in the wild?

No public exploit code has been indexed for GHSA-9mfc-chwf-7whf 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-9mfc-chwf-7whf published, and has it been updated?

GHSA-9mfc-chwf-7whf 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

ckb: Large dep group requires a lot of resources to process but the cost to commit the transaction is very lowGHSA-9mfc-chwf-7whf

GHSA-9mfc-chwf-7whf is a security vulnerability in ckb. A fix is available for ckb — see the affected versions and patch details below.

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

When a transaction contains a dep group with many cells, the resources required to process it are not linear to the transaction size nor spent script cycles.

Patches

In 0.43.3, nodes drop the transactions relayed to them when they contain a dep group with more than 64 cells. They do not ban peers who send them such transactions.

In 0.100, the consensus disallow transactions using a dep group with more than 64 cells. Peers relaying such transaction must be banned. Blocks committing such transactions must be rejected.

Affected Packages

1 total 1 fixed

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

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.43.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9mfc-chwf-7whf 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.

Frequently Asked Questions

### Impact When a transaction contains a dep group with many cells, the resources required to process it are not linear to the transaction size nor spent script cycles. ### Patches In 0.43.3, nodes drop the transactions relayed to them when they contain a dep group with more than 64 cells. They do not ban peers who send them such transactions. In 0.100, the consensus disallow transactions using a dep group with more than 64 cells. Peers relaying such transaction must be banned. Blocks committing such transactions must be rejected.

O3 Security · Impact-Aware SCA

Is GHSA-9mfc-chwf-7whf in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works