céu limpo
- [USD] USD 73,732.70
- [BRL] BRL 371,891.79 [USD] USD 73,732.70 [GBP] GBP 54,822.32 [EUR] EUR 63,267.52
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.
[31/05/2026 19:28] João Fonseca vence Casper Ruud e segue fazendo história em Roland Garros - CNN Brasil
[31/05/2026 18:59] Primeiros resultados de eleição na Colômbia tem Espriella na frente - CNN Brasil
[31/05/2026 03:00] 6x1: Oposição quer debate sobre transição e insistirá em texto alternativo - CNN Brasil
[31/05/2026 17:13] Caso Henry: pai de Jairinho critica ex-namoradas do filho que relataram agressões e fala sobre últimos momentos com o menino: 'Pedi a Deus que ele voltasse' - O Globo
[30/05/2026 15:55] Após saída de Pacheco, PT de Minas abre debate sobre candidatura própria ao governo - CartaCapital
[31/05/2026 06:49] Decisão de Trump sobre PCC e CV 'põe Lula em situação desconfortável na segurança, mas impacto eleitoral deve ser limitado', diz analista - BBC
[31/05/2026 16:12] Criança é mordida por tubarão na Praia de Piedade, em Jaboatão dos Guararapes - Folha PE
[31/05/2026 13:46] Diácono repreende público após tumulto entre apoiadores de Ciro e Elmano em Barbalha; veja vídeo - O POVO
[31/05/2026 13:48] Cleitinho rebate proposta de Zema para formados em federais: ‘políticos que devem ser taxados' - O TEMPO
[31/05/2026 16:30] BH ganha novo parque de 30 mil m² na região Centro-Sul; saiba onde - O TEMPO