How severe is GHSA-hjqq-29pw-96wj?

No CVSS score has been assigned to GHSA-hjqq-29pw-96wj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hjqq-29pw-96wj?

GHSA-hjqq-29pw-96wj affects the following packages: ckb (crates.io), ckb (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-hjqq-29pw-96wj?

Update ckb to 0.33.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hjqq-29pw-96wj is resolved across your whole dependency graph.

How do I detect GHSA-hjqq-29pw-96wj 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-hjqq-29pw-96wj if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-hjqq-29pw-96wj actively exploited in the wild?

No public exploit code has been indexed for GHSA-hjqq-29pw-96wj 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-hjqq-29pw-96wj published, and has it been updated?

GHSA-hjqq-29pw-96wj was published on February 2, 2024. 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 node panics when processing a block which parent timestamp is too newGHSA-hjqq-29pw-96wj

Fix: nervosnetwork/ckb@ae3c791

GHSA-hjqq-29pw-96wj is a security vulnerability in ckb. A fix is available for ckb — see the affected versions and patch details below.

Published

Feb 2, 2024

Updated

Feb 2, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Feb 2, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

🦀ckb🦀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

Adversary can initiate DOS attack by broadcasting two consecutive blocks with timestamps in the future.

Patches

Please upgrade to v0.34.1

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`ckb`	≥ 0.33.0&&< 0.33.2	0.33.2`cargo update -p ckb --precise 0.33.2`
🦀crates.io	`ckb`	≥ 0.34.0&&< 0.34.1	0.34.1`cargo update -p ckb --precise 0.34.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.33.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hjqq-29pw-96wj is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

### Impact Adversary can initiate DOS attack by broadcasting two consecutive blocks with timestamps in the future. ### Patches Please upgrade to v0.34.1

O3 Security · Impact-Aware SCA

Is GHSA-hjqq-29pw-96wj in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works