nublado
- [USD] USD 65,681.42
- [BRL] BRL 333,175.56 [USD] USD 65,681.42 [GBP] GBP 48,939.03 [EUR] EUR 56,627.83
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.
[03/06/2026 08:45] Brasil, China e Reino Unido: Veja 60 economias que podem ter taxa dos EUA - CNN Brasil
[03/06/2026 11:00] Lula ataca Rubio por tarifaço, diz que vai mandar carta para Trump e ameaça procurar outros parceiros: ‘Eu nem ia ao G7, mas agora vou’ - O Globo
[03/06/2026 05:03] Entenda como deve ser o último dia do julgamento do caso Henry, com os réus Jairinho e Monique Medeiros - O Globo
[02/06/2026 20:01] Senado aprova projeto que dificulta o aborto legal em crianças - CartaCapital
[03/06/2026 05:08] Farra de Vorcaro para autoridades brasileiras com russas e ucranianas em Nova York custou quase R$ 12 milhões - Brasil 247
[03/06/2026 11:03] Greve geral em Portugal paralisa trens, voos e fecha escolas - CNN Brasil
[03/06/2026 10:48] Bicheiro Adilsinho e ex-PM Sem Alma têm prisão decretada por execução de policial penal ligado à máfia do cigarro - Extra online
[02/06/2026 16:17] FAB contradiz influenciador e diz não ter detectado suposto Ovni visto no Paraná - UOL
[03/06/2026 06:45] 53% defendem classificar PCC e CV como “terroristas” - Poder360
[02/06/2026 20:18] Sob protestos, Flávio Bolsonaro recebe título de cidadão honorário de Belo Horizonte - CartaCapital