GHSA-r9rv-9mh8-pxf4
Nervos CKB BlockTimeTooNew should not be considered as invalid block
GHSA-r9rv-9mh8-pxf4 is a vulnerability with no CVSS score yet in ckb, published February 2, 2024. No source lists public exploit code. Fixed in ckb 0.33.1.
- Severity
- UnratedNo CVSS score yet
- Exploit chance
- UnscoredNo EPSS score yet
- Exploitation
- None knownNot on CISA’s or ENISA’s lists
- Fixed in
0.33.1ckb +1 more
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
What each source reports
GitHub AdvisoriesNo score
Nervos CKB BlockTimeTooNew should not be considered as invalid block
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.
- Record
GHSA-r9rv-9mh8-pxf4- Updated
- 2026-11-02
OSVNo score
Nervos CKB BlockTimeTooNew should not be considered as invalid block
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.
- Record
GHSA-r9rv-9mh8-pxf4- Updated
- 2026-11-02
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.