nuvens dispersas
- [USD] USD 80,852.32
- [BRL] BRL 397,073.80 [USD] USD 80,852.32 [GBP] GBP 59,716.95 [EUR] EUR 68,821.25
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.
[11/05/2026 23:18] Explosão em SP: Sabesp e Comgás vão pagar R$ 2 mil a cidadãos afetados - CNN Brasil
[11/05/2026 15:28] STF deve validar Lei da Dosimetria mesmo após suspensão por Moraes - CartaCapital
[12/05/2026 05:10] Em ano eleitoral, Nunes Marques no TSE anima o PL e acende alerta no PT - CNN Brasil
[12/05/2026 06:30] Internet sob domínio do crime: exploração ilegal de sinal já atinge 37 cidades do Rio em meio a disputa de traficantes e milicianos - Extra online
[11/05/2026 13:14] Kakay deixa defesa de Ciro Nogueira no caso Banco Master - Poder360
[12/05/2026 08:08] VÍDEO: No dia mais frio ano, geada cobre cidades de SC após madrugada com -7°C - ND Mais
[12/05/2026 08:18] PF mira contratos da Secretaria estadual de Agricultura, Pecuária e Abastecimento com suspeita de fraude de R$ 200 milhões - O Globo
[12/05/2026 07:42] Pesquisa mostra a disputa pela presidência entre os eleitores do Mato Grosso do Sul; veja os números - CartaCapital
[12/05/2026 06:01] Pressionado, Lula lança seu 4º plano para segurança pública - Poder360
[12/05/2026 07:43] PF mira facções e cumpre 71 mandados de prisão em 16 estados - Correio Braziliense