GHSA-r9rv-9mh8-pxf4

Source
https://github.com/advisories/GHSA-r9rv-9mh8-pxf4
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2024/02/GHSA-r9rv-9mh8-pxf4/GHSA-r9rv-9mh8-pxf4.json
Published
2024-02-02T22:23:07Z
Modified
2024-02-02T22:23:07Z
Details

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.

References

Affected packages

crates.io / ckb

Package

Name
ckb

Affected ranges

Type
SEMVER
Events
Introduced
0The exact introduced commit is unknown
Fixed
0.33.1

Database specific

{
    "last_known_affected_version_range": "<= 0.33.0"
}