nublado
- [USD] USD 63,855.79
- [BRL] BRL 328,959.49 [USD] USD 63,855.79 [GBP] GBP 48,251.29 [EUR] EUR 55,659.90
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.
[20/06/2026 15:57] No caminho do Brasil, Holanda atropela Suécia com shows de Brobbey e Gakpo - CNN Brasil
[20/06/2026 12:05] Datafolha 2º turno: Lula tem 47%, e Flávio Bolsonaro, 43% - G1
[20/06/2026 13:10] Governo suspeita de ataque hacker coordenado em alertas de "misantropia" - Poder360
[20/06/2026 14:13] Irã diz ter fechado estreito de Ormuz; EUA negam - Poder360
[19/06/2026 19:31] Vorcaro marcou encontro com Jaques Wagner e disponibilizou avião para senador, indicam diálogos - Estadão
[20/06/2026 13:01] Meloni chama ataques de Trump de 'sem sentido' e provoca após ele falar que sua popularidade está baixa: 'Se concentre na sua' - G1
[20/06/2026 12:28] Rope jump: Outros três suspeitos são presos por morte de jovem em SP - CNN Brasil
[20/06/2026 11:06] Acidente com mais de 10 veículos provoca morte e bloqueia totalmente a BR-262 em MG - R7
[20/06/2026 14:30] Líder do Vox chama Moraes de 'delinquente' e diz que Eduardo sofreu 'golpe judicial' - Revista Oeste
[20/06/2026 08:14] Paraná recebe alerta verdadeiro de tempestades com ventos de até 100 km/h em 69 cidades; veja onde e a previsão do tempo - G1