céu pouco nublado
- [USD] USD 61,370.57
- [BRL] BRL 316,470.91 [USD] USD 61,370.57 [GBP] GBP 45,962.81 [EUR] EUR 53,230.56
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.
[05/06/2026 04:47] PCC e CV designados terroristas: os efeitos no México, Colômbia e Venezuela após governo Trump fazer isso com facções locais - BBC
[04/06/2026 19:45] Gleisi critica Eduardo Bolsonaro após fala sobre Pix e Zelle - Poder360
[05/06/2026 03:37] "Crime doloso contra vida pode ter perdão judicial?", contesta pai de Henry - CNN Brasil
[05/06/2026 09:06] Exército de Israel ordena retirada de moradores do Líbano em meio a ataques - CNN Brasil
[05/06/2026 11:26] Lula tem 47,8% e Flávio, 41,3%, no 2º turno, diz pesquisa - Poder360
[04/06/2026 21:45] Lula diz que vai a Washington negociar, mas precisa das tarifas para sua propaganda - Gazeta do Povo
[05/06/2026 09:44] Justiça manda prender jornalista perseguido por Carla Zambelli - Estadão
[04/06/2026 14:59] Sob pressão e às vésperas da eleição, senadores recuam em apoio a PEC da oposição sobre a 6×1 - CartaCapital
[05/06/2026 02:15] Inscrições para o Enem terminam nesta sexta-feira (5); saiba como fazer - CNN Brasil
[05/06/2026 07:05] Onde pode chover muito no Sul do Brasil no começo do El Niño - MetSul Meteorologia