Nervos CKB BlockTimeTooNew should not be considered as invalid block
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
### 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.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | ckb (crates.io) | before 0.33.1 | 0.33.1 | Patch available | GHSA-r9rv-9mh8-pxf4 |
- ckb (crates.io) Vendor— Affected before 0.33.1 Fixed in 0.33.1 Patch available GHSA-r9rv-9mh8-pxf4
Remediation
- Fix · GHSA-r9rv-9mh8-pxf4 ckb (crates.io) Fixed in 0.33.1 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-r9rv-9mh8-pxf4
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences