Skip to content
Fencer Intel
medium —

GHSA-r9rv-9mh8-pxf4 json

Nervos CKB BlockTimeTooNew should not be considered as invalid block

published 2y ago modified 2y ago

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

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.

Patch / fix

  • crates.io ckb 0.33.1

Is GHSA-r9rv-9mh8-pxf4 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
crates.io ckb
<0.33.1
0.33.1

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.