céu limpo
- [USD] USD 59,852.29
- [BRL] BRL 311,968.08 [USD] USD 59,852.29 [GBP] GBP 45,061.71 [EUR] EUR 52,588.97
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.
[01/07/2026 11:56] Leonardo Sakamoto: Flávio se cala diante de nova onda de ataques a Michelle Bolsonaro - UOL Notícias
[01/07/2026 12:04] EUA sancionam duas pessoas e três empresas brasileiras por suposta ligação com o PCC - G1
[30/06/2026 19:07] Nova audiência de conciliação sobre greve de rodoviários no Rio é convocada - CNN Brasil
[01/07/2026 11:44] Operação mira pessoas ligadas a Sóstenes, líder do PL na Câmara - Poder360
[01/07/2026 07:00] As intenções de voto para presidente no primeiro turno, segundo nova pesquisa AtlasIntel - CartaCapital
[01/07/2026 11:27] Sargento diz à PCDF que retirou arma de Bolsonaro com aval de Michelle - Revista Oeste
[01/07/2026 10:12] Alcolumbre defende redução da jornada sem transição em reunião com centrais sindicais - G1
[01/07/2026 08:39] Advogado e esposa são mortos a facadas em apartamento em BH - Migalhas
[01/07/2026 11:32] Procuradoria da Itália pede rejeição da extradição de Carla Zambelli - UOL Notícias
[01/07/2026 11:09] Alerta vermelho coloca 400 cidades em zona de "grande perigo" por chuva de 100 mm e alagamentos - NSC Total