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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-hjqq-29pw-96wj 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-hjqq-29pw-96wj?

O3 pinpoints whether GHSA-hjqq-29pw-96wj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

GHSA-hjqq-29pw-96wj

Nervos CKB node panics when processing a block which parent timestamp is too new

Published

Feb 2, 2024

Updated

Feb 2, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Blast Radius

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
🦀crates.io	`ckb`	≥ 0.34.0&&< 0.34.1	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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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
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 pinpoints whether GHSA-hjqq-29pw-96wj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-hjqq-29pw-96wj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 detects GHSA-hjqq-29pw-96wj across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works