céu limpo
- [USD] USD 76,968.27
- [BRL] BRL 389,913.47 [USD] USD 76,968.27 [GBP] GBP 57,680.02 [EUR] EUR 66,168.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.
[17/05/2026 18:13] Fundo investigado pela PF liga Flávio, Eduardo Bolsonaro e Vorcaro - NSC Total
[17/05/2026 15:30] Quaest: 52% são contra redução de penas a envolvidos no 8 de Janeiro - G1
[17/05/2026 16:04] Lula se prepara para reenviar indicação de Messias antes das eleições, mas ministro adota cautela - Estadão
[17/05/2026 14:14] Trump diz para Irã agir rápido "ou não sobrará nada deles" - CNN Brasil
[17/05/2026 21:45] Morre piloto de helicóptero da polícia baleado na testa por fuzil - Estado de Minas
[16/05/2026 19:16] A popularidade de Lula no Datafolha a menos de 5 meses da eleição - CartaCapital
[17/05/2026 16:30] Prédio desaba em Salvador e deixa 3 mortos: veja quem são as vítimas - ND Mais
[17/05/2026 16:03] Motta diz que seguirá regimento da Câmara sobre instauração de CPI do Master - Correio Braziliense
[17/05/2026 08:16] Trump sabe que sou melhor que Bolsonaro, diz Lula ao The Washington Post - CNN Brasil
[18/05/2026 00:05] 'Me fiz de morta', diz mulher que teve mão decepada com foice no Ceará - UOL Notícias