How severe is GHSA-r9rv-9mh8-pxf4?

No CVSS score has been assigned to GHSA-r9rv-9mh8-pxf4 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-r9rv-9mh8-pxf4?

GHSA-r9rv-9mh8-pxf4 affects the following packages: ckb (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-r9rv-9mh8-pxf4?

Update ckb to 0.33.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r9rv-9mh8-pxf4 is resolved across your whole dependency graph.

How do I detect GHSA-r9rv-9mh8-pxf4 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-r9rv-9mh8-pxf4 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-r9rv-9mh8-pxf4 actively exploited in the wild?

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

GHSA-r9rv-9mh8-pxf4 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 BlockTimeTooNew should not be considered as invalid blockGHSA-r9rv-9mh8-pxf4

Fix: nervosnetwork/ckb@760d447

GHSA-r9rv-9mh8-pxf4 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

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Feb 2, 2024 · 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

Currently, when a node receives a block in future according to its local wall clock, it will mark the block as invalid and ban the peer.

If the header's timestamp is more than 15 seconds ahead of our current time. In that case, the header may become valid in the future, and we don't want to disconnect a peer merely for serving us one too-far-ahead block header, to prevent an attacker from splitting the network by mining a block right at the 15 seconds boundary.

Patches

Upgrade to v0.33.1 or above.

Workarounds

Don't ban peer serving too-far-ahead block header.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`ckb`	all versions	0.33.1`cargo update -p ckb --precise 0.33.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.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r9rv-9mh8-pxf4 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 Currently, when a node receives a block in future according to its local wall clock, it will mark the block as invalid and ban the peer. If the header's timestamp is more than 15 seconds ahead of our current time. In that case, the header may become valid in the future, and we don't want to disconnect a peer merely for serving us one too-far-ahead block header, to prevent an attacker from splitting the network by mining a block right at the 15 seconds boundary. ### Patches Upgrade to v0.33.1 or above. ### Workarounds Don't ban peer serving too-far-ahead block header.

O3 Security · Impact-Aware SCA

Is GHSA-r9rv-9mh8-pxf4 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works