céu limpo
- [USD] USD 61,911.22
- [BRL] BRL 321,291.79 [USD] USD 61,911.22 [GBP] GBP 46,347.91 [EUR] EUR 54,074.00
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.
[03/07/2026 07:09] Operação da PF prende secretária alvo de sanção dos EUA por suspeita de ligação com PCC e mais 6 pessoas; empresário está foragido - G1
[02/07/2026 17:53] Lula critica família Bolsonaro por “entreguismo” aos EUA - Poder360
[03/07/2026 04:00] Especialistas levantam dúvidas sobre o número de mortos na Venezuela - CNN Brasil
[03/07/2026 04:30] Governo do Rio tinha funcionários fantasmas em todos os órgãos públicos; conheça quem são os suspeitos - O GLOBO
[02/07/2026 11:27] Michelle Bolsonaro sinaliza desistência do Senado e amplia crise no PL - CartaCapital
[02/07/2026 21:18] Primo que indicou diarista que matou casal de idosos se sente 'culpado' - UOL Notícias
[03/07/2026 05:30] Ministro de Lula contraria Banco Mundial ao propor imposto do pecado ‘light’ - Estadão
[03/07/2026 06:58] Concurso da Dataprev tem edital publicado com quase 2 mil vagas em sete capitais - JC Concursos
[02/07/2026 21:32] Em agendas pelo Ceará, Lula faz entregas e critica oposição ao lado de Camilo e Elmano - Diário do Nordeste
[03/07/2026 06:35] Motorista atropela homem em avenida, abandona carro e foge em BH - G1