Fellipe Weno

fweno.onefour.com.br

Current Conditions

São Paulo
nublado

19 ℃

86%

Temperatura

Umidade

Fonte: OpenWeatherMap. - 13:30:01

[USD] USD 62,582.26

[BRL] BRL 323,005.84 [USD] USD 62,582.26 [GBP] GBP 46,939.83 [EUR] EUR 54,368.59
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 of CScriptCheck functors. Each CScriptCheck holds a pointer to a PrecomputedTransactionData object 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 the PrecomputedTransactionData outlives the CScriptCheck.
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 of PrecomputedTransactionData is destroyed before the CCheckQueueControl.
This is not an issue when the block is valid, as CCheckQueueControl::Wait() will be called before the function returns and the PrecomputedTransactionData gets 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.

dog - 13:55:55 up 264 days, 22:27, 5 users, load average: 0.00, 0.00, 0.00

[11/06/2026 00:03] Congresso não pode criar despesas a Estados e municípios, diz Gilmar - Poder360

[11/06/2026 04:42] Caso Henry Borel: criadora da Lei Maria da Penha critica 'perdão' a Monique Medeiros: 'Desserviço ao feminismo' - BBC

[10/06/2026 20:47] Irã anuncia fechamento do Estreito de Ormuz após ataques dos EUA - CNN Brasil

[11/06/2026 07:12] Keiko Fujimori reassume liderança na apuração de votos no Peru - Folha PE

[11/06/2026 07:55] A vantagem de Lula na disputa com Flávio Bolsonaro em Pernambuco, segundo pesquisa - CartaCapital

[11/06/2026 10:05] NOAA anuncia o começo do El Niño de 2026-2027 - MetSul Meteorologia

[10/06/2026 15:00] Governo Lula registra marca Pix e reforça defesa do sistema após críticas dos EUA - O Globo

[11/06/2026 09:08] Novo ciclone em cinco dias coloca SC em perigo para chuva de até 100 mm em 24h - NSC Total

[11/06/2026 07:02] Big Data: João Campos mantém liderança no 1º e 2 turnos para governo de PE - CNN Brasil

[10/06/2026 19:10] Senado aprova projeto de renegociação de dívidas rurais, visto como ‘pauta-bomba’ pelo governo Lula - Estadão

[CVE-2024-56807] [Modified: 12-02-2026] [Analyzed] [V3.1 S5.5:MEDIUM] An out-of-bounds read vulnerability has been reported to affect Media Streaming add-on. If an attacker gains local network access, they can then exploit the vulnerability to obtain secret data. We have already fixed the vulnerability in the following version: Media Streaming add-on 500.1.1.6 ( 2024/08/02 ) and later

[CVE-2024-56808] [Modified: 12-02-2026] [Analyzed] [V3.1 S7.8:HIGH] A command injection vulnerability has been reported to affect Media Streaming add-on. If an attacker gains local network access who have also gained a user account, they can then exploit the vulnerability to execute arbitrary commands. We have already fixed the vulnerability in the following version: Media Streaming add-on 500.1.1.6 ( 2024/08/02 ) and later

[CVE-2025-30266] [Modified: 11-02-2026] [Analyzed] [V3.1 S6.5:MEDIUM] A NULL pointer dereference vulnerability has been reported to affect Qsync Central. If a remote attacker gains a user account, they can then exploit the vulnerability to launch a denial-of-service (DoS) attack. We have already fixed the vulnerability in the following version: Qsync Central 5.0.0.4 ( 2026/01/20 ) and later

[CVE-2025-30269] [Modified: 11-02-2026] [Analyzed] [V3.1 S8.1:HIGH] A use of externally-controlled format string vulnerability has been reported to affect Qsync Central. If a remote attacker gains a user account, they can then exploit the vulnerability to obtain secret data or modify memory. We have already fixed the vulnerability in the following version: Qsync Central 5.0.0.4 ( 2026/01/20 ) and later

[CVE-2025-30276] [Modified: 11-02-2026] [Analyzed] [V3.1 S8.8:HIGH] An out-of-bounds write vulnerability has been reported to affect Qsync Central. If a remote attacker gains a user account, they can then exploit the vulnerability to modify or corrupt memory. We have already fixed the vulnerability in the following version: Qsync Central 5.0.0.4 ( 2026/01/20 ) and later

[CVE-2025-47205] [Modified: 27-02-2026] [Analyzed] [V3.1 S4.9:MEDIUM] A NULL pointer dereference vulnerability has been reported to affect several QNAP operating system versions. If a remote attacker gains an administrator account, they can then exploit the vulnerability to launch a denial-of-service (DoS) attack. We have already fixed the vulnerability in the following versions: QTS 5.2.8.3332 build 20251128 and later QuTS hero h5.2.8.3321 build 20251117 and later

[CVE-2025-47209] [Modified: 11-02-2026] [Analyzed] [V3.1 S6.5:MEDIUM] A NULL pointer dereference vulnerability has been reported to affect Qsync Central. If a remote attacker gains a user account, they can then exploit the vulnerability to launch a denial-of-service (DoS) attack. We have already fixed the vulnerability in the following version: Qsync Central 5.0.0.4 ( 2026/01/20 ) and later

[CVE-2025-48722] [Modified: 11-02-2026] [Analyzed] [V3.1 S6.5:MEDIUM] A NULL pointer dereference vulnerability has been reported to affect Qsync Central. If a remote attacker gains a user account, they can then exploit the vulnerability to launch a denial-of-service (DoS) attack. We have already fixed the vulnerability in the following version: Qsync Central 5.0.0.4 ( 2026/01/20 ) and later

[CVE-2025-48723] [Modified: 11-02-2026] [Analyzed] [V3.1 S8.1:HIGH] A buffer overflow vulnerability has been reported to affect Qsync Central. If a remote attacker gains a user account, they can then exploit the vulnerability to modify memory or crash processes. We have already fixed the vulnerability in the following version: Qsync Central 5.0.0.4 ( 2026/01/20 ) and later

[CVE-2025-48724] [Modified: 11-02-2026] [Analyzed] [V3.1 S8.1:HIGH] A buffer overflow vulnerability has been reported to affect Qsync Central. If a remote attacker gains a user account, they can then exploit the vulnerability to modify memory or crash processes. We have already fixed the vulnerability in the following version: Qsync Central 5.0.0.4 ( 2026/01/20 ) and later

[CVE-2025-48725] [Modified: 11-02-2026] [Analyzed] [V3.1 S8.1:HIGH] A buffer overflow vulnerability has been reported to affect several QNAP operating system versions. If a remote attacker gains a user account, they can then exploit the vulnerability to modify memory or crash processes. We have already fixed the vulnerability in the following version: QuTS hero h5.3.2.3354 build 20251225 and later

[CVE-2025-52868] [Modified: 11-02-2026] [Analyzed] [V3.1 S8.1:HIGH] A buffer overflow vulnerability has been reported to affect Qsync Central. If a remote attacker gains a user account, they can then exploit the vulnerability to modify memory or crash processes. We have already fixed the vulnerability in the following version: Qsync Central 5.0.0.4 ( 2026/01/20 ) and later

[CVE-2025-52869] [Modified: 12-02-2026] [Analyzed] [V3.1 S8.1:HIGH] A buffer overflow vulnerability has been reported to affect Qsync Central. If a remote attacker gains a user account, they can then exploit the vulnerability to modify memory or crash processes. We have already fixed the vulnerability in the following version: Qsync Central 5.0.0.4 ( 2026/01/20 ) and later

[CVE-2025-52870] [Modified: 12-02-2026] [Analyzed] [V3.1 S8.1:HIGH] A buffer overflow vulnerability has been reported to affect Qsync Central. If a remote attacker gains a user account, they can then exploit the vulnerability to modify memory or crash processes. We have already fixed the vulnerability in the following version: Qsync Central 5.0.0.4 ( 2026/01/20 ) and later

[CVE-2025-53598] [Modified: 12-02-2026] [Analyzed] [V3.1 S6.5:MEDIUM] A NULL pointer dereference vulnerability has been reported to affect Qsync Central. If a remote attacker gains a user account, they can then exploit the vulnerability to launch a denial-of-service (DoS) attack. We have already fixed the vulnerability in the following version: Qsync Central 5.0.0.4 ( 2026/01/20 ) and later

[CVE-2025-54146] [Modified: 12-02-2026] [Analyzed] [V3.1 S6.5:MEDIUM] A NULL pointer dereference vulnerability has been reported to affect Qsync Central. If a remote attacker gains a user account, they can then exploit the vulnerability to launch a denial-of-service (DoS) attack. We have already fixed the vulnerability in the following version: Qsync Central 5.0.0.4 ( 2026/01/20 ) and later

[CVE-2025-54147] [Modified: 12-02-2026] [Analyzed] [V3.1 S6.5:MEDIUM] A NULL pointer dereference vulnerability has been reported to affect Qsync Central. If a remote attacker gains a user account, they can then exploit the vulnerability to launch a denial-of-service (DoS) attack. We have already fixed the vulnerability in the following version: Qsync Central 5.0.0.4 ( 2026/01/20 ) and later

[CVE-2025-54148] [Modified: 12-02-2026] [Analyzed] [V3.1 S6.5:MEDIUM] A NULL pointer dereference vulnerability has been reported to affect Qsync Central. If a remote attacker gains a user account, they can then exploit the vulnerability to launch a denial-of-service (DoS) attack. We have already fixed the vulnerability in the following version: Qsync Central 5.0.0.4 ( 2026/01/20 ) and later

[CVE-2025-54149] [Modified: 12-02-2026] [Analyzed] [V3.1 S5.5:MEDIUM] An uncontrolled resource consumption vulnerability has been reported to affect Qsync Central. If a local attacker gains a user account, they can then exploit the vulnerability to launch a denial-of-service (DoS) attack. We have already fixed the vulnerability in the following version: Qsync Central 5.0.0.4 ( 2026/01/20 ) and later

[CVE-2025-54150] [Modified: 12-02-2026] [Analyzed] [V3.1 S5.5:MEDIUM] An uncontrolled resource consumption vulnerability has been reported to affect Qsync Central. If a local attacker gains a user account, they can then exploit the vulnerability to launch a denial-of-service (DoS) attack. We have already fixed the vulnerability in the following version: Qsync Central 5.0.0.4 ( 2026/01/20 ) and later