Fellipe Weno

fweno.onefour.com.br

Current Conditions

São Paulo
nevoeiro

18 ℃

87%

Temperatura

Umidade

Fonte: OpenWeatherMap. - 08:30:02

[USD] USD 80,610.94

[BRL] BRL 403,522.25 [USD] USD 80,610.94 [GBP] GBP 60,254.58 [EUR] EUR 69,238.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 - 08:53:13 up 237 days, 17:24, 3 users, load average: 0.00, 0.00, 0.00

[15/05/2026 08:13] Cláudio Castro é alvo de operação da PF que mira em fraudes no setor de combustíveis - O GLOBO

[14/05/2026 20:23] Flávio diz que dinheiro pago por Vorcaro foi repassado para fundo gerido por advogado de Eduardo - CartaCapital

[14/05/2026 14:19] Preso pela PF, pai de Vorcaro doou R$ 1 milhão ao partido de Zema em 2022 - BBC

[14/05/2026 07:05] Em reunião em Pequim, Xi alerta Trump sobre risco de conflito por Taiwan - Jovem Pan

[14/05/2026 18:22] STF valida por unanimidade Lei da Igualdade Salarial - Correio Braziliense

[14/05/2026 12:57] Amoêdo diz que Zema foi submisso ao bolsonarismo por 8 anos - Poder360

[15/05/2026 06:22] Explosão em SP: ao menos 50 famílias devem se mudar para imóveis do CDHU - UOL Notícias

[15/05/2026 05:30] A Hora: Governo aposta em saco de bondades e nas maldades do Master - UOL Notícias

[14/05/2026 22:19] El Niño ganha força e Defesa Civil alerta para eventos extremos; veja quando - NSC Total

[14/05/2026 13:05] Petrobras celebra retomada da produção de fertilizantes na Bahia com visita de Lula à Fafen - Brasil 247

[CVE-2026-22907] [Modified: 23-01-2026] [Analyzed] [V3.1 S9.9:CRITICAL] An attacker may gain unauthorized access to the host filesystem, potentially allowing them to read and modify system data.

[CVE-2026-22908] [Modified: 23-01-2026] [Analyzed] [V3.1 S9.1:CRITICAL] Uploading unvalidated container images may allow remote attackers to gain full access to the system, potentially compromising its integrity and confidentiality.

[CVE-2026-22909] [Modified: 23-01-2026] [Analyzed] [V3.1 S7.5:HIGH] Certain system functions may be accessed without proper authorization, allowing attackers to start, stop, or delete installed applications, potentially disrupting system operations.

[CVE-2026-22910] [Modified: 23-01-2026] [Analyzed] [V3.1 S7.5:HIGH] The device is deployed with weak and publicly known default passwords for certain hidden user levels, increasing the risk of unauthorized access. This represents a high risk to the integrity of the system.

[CVE-2026-22911] [Modified: 23-01-2026] [Analyzed] [V3.1 S5.3:MEDIUM] Firmware update files may expose password hashes for system accounts, which could allow a remote attacker to recover credentials and gain unauthorized access to the device.

[CVE-2026-22912] [Modified: 23-01-2026] [Analyzed] [V3.1 S4.3:MEDIUM] Improper validation of a login parameter may allow attackers to redirect users to malicious websites after authentication. This can lead to various risk including stealing credentials from unsuspecting users.

[CVE-2026-22913] [Modified: 23-01-2026] [Analyzed] [V3.1 S4.3:MEDIUM] Improper handling of a URL parameter may allow attackers to execute code in a user's browser after login. This can lead to the extraction of sensitive data.

[CVE-2026-22914] [Modified: 23-01-2026] [Analyzed] [V3.1 S4.3:MEDIUM] An attacker with limited permissions may still be able to write files to specific locations on the device, potentially leading to system manipulation.

[CVE-2026-22915] [Modified: 23-01-2026] [Analyzed] [V3.1 S4.3:MEDIUM] An attacker with low privileges may be able to read files from specific directories on the device, potentially exposing sensitive information.

[CVE-2026-22916] [Modified: 23-01-2026] [Analyzed] [V3.1 S4.3:MEDIUM] An attacker with low privileges may be able to trigger critical system functions such as reboot or factory reset without proper restrictions, potentially leading to service disruption or loss of configuration.

[CVE-2026-22917] [Modified: 23-01-2026] [Analyzed] [V3.1 S4.3:MEDIUM] Improper input handling in a system endpoint may allow attackers to overload resources, causing a denial of service.

[CVE-2026-22918] [Modified: 23-01-2026] [Analyzed] [V3.1 S4.3:MEDIUM] An attacker may exploit missing protection against clickjacking by tricking users into performing unintended actions through maliciously crafted web pages, leading to the extraction of sensitive data.

[CVE-2026-22919] [Modified: 23-01-2026] [Analyzed] [V3.1 S3.8:LOW] An attacker with administrative access may inject malicious content into the login page, potentially enabling cross-site scripting (XSS) attacks, leading to the extraction of sensitive data.

[CVE-2026-0897] [Modified: 23-01-2026] [Analyzed] [V3.1 S7.5:HIGH] Allocation of Resources Without Limits or Throttling in the HDF5 weight loading component in Google Keras 3.0.0 through 3.13.0 on all platforms allows a remote attacker to cause a Denial of Service (DoS) through memory exhaustion and a crash of the Python interpreter via a crafted .keras archive containing a valid model.weights.h5 file whose dataset declares an extremely large shape.

[CVE-2026-22644] [Modified: 29-01-2026] [Analyzed] [V3.1 S5.3:MEDIUM] Certain requests pass the authentication token in the URL as string query parameter, making it vulnerable to theft through server logs, proxy logs and Referer headers, which could allow an attacker to hijack the user's session and gain unauthorized access.

[CVE-2026-22645] [Modified: 29-01-2026] [Analyzed] [V3.1 S5.3:MEDIUM] The application discloses all used components, versions and license information to unauthenticated actors, giving attackers the opportunity to target known security vulnerabilities of used components.

[CVE-2026-22646] [Modified: 29-01-2026] [Analyzed] [V3.1 S4.3:MEDIUM] Certain error messages returned by the application expose internal system details that should not be visible to end users, providing attackers with valuable reconnaissance information (like file paths, database errors, or software versions) that can be used to map the application's internal structure and discover other, more critical vulnerabilities.

[CVE-2025-67081] [Modified: 23-01-2026] [Analyzed] [V3.1 S4.9:MEDIUM] An SQL injection vulnerability in Itflow through 25.06 has been identified in the "role_id" parameter when editing a profile. An attacker with admin account can exploit this issue via blind SQL injection, allowing for the extraction of arbitrary data from the database. The vulnerability arises from insufficient sanitizing on integer parameter.

[CVE-2025-67082] [Modified: 22-01-2026] [Analyzed] [V3.1 S6.5:MEDIUM] An SQL injection vulnerability in InvoicePlane through 1.6.3 has been identified in "maxQuantity" and "minQuantity" parameters when generating a report. An authenticated attacker can exploit this issue via error-based SQL injection, allowing for the extraction of arbitrary data from the database. The vulnerability arises from insufficient sanitizing of single quotes.

[CVE-2025-67083] [Modified: 22-01-2026] [Analyzed] [V3.1 S5.3:MEDIUM] Directory traversal vulnerability in InvoicePlane through 1.6.3 allows unauthenticated attackers to read files from the server. The ability to read files and the file type depends on the web server and its configuration.