Fellipe Weno

fweno.onefour.com.br

Current Conditions

São Paulo
nuvens quebradas

18 ℃

87%

Temperatura

Umidade

Fonte: OpenWeatherMap. - 14:30:01

[USD] USD 63,747.70

[BRL] BRL 323,621.59 [USD] USD 63,747.70 [GBP] GBP 47,514.48 [EUR] EUR 55,076.49
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:31:59 up 265 days, 23:03, 5 users, load average: 0.00, 0.00, 0.00

[12/06/2026 05:01] Transações feitas para financiar filme sobre Bolsonaro são investigadas - Valor Econômico

[12/06/2026 08:49] Itália publica anulação de extradição de Zambelli e vê Moraes parcial - Migalhas

[12/06/2026 05:30] Daniela Lima: Alcolumbre sinaliza destravar análise de fim da escala 6x1 semana que vem - UOL Notícias

[11/06/2026 22:03] Waack: Planalto mira ganho eleitoral em embate com Congresso - CNN Brasil

[12/06/2026 01:18] Vorcaro transferiu US$ 30 milhões a Alcolumbre, diz revista - Poder360

[12/06/2026 10:50] Trump acusa Irã de mentir sobre termos de acordo provisório com os EUA - CNN Brasil

[12/06/2026 12:26] Lula lança linha de crédito para compra de motos e bicicletas elétricas por entregadores de app; veja regras - G1

[12/06/2026 09:11] 'Família devastada', lamenta tio de criança morta em acidente com bicicleta elétrica - O Dia

[12/06/2026 11:34] Ciclone começa a se formar e trará vento acima de 100 km/h em mar aberto - MetSul Meteorologia

[11/06/2026 13:21] Desmatamento na Amazônia cai 61,4% em maio de 2026 - Agência Brasil

[CVE-2026-2003] [Modified: 20-02-2026] [Analyzed] [V3.1 S4.3:MEDIUM] Improper validation of type "oidvector" in PostgreSQL allows a database user to disclose a few bytes of server memory. We have not ruled out viability of attacks that arrange for presence of confidential information in disclosed bytes, but they seem unlikely. Versions before PostgreSQL 18.2, 17.8, 16.12, 15.16, and 14.21 are affected.

[CVE-2026-2004] [Modified: 20-02-2026] [Analyzed] [V3.1 S8.8:HIGH] Missing validation of type of input in PostgreSQL intarray extension selectivity estimator function allows an object creator to execute arbitrary code as the operating system user running the database. Versions before PostgreSQL 18.2, 17.8, 16.12, 15.16, and 14.21 are affected.

[CVE-2026-2005] [Modified: 20-02-2026] [Analyzed] [V3.1 S8.8:HIGH] Heap buffer overflow in PostgreSQL pgcrypto allows a ciphertext provider to execute arbitrary code as the operating system user running the database. Versions before PostgreSQL 18.2, 17.8, 16.12, 15.16, and 14.21 are affected.

[CVE-2026-2006] [Modified: 20-02-2026] [Analyzed] [V3.1 S8.8:HIGH] Missing validation of multibyte character length in PostgreSQL text manipulation allows a database user to issue crafted queries that achieve a buffer overrun. That suffices to execute arbitrary code as the operating system user running the database. Versions before PostgreSQL 18.2, 17.8, 16.12, 15.16, and 14.21 are affected.

[CVE-2026-2007] [Modified: 20-02-2026] [Analyzed] [V3.1 S8.2:HIGH] Heap buffer overflow in PostgreSQL pg_trgm allows a database user to achieve unknown impacts via a crafted input string. The attacker has limited control over the byte patterns to be written, but we have not ruled out the viability of attacks that lead to privilege escalation. PostgreSQL 18.1 and 18.0 are affected.

[CVE-2025-70886] [Modified: 18-02-2026] [Analyzed] [V3.1 S7.5:HIGH] An issue in halo v.2.22.4 and before allows a remote attacker to cause a denial of service via a crafted payload to the public comment submission endpoint

[CVE-2026-26216] [Modified: 20-02-2026] [Analyzed] [V3.1 S10.0:CRITICAL] Crawl4AI versions prior to 0.8.0 contain a remote code execution vulnerability in the Docker API deployment. The /crawl endpoint accepts a hooks parameter containing Python code that is executed using exec(). The __import__ builtin was included in the allowed builtins, allowing unauthenticated remote attackers to import arbitrary modules and execute system commands. Successful exploitation allows full server compromise, including arbitrary command execution, file read and write access, sensitive data exfiltration, and lateral movement within internal networks.

[CVE-2026-26217] [Modified: 20-02-2026] [Analyzed] [V3.1 S8.6:HIGH] Crawl4AI versions prior to 0.8.0 contain a local file inclusion vulnerability in the Docker API deployment. The /execute_js, /screenshot, /pdf, and /html endpoints accept file:// URLs, allowing unauthenticated remote attackers to read arbitrary files from the server filesystem. An attacker can access sensitive files such as /etc/passwd, /etc/shadow, application configuration files, and environment variables via /proc/self/environ, potentially exposing credentials, API keys, and internal application structure.

[CVE-2025-55210] [Modified: 27-02-2026] [Analyzed] [V3.1 S7.5:HIGH] FreePBX is an open-source web-based graphical user interface (GUI) that manages Asterisk. Prior to 17.0.5 and 16.0.17, FreePBX module api (PBX API) is vulnerable to privilege escalation by authenticated users with REST/GraphQL API access. This vulnerability allows an attacker to forge a valid JWT with full access to the REST and GraphQL APIs on a FreePBX that they've already connected to, possibly as a lower privileged user. The JWT is signed using the api-oauth.key private key. An attacker can generate their own token if they possess this key (e.g., by accessing an affected instance), and specify any scopes they wish (e.g., rest, gql), bypassing traditional authorization checks. However, FreePBX enforces that the jti (JWT ID) claim must exist in the database (api_access_tokens table in the asterisk MySQL database) in order for the token to be accepted. Therefore, the attacker must know a jti value that already exists on the target instance. This vulnerability is fixed in 17.0.5 and 16.0.17.

[CVE-2025-61879] [Modified: 19-02-2026] [Analyzed] [V3.1 S7.7:HIGH] In Infoblox NIOS through 9.0.7, a High-Privileged User Can Trigger an Arbitrary File Write via the Account Creation Mechanism.

[CVE-2025-61880] [Modified: 19-02-2026] [Analyzed] [V3.1 S8.8:HIGH] In Infoblox NIOS through 9.0.7, insecure deserialization can result in remote code execution.

[CVE-2025-69806] [Modified: 23-02-2026] [Analyzed] [V3.1 S7.5:HIGH] p2r3 bareiron commit: 8e4d4020d contains an Out-of-bounds Read, which allows unauthenticated remote attackers to get relative information leakage via a packet sent to the server

[CVE-2025-69807] [Modified: 23-02-2026] [Analyzed] [V3.1 S7.5:HIGH] p2r3 Bareiron commit: 8e4d4020d is vulnerable to Buffer Overflow, which allows unauthenticated remote attackers to cause a denial of service via a packet sent to the server.

[CVE-2025-70981] [Modified: 18-02-2026] [Analyzed] [V3.1 S9.8:CRITICAL] CordysCRM 1.4.1 is vulnerable to SQL Injection in the employee list query interface (/user/list) via the departmentIds parameter.

[CVE-2026-21434] [Modified: 19-02-2026] [Analyzed] [V3.1 S5.3:MEDIUM] webtransport-go is an implementation of the WebTransport protocol. From 0.3.0 to 0.9.0, an attacker can cause excessive memory consumption in webtransport-go's session implementation by sending a WT_CLOSE_SESSION capsule containing an excessively large Application Error Message. The implementation does not enforce the draft-mandated limit of 1024 bytes on this field, allowing a peer to send an arbitrarily large message payload that is fully read and stored in memory. This allows an attacker to consume an arbitrary amount of memory. The attacker must transmit the full payload to achieve the memory consumption, but the lack of any upper bound makes large-scale attacks feasible given sufficient bandwidth. This vulnerability is fixed in 0.10.0.

[CVE-2026-21435] [Modified: 19-02-2026] [Analyzed] [V3.1 S5.3:MEDIUM] webtransport-go is an implementation of the WebTransport protocol. Prior to v0.10.0, an attacker can cause a denial of service in webtransport-go by preventing or indefinitely delaying WebTransport session closure. A malicious peer can withhold QUIC flow control credit on the CONNECT stream, blocking transmission of the WT_CLOSE_SESSION capsule and causing the close operation to hang. This vulnerability is fixed in v0.10.0.

[CVE-2026-21438] [Modified: 19-02-2026] [Analyzed] [V3.1 S5.3:MEDIUM] webtransport-go is an implementation of the WebTransport protocol. Prior to 0.10.0, an attacker can cause unbounded memory consumption repeatedly creating and closing many WebTransport streams. Closed streams were not removed from an internal session map, preventing garbage collection of their resources. This vulnerability is fixed in v0.10.0.

[CVE-2026-22821] [Modified: 20-02-2026] [Analyzed] [V3.1 S4.9:MEDIUM] mreporting is the more reporting GLPI plugin. Prior to 1.9.4, there is a possible SQL injection on date change. This vulnerability is fixed in 1.9.4.

[CVE-2026-26218] [Modified: 25-02-2026] [Analyzed] [V3.1 S9.8:CRITICAL] newbee-mall includes pre-seeded administrator accounts in its database initialization script. These accounts are provisioned with a predictable default password. Deployments that initialize or reset the database using the provided schema and fail to change the default administrative credentials may allow unauthenticated attackers to log in as an administrator and gain full administrative control of the application.

[CVE-2026-26219] [Modified: 25-02-2026] [Analyzed] [V3.1 S9.1:CRITICAL] newbee-mall stores and verifies user passwords using an unsalted MD5 hashing algorithm. The implementation does not incorporate per-user salts or computational cost controls, enabling attackers who obtain password hashes through database exposure, backup leakage, or other compromise vectors to rapidly recover plaintext credentials via offline attacks.