Fellipe Weno

fweno.onefour.com.br

Current Conditions

São Paulo
nuvens quebradas

19 ℃

81%

Temperatura

Umidade

Fonte: OpenWeatherMap. - 14:00:01

[USD] USD 67,351.93

[BRL] BRL 338,921.66 [USD] USD 67,351.93 [GBP] GBP 50,012.18 [EUR] EUR 57,920.84
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 - 14:03:58 up 255 days, 22:35, 4 users, load average: 0.02, 0.02, 0.00

[02/06/2026 11:23] Governo convoca reunião de emergência para discutir novo tarifaço dos EUA - CNN Brasil

[02/06/2026 10:01] Médico diz que mulher atacada por tubarão no Recife já saiu do mar sem a perna - O Globo

[02/06/2026 11:59] 'Mamãe, o Jairo me empurrou e eu caí da cama', diz Monique ao relatar conversa com Henry - O Globo

[02/06/2026 07:00] As intenções de voto de Lula e Flávio Bolsonaro em Mato Grosso, segundo Real Time Big Data - CartaCapital

[02/06/2026 04:04] Mercado terá de se adequar, diz Lewandowski sobre caso PCC/CV - Poder360

[02/06/2026 12:07] Análise: Novo tarifaço de Trump deve desfazer ajuda a Flávio Bolsonaro com visita à Casa Branca - Valor Econômico

[02/06/2026 09:26] Quem eram os cinco estudantes mortos em acidente com van em GO - Metrópoles

[02/06/2026 07:29] Corpo achado em Ilhabela é de jovem que sumiu em moto aquática, afirma Marinha - Jovem Pan

[01/06/2026 22:54] Flávio nega ter pedido dinheiro a Vorcaro e diz que Zema se precipitou - CNN Brasil

[01/06/2026 20:33] Trump expressou raiva em ligação com Netanyahu sobre planos para o Líbano - CNN Brasil

[CVE-2026-24071] [Modified: 11-02-2026] [Analyzed] [V3.1 S7.8:HIGH] It was found that the XPC service offered by the privileged helper of Native Access uses the PID of the connecting client to verify its code signature. This is considered insecure and can be exploited by PID reuse attacks. The connection handler function uses _xpc_connection_get_pid(arg2) as argument for the hasValidSignature function. This value can not be trusted since it is vulnerable to PID reuse attacks.

[CVE-2025-14914] [Modified: 12-02-2026] [Analyzed] [V3.1 S7.6:HIGH] IBM WebSphere Application Server Liberty 17.0.0.3 through 26.0.0.1 could allow a privileged user to upload a zip archive containing path traversal sequences resulting in an overwrite of files leading to arbitrary code execution.

[CVE-2025-15395] [Modified: 11-02-2026] [Analyzed] [V3.1 S4.3:MEDIUM] IBM Jazz Foundation 7.0.3 through 7.0.3 iFix019 and 7.1.0 through 7.1.0 iFix005 is vulnerable to access control violations that allows the users to view or access/perform actions beyond their expected capability.

[CVE-2025-47358] [Modified: 11-02-2026] [Analyzed] [V3.1 S7.8:HIGH] Memory Corruption when user space address is modified and passed to mem_free API, causing kernel memory to be freed inadvertently.

[CVE-2025-47359] [Modified: 11-02-2026] [Analyzed] [V3.1 S7.8:HIGH] Memory Corruption when multiple threads simultaneously access a memory free API.

[CVE-2025-47363] [Modified: 11-02-2026] [Analyzed] [V3.1 S6.8:MEDIUM] Memory corruption when calculating oversized partition sizes without proper checks.

[CVE-2025-47364] [Modified: 11-02-2026] [Analyzed] [V3.1 S6.8:MEDIUM] Memory corruption while calculating offset from partition start point.

[CVE-2025-47366] [Modified: 11-02-2026] [Analyzed] [V3.1 S7.1:HIGH] Cryptographic issue when a Trusted Zone with outdated code is triggered by a HLOS providing incorrect input.

[CVE-2025-47397] [Modified: 11-02-2026] [Analyzed] [V3.1 S7.8:HIGH] Memory Corruption when initiating GPU memory mapping using scatter-gather lists due to unchecked IOMMU mapping errors.

[CVE-2025-47398] [Modified: 11-02-2026] [Analyzed] [V3.1 S7.8:HIGH] Memory Corruption while deallocating graphics processing unit memory buffers due to improper handling of memory pointers.

[CVE-2025-47399] [Modified: 11-02-2026] [Analyzed] [V3.1 S7.8:HIGH] Memory Corruption while processing IOCTL call to update sensor property settings with invalid input parameters.

[CVE-2025-47402] [Modified: 11-02-2026] [Analyzed] [V3.1 S6.5:MEDIUM] Transient DOS when processing a received frame with an excessively large authentication information element.

[CVE-2026-0631] [Modified: 06-02-2026] [Analyzed] [V3.1 S8.0:HIGH] An OS Command Injection vulnerability in TP-Link Archer BE230 v1.2(vpn modules) allows an adjacent authenticated attacker to execute arbitrary code. Successful exploitation could allow an attacker to gain full administrative control of the device, resulting in severe compromise of configuration integrity, network security, and service availability. This CVE covers one of multiple distinct OS command injection issues identified across separate code paths. Although similar in nature, each instance is tracked under a unique CVE ID.This issue affects Archer BE230 v1.2 < 1.2.4 Build 20251218 rel.70420.

[CVE-2026-22221] [Modified: 06-02-2026] [Analyzed] [V3.1 S8.0:HIGH] An OS Command Injection vulnerability in TP-Link Archer BE230 v1.2(vpn modules) allows adjacent authenticated attacker execute arbitrary code. Successful exploitation could allow an attacker to gain full administrative control of the device, resulting in severe compromise of configuration integrity, network security, and service availability. This CVE covers one of multiple distinct OS command injection issues identified across separate code paths. Although similar in nature, each instance is tracked under a unique CVE ID.This issue affects Archer BE230 v1.2 < 1.2.4 Build 20251218 rel.70420.

[CVE-2026-22222] [Modified: 06-02-2026] [Analyzed] [V3.1 S8.0:HIGH] An OS Command Injection vulnerability in TP-Link Archer BE230 v1.2(web modules) allows adjacent authenticated attacker to execute arbitrary code. Successful exploitation could allow an attacker to gain full administrative control of the device, resulting in severe compromise of configuration integrity, network security, and service availability. This CVE covers one of multiple distinct OS command injection issues identified across separate code paths. Although similar in nature, each instance is tracked under a unique CVE ID.This issue affects Archer BE230 v1.2 < 1.2.4 Build 20251218 rel.70420.

[CVE-2026-22223] [Modified: 06-02-2026] [Analyzed] [V3.1 S8.0:HIGH] An OS Command Injection vulnerability in TP-Link Archer BE230 v1.2(vpn modules) allows adjacent authenticated attacker execute arbitrary code. Successful exploitation could allow an attacker to gain full administrative control of the device, resulting in severe compromise of configuration integrity, network security, and service availability. This CVE covers one of multiple distinct OS command injection issues identified across separate code paths. Although similar in nature, each instance is tracked under a unique CVE ID.This issue affects Archer BE230 v1.2 < 1.2.4 Build 20251218 rel.70420.

[CVE-2026-22224] [Modified: 06-02-2026] [Analyzed] [V3.1 S7.2:HIGH] A command injection vulnerability may be exploited after the admin's authentication in the cloud communication interface on the TP-Link Archer BE230 v1.2. Successful exploitation could allow an attacker to gain full administrative control of the device, resulting in severe compromise of configuration integrity, network security, and service availability. This CVE covers one of multiple distinct OS command injection issues identified across separate code paths. Although similar in nature, each instance is tracked under a unique CVE ID. This issue affects Archer BE230 v1.2 < 1.2.4 Build 20251218 rel.70420.

[CVE-2026-22226] [Modified: 06-02-2026] [Analyzed] [V3.1 S7.2:HIGH] A command injection vulnerability may be exploited after the admin's authentication in the VPN server configuration module on the TP-Link Archer BE230 v1.2. Successful exploitation could allow an attacker to gain full administrative control of the device, resulting in severe compromise of configuration integrity, network security, and service availability. This CVE covers one of multiple distinct OS command injection issues identified across separate code paths. Although similar in nature, each instance is tracked under a unique CVE ID. This issue affects Archer BE230 v1.2 < 1.2.4 Build 20251218 rel.70420.

[CVE-2026-22227] [Modified: 06-02-2026] [Analyzed] [V3.1 S7.2:HIGH] A command injection vulnerability may be exploited after the admin's authentication via the configuration backup restoration function of the TP-Link Archer BE230 v1.2. Successful exploitation could allow an attacker to gain full administrative control of the device, resulting in severe compromise of configuration integrity, network security, and service availability. This CVE covers one of multiple distinct OS command injection issues identified across separate code paths. Although similar in nature, each instance is tracked under a unique CVE ID. This issue affects Archer BE230 v1.2 < 1.2.4 Build 20251218 rel.70420.

[CVE-2025-12679] [Modified: 03-03-2026] [Analyzed] [V3.1 S6.5:MEDIUM] A vulnerability in Brocade SANnav before 2.4.0b prints the Password-Based Encryption (PBE) key in plaintext in the system audit log file. The vulnerability could allow a remote authenticated attacker with access to the audit logs to access the pbe key. Note: The vulnerability is only triggered during a migration and not in a new installation. The system audit logs are accessible only to a privileged user on the server. These audit logs are the local server VM’s audit logs and are not controlled by SANnav. These logs are only visible to the server admin of the host server and are not visible to the SANnav admin or any SANnav user.