nublado
- [USD] USD 62,672.05
- [BRL] BRL 325,875.85 [USD] USD 62,672.05 [GBP] GBP 47,481.66 [EUR] EUR 55,132.91
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.
[23/06/2026 16:29] Justiça dos EUA permite entrada da AGU em processo contra Moraes - Poder360
[23/06/2026 21:05] Planalto se prepara para receber mais denúncias contra ‘República da Bahia’ e blindar Lula - Estadão
[23/06/2026 18:35] MEC publica desempenho de escolas no Enem de 2025; saiba como consultar - CNN Brasil
[23/06/2026 14:26] Resultado oficial do 2º turno da Colômbia é quase idêntico à contagem inicial que deu vitória a Espriella, diz órgão eleitoral - G1
[23/06/2026 14:46] Trump compartilha texto que aponta eleição no Brasil como seu próximo 'teste' na América Latina - CartaCapital
[23/06/2026 11:24] Flávio Bolsonaro pede espaço em audiência nos EUA para falar de tarifas - Correio Braziliense
[23/06/2026 15:24] Banco Digimais, de Edir Macedo, replicou 'modus operandi' do Master, diz PF - Valor Econômico
[23/06/2026 16:50] Lula cria plataforma para coibir roubos de celulares e vendas ilegais - Agência Brasil
[23/06/2026 16:43] Casa da família de Vorcaro é roubada em MG; ladrão leva relógio de R$ 1 mi - CNN Brasil
[23/06/2026 16:23] Michelle Bolsonaro volta a criticar Ciro Gomes, e André Fernandes rebate: 'Ela faz o que quiser' - Diário do Nordeste