céu pouco nublado
- [USD] USD 73,302.16
- [BRL] BRL 370,542.35 [USD] USD 73,302.16 [GBP] GBP 54,528.53 [EUR] EUR 62,890.62
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.
[28/05/2026 12:46] Petrobras anuncia reajuste nos preços da gasolina para as distribuidoras - G1
[28/05/2026 10:34] Alcolumbre envia à CCJ proposta da oposição alternativa ao fim da 6x1 - CNN Brasil
[28/05/2026 07:42] Fraude no setor de combustíveis: nova operação mira 6 fintechs e cumpre 55 mandados - Revista Oeste
[28/05/2026 08:20] A melhora na avaliação do governo Lula, segundo a pesquisa Meio/Ideia - CartaCapital
[28/05/2026 07:01] Lula vence todos os oponentes no 2º turno, diz Meio/Ideia - Poder360
[27/05/2026 18:38] PF não quer mais negociar com Vorcaro e não dará mais chance para delação - Jovem Pan
[27/05/2026 11:38] Entenda o que é a ‘challenge coin’, moeda que Flávio Bolsonaro ganhou de Trump durante visita - O GLOBO
[28/05/2026 07:28] Como jovem sobreviveu 3 dias à deriva esperando por resgate no litoral de SP - Brasil 247
[28/05/2026 06:52] NASA alerta que novo El Niño lembra episódios intensos do passado - MetSul Meteorologia
[28/05/2026 09:23] Big Techs: Alcolumbre aciona jurídico e avalia suspender decretos de Lula - CNN Brasil