céu limpo
- [USD] USD 63,232.88
- [BRL] BRL 329,089.17 [USD] USD 63,232.88 [GBP] GBP 47,328.04 [EUR] EUR 54,753.35
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.
[08/06/2026 18:37] Eleição no Peru: Siga a reta final da apuração em tempo real - CNN Brasil
[08/06/2026 23:18] Nunes Marques acata pedido de Flávio Bolsonaro e suspende divulgação de pesquisa eleitoral - Valor Econômico
[08/06/2026 20:22] Atenção para virada radical de tempo em SP - Climatempo
[08/06/2026 17:58] O que se sabe sobre os casos adversos de vacina do Butantan - Poder360
[08/06/2026 10:30] Após alerta de Trump, Irã anuncia 'interrupção' de ataques contra Israel - Correio Braziliense
[08/06/2026 19:07] PF manifesta incômodo com conteúdo da delação de Vorcaro - Revista Oeste
[08/06/2026 00:00] Comissão da Câmara vota redução da maioridade penal e amplia pressão sobre o governo na segurança pública - O Globo
[08/06/2026 13:20] Alckmin anuncia R$ 35 bilhões em crédito para tratores e caminhões - Brasil 247
[08/06/2026 10:24] Flávio Bolsonaro sobre veto à carne: ‘Problema do Lula que vou resolver’ - Estado de Minas
[08/06/2026 14:34] Janja rebate Silas Malafaia após crítica à encontro da primeira-dama com evangélicas: 'Insignificante é ele' - O Globo