céu limpo
- [USD] USD 60,731.75
- [BRL] BRL 314,444.70 [USD] USD 60,731.75 [GBP] GBP 45,515.83 [EUR] EUR 52,697.73
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.
[06/06/2026 09:53] UE formaliza restrição a carnes e produtos de origem animal do Brasil - O Globo
[06/06/2026 04:30] Caso Henry: MP recorre do perdão judicial à Monique, alegando que juíza reformulou pergunta ao júri; entenda - O Globo
[05/06/2026 20:48] Diretor da PF é contra classificação de facções como terroristas - Revista Oeste
[06/06/2026 13:03] Vídeo: ponte de R$ 36 milhões desaba e deixa feridos no Acre - CNN Brasil
[06/06/2026 07:26] As eleições que podem fechar 'círculo de fogo' pró-Trump em torno do Brasil - BBC
[06/06/2026 04:00] Empresas brasileiras taxadas agora por Trump têm dificuldades de vender para outros países: veja a diferença do 1º tarifaço - O Globo
[06/06/2026 08:57] Carreta com combustível tomba e provoca bloqueio total da BR-381 - Estado de Minas
[05/06/2026 17:39] Ex-prefeito de cidade no Pará mata a tiros mulher durante assinatura de divórcio - O Globo
[05/06/2026 21:04] Governo prorroga prazo de inscrição do Enem 2026 - Correio do Povo
[06/06/2026 03:34] Parada LGBT+ em SP terá segurança reforçada com mais de 1,5 mil policiais - CNN Brasil