Fellipe Weno

fweno.onefour.com.br

Current Conditions

São Paulo
céu limpo

17 ℃

82%

Temperatura

Umidade

Fonte: OpenWeatherMap. - 23:00:02

[USD] USD 81,164.64

[BRL] BRL 406,326.44 [USD] USD 81,164.64 [GBP] GBP 60,715.13 [EUR] EUR 69,681.63
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 - 23:23:08 up 237 days, 7:54, 3 users, load average: 0.00, 0.01, 0.00

[14/05/2026 18:45] Flávio diz que dinheiro pago por Vorcaro para filme foi repassado por meio de fundo de advogado de Eduardo - O Globo

[14/05/2026 18:42] Caminhão desgovernado mata três pessoas no Rio de Janeiro; veja vídeo - CNN Brasil

[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 13:38] Projeto que torna Fábio Porchat ‘persona non grata’ no Rio avança na Assembleia - CartaCapital

[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

[14/05/2026 18:01] EL Niño deve estar formado em junho e NOAA eleva para alerta risco de formação do fenômeno - Climatempo

[14/05/2026 12:55] Trump diz que Xi Jinping ofereceu ajuda para mediar conflito com Irã - CNN Brasil

[14/05/2026 12:30] Hantavírus: OMS confirma oito casos de cepa que causou surto em navio - Agência Brasil

[14/05/2026 19:51] Na China, Trump diz que campanha militar no Irã deve continuar - CNN Brasil

[CVE-2025-13455] [Modified: 23-02-2026] [Analyzed] [V3.1 S7.8:HIGH] A vulnerability was reported in ThinkPlus configuration software that could allow a local authenticated user to bypass ThinkPlus device authentication and enroll an untrusted fingerprint.

[CVE-2025-14448] [Modified: 24-02-2026] [Analyzed] [V3.1 S5.4:MEDIUM] The WP-Members Membership Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Multiple Checkbox and Multiple Select user profile fields in all versions up to, and including, 3.5.4.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

[CVE-2025-14457] [Modified: 23-01-2026] [Analyzed] [V3.1 S3.7:LOW] The Drag and Drop Multiple File Upload for Contact Form 7 plugin for WordPress is vulnerable to unauthorized modification of data due to a missing ownership check in the dnd_codedropz_upload_delete() function in all versions up to, and including, 1.3.9.2. This makes it possible for unauthenticated attackers to delete arbitrary uploaded files when the "Send attachments as links" setting is enabled.

[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.