nublado
- [USD] USD 62,782.91
- [BRL] BRL 325,526.23 [USD] USD 62,782.91 [GBP] GBP 47,007.26 [EUR] EUR 54,896.93
Price index provided by blockchain.info. - After Bitcoin Core 0.14.0 and before Bitcoin Core 29.0, validating a specially-crafted block may cause the node to access previously freed memory.
During validation, necessary data required for checking inputs for each transaction is pre-calculated and cached. For specially crafted invalid blocks, it was possible for this data to be destroyed while it was still being accessed by a background validation thread. An attacker capable of mining a block with sufficient proof-of-work could have exploited this to crash victim nodes. Because of the nature of use-after-free bugs, it is possible that the crash could have been used for remote code execution, though constraints on the input (block) data make this unlikely.
This issue is considered High severity.
Details
By default, script validation for new blocks is dispatched to background threads via a vector ofCScriptCheckfunctors. Each CScriptCheck holds a pointer to aPrecomputedTransactionDataobject which stores some data needed by each input in the transaction. Because it stores a pointer and not the data itself, care must be taken to ensure that thePrecomputedTransactionDataoutlives theCScriptCheck.
The script checks lifetime is enforced by an RAII class,CCheckQueueControl. However, the control is intantiated before the precomputed transaction data. Because local objects in C++ are destructed in reverse order of construction, this means the vector ofPrecomputedTransactionDatais destroyed before theCCheckQueueControl.
This is not an issue when the block is valid, asCCheckQueueControl::Wait()will be called before the function returns and thePrecomputedTransactionDatagets destroyed. However, in case of an early return (when a separate check fails) a background script thread may read the precomputed transaction data after it was destroyed. An attacker could exploit this to crash victim nodes at the expense of a valid PoW at tip.
Attribution
Cory Fields (MIT DCI) discovered this vulnerability and responsibly disclosed it in a detailed report containing a proof of concept for reproduction and a proposed mitigation.
Timeline
- 2024-11-02 Cory Fields privately reports the bug
- 2024-11-06 Pieter Wuille pushes a covert fix to already open PR #31112 which works around the issue by removing the early returns
- 2024-12-03 PR #31112 is merged
- 2025-04-12 Bitcoin Core version 29.0 is released with a fix
- 2026-04-19 The last vulnerable Bitcoin Core version (28.x) goes end of life
- 2026-05-05 Public disclosure.
[04/07/2026 17:14] Pivô da briga entre Flávio e Michelle, vereadora do Ceará diz que não vai alimentar conflitos e reforça apoio a senador - O GLOBO
[05/07/2026 00:12] Datafolha: aprovação da gestão Tarcísio permanece 45% em SP - G1
[04/07/2026 16:59] Moraes manda apreender 11 armas de Bolsonaro; leia a lista - Poder360
[04/07/2026 14:53] Líderes estrangeiros parabenizam EUA pelos 250 anos da independência - CNN Brasil
[04/07/2026 17:14] Calor extremo nos EUA impacta comemorações do 4 de julho e cancela eventos - CNN Brasil
[04/07/2026 20:07] Mbappé marca, França vence Paraguai em 'jogo de Libertadores' e vai às quartas da Copa - ESPN Brasil
[04/07/2026 09:14] Ônibus que levava romeiros tomba em Canindé e deixa duas mulheres mortas - O POVO
[04/07/2026 14:38] Mãe de Eliza Samúdio fala sobre sumiço de ex-mulher do goleiro Bruno - CNN Brasil
[04/07/2026 12:28] Flávio Bolsonaro viaja aos EUA neste sábado e diz que defenderá o Pix - Correio Braziliense
[04/07/2026 17:34] Morre Waldemar Borges, marido da ministra Luciana Santos - Poder360