Nimiq Block
Approved changes feed: RSS · Atom
cpe:2.3:a:nimiq:nimiq-block:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Nimiq (a6c6d398-2780-5e77-a82f-ca37478d870d) |
|---|---|
| Product | Nimiq Block (02d9877f-0e90-5c76-b208-8b373a1b2cb4) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-33471 |
vulnerable | 2026-06-08 07:59:10.144357 |
nimiq-block has skip block quorum bypass via out-of-range BitSet indices & u16 truncation
CRITICAL (9.6)
nimiq-block contains block primitives to be used in Nimiq's Rust implementation. `SkipBlockProof::verify` computes its quorum check using `BitSet.len()`, then iterates `BitSet` indices and casts each `usize` index to `u16` (`slot as u16`) for slot lookup. Prior to version 1.3.0, if an attacker can get a `SkipBlockProof` verified where `MultiSignature.signers` contains out-of-range indices spaced by 65536, these indices inflate `len()` but collide onto the same in-range `u16` slot during aggregation. This makes it possible for a malicious validator with far fewer than `2f+1` real signer slots to pass skip block proof verification by multiplying a single BLS signature by the same factor. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available.
Published: 2026-04-22T19:13:04.687Z
Updated: 2026-04-23T14:15:20.570Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.