nimiq-blockchain is missing a wall-clock upper bound on block timestamps
nimiq core-rs-albatross
nimiq core-rs-albatross
| Product | Affected | Fixed in |
|---|---|---|
| nimiq-blockchain crates.io |
| No fix yet |
nimiq-blockchain provides persistent block storage for Nimiq's Rust implementation. In 1.3.0 and earlier, block timestamp validation enforces that timestamp >= parent.timestamp for non-skip blocks and timestamp == parent.timestamp + MIN_PRODUCER_TIMEOUT for skip blocks, but there is no visible upper bound check against the wall clock. A malicious block-producing validator can set block timestamps arbitrarily far in the future. This directly affects reward calculations via Policy::supply_at() and batch_delay() in blockchain/src/reward.rs, inflating the monetary supply beyond the intended emission schedule.
From the CVE record · GitHub_M
In nimiq-blockchain 1.3.0 and earlier, block timestamp validation has no visible upper bound against the wall clock. A malicious block-producing validator can set timestamps arbitrarily far in the future, inflating monetary supply beyond the intended emission schedule through reward calculations.
Engineers running Nimiq core-rs-albatross with the crates.io nimiq-blockchain package at version 1.3.0 or earlier should check their deployments.