Описание
nimiq-transaction: Panic via HistoryTreeProof length mismatch
Impact
HistoryTreeProof::verify panics on a malformed proof where history.len() != positions.len() due to assert_eq!(history.len(), positions.len()).
The proof object is derived from untrusted p2p responses (ResponseTransactionsProof.proof) and is therefore attacker-controlled at the network boundary until validated. A malicious peer could trigger a crash by returning a crafted inclusion proof with a length mismatch.
Patches
The patch for this vulnerability is included as part of v1.3.0.
Workarounds
No known workarounds know.
Ссылки
- https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-264v-m8fm-76jm
- https://nvd.nist.gov/vuln/detail/CVE-2026-34067
- https://github.com/nimiq/core-rs-albatross/pull/3659
- https://github.com/nimiq/core-rs-albatross/commit/6ff0800e8e031363e787c827d8d033e5694e4e6a
- https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0
Пакеты
nimiq-transaction
<= 0.2.0
Отсутствует
Связанные уязвимости
nimiq-transaction provides the transaction primitive to be used in Nimiq's Rust implementation. Prior to version 1.3.0, `HistoryTreeProof::verify` panics on a malformed proof where `history.len() != positions.len()` due to `assert_eq!(history.len(), positions.len())`. The proof object is derived from untrusted p2p responses (`ResponseTransactionsProof.proof`) and is therefore attacker-controlled at the network boundary until validated. A malicious peer could trigger a crash by returning a crafted inclusion proof with a length mismatch. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available.