Fellipe Weno

fweno.onefour.com.br

Current Conditions

São Paulo
chuva fraca

15 ℃

99%

Temperatura

Umidade

Fonte: OpenWeatherMap. - 05:00:02

[USD] USD 62,652.98

[BRL] BRL 324,830.62 [USD] USD 62,652.98 [GBP] GBP 46,813.18 [EUR] EUR 54,259.54
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 - 05:06:52 up 264 days, 13:38, 5 users, load average: 0.04, 0.03, 0.01

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

[10/06/2026 21:53] Senado aprova pauta-bomba que custará R$ 140 bilhões - Poder360

[10/06/2026 13:39] Comissão da Câmara aprova redução da maioridade penal de 18 para 16 anos - O Globo

[10/06/2026 11:20] Nova delação de Vorcaro cita Rueda e integrantes do PT da Bahia - Revista Oeste

[10/06/2026 19:11] Como está a disputa entre Keiko Fujimori e Sánchez entre peruanos de 11 capitais brasileiras - CartaCapital

[10/06/2026 11:34] PEC da autonomia do Banco Central inclui o Pix na Constituição - Poder360

[10/06/2026 19:46] Formação de ciclone afeta três regiões do Brasil nesta quinta-feira - MetSul Meteorologia

[10/06/2026 18:02] Senado aprova Benedito Gonçalves para a Corregedoria do CNJ - Revista Oeste

[10/06/2026 10:13] As intenções de voto para presidente entre evangélicos e católicos, segundo a Quaest - CartaCapital

[10/06/2026 16:14] Deolane e Marcola são denunciados por esquema de lavagem de dinheiro - CNN Brasil

[CVE-2025-13648] [Modified: 17-03-2026] [Analyzed] [V3.1 S6.1:MEDIUM] An attacker with access to the web application ZeusWeb of the provider Microcom (in this case, registration is required) who has the vulnerable software could introduce arbitrary JavaScript by injecting an XSS payload into the ‘Name’ and “Surname” parameters within the ‘My Account’ section at the URL: https://zeus.microcom.es:4040/administracion-estaciones.html resulting in a stored XSS. This issue affects ZeusWeb: 6.1.31.

[CVE-2025-13649] [Modified: 17-03-2026] [Analyzed] [V3.1 S6.1:MEDIUM] An attacker with access to the web application ZeusWeb of the provider Microcom (in this case, registration is not necessary, but the action must be performed) who has the vulnerable software could introduce arbitrary JavaScript by injecting an XSS payload into the ‘Email’ parameters within the ‘Recover password’ section at the URL: https://zeus.microcom.es:4040/index.html?zeus6=true . This issue affects ZeusWeb: 6.1.31.

[CVE-2025-13650] [Modified: 20-03-2026] [Analyzed] [V3.1 S6.1:MEDIUM] An attacker with access to the web application ZeusWeb of the provider Microcom (in this case, registration is not necessary, but the action must be performed) who has the vulnerable software could introduce arbitrary JavaScript by injecting an XSS payload into the ‘Surname’ parameter of the ‘Create Account’ operation at the URL: https://zeus.microcom.es:4040/index.html?zeus6=true . This issue affects ZeusWeb: 6.1.31.

[CVE-2025-13651] [Modified: 26-03-2026] [Analyzed] [V3.1 S7.5:HIGH] Exposure of Sensitive System Information to an Unauthorized Actor vulnerability in Microcom ZeusWeb allows Web Application Fingerprinting of sensitive data. This issue affects ZeusWeb: 6.1.31.

[CVE-2025-12073] [Modified: 13-02-2026] [Analyzed] [V3.1 S4.3:MEDIUM] GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.0 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that, under certain conditions, could have allowed an authenticated user to perform server-side request forgery against internal services by bypassing protections in the Git repository import functionality.

[CVE-2025-12575] [Modified: 13-02-2026] [Analyzed] [V3.1 S5.4:MEDIUM] GitLab has remediated an issue in GitLab EE affecting all versions from 18.0 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that, under certain conditions could have allowed an authenticated user with certain permissions to make unauthorized requests to internal network services through the GitLab server.

[CVE-2025-14560] [Modified: 13-02-2026] [Analyzed] [V3.1 S7.3:HIGH] GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.1 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that, under certain conditions could have allowed an authenticated user to perform unauthorized actions on behalf of another user by injecting malicious content into vulnerability code flow.

[CVE-2025-14592] [Modified: 13-02-2026] [Analyzed] [V3.1 S3.7:LOW] GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.6 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that, under certain conditions could have allowed an authenticated user to perform unauthorized operations by submitting GraphQL mutations through the GLQL API endpoint.

[CVE-2025-14594] [Modified: 13-02-2026] [Analyzed] [V3.1 S3.5:LOW] GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.11 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that, under certain conditions could have allowed an authenticated user to view certain pipeline values by querying the API.

[CVE-2025-7659] [Modified: 13-02-2026] [Analyzed] [V3.1 S8.0:HIGH] GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that could have allowed an unauthenticated user to steal tokens and access private repositories by abusing incomplete validation in the Web IDE.

[CVE-2025-8099] [Modified: 13-02-2026] [Analyzed] [V3.1 S7.5:HIGH] GitLab has remediated an issue in GitLab CE/EE affecting all versions from 10.8 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that, under certain conditions, could have allowed an unauthenticated user to cause denial of service by sending repeated GraphQL queries.

[CVE-2026-0595] [Modified: 12-02-2026] [Analyzed] [V3.1 S7.3:HIGH] GitLab has remediated an issue in GitLab CE/EE affecting all versions from 13.9 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that, under certain conditions could have allowed an authenticated user to add unauthorized email addresses to victim accounts through HTML injection in test case titles.

[CVE-2026-0958] [Modified: 13-02-2026] [Analyzed] [V3.1 S7.5:HIGH] GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.4 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that could have allowed an unauthenticated user to cause denial of service through memory or CPU exhaustion by bypassing JSON validation middleware limits.

[CVE-2026-1080] [Modified: 12-02-2026] [Analyzed] [V3.1 S4.3:MEDIUM] GitLab has remediated an issue in GitLab EE affecting all versions from 16.7 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that, under certain conditions could have allowed an authenticated user to access iteration data from private descendant groups by querying the iterations API endpoint.

[CVE-2026-1094] [Modified: 12-02-2026] [Analyzed] [V3.1 S4.6:MEDIUM] GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.8 before 18.8.4 that could have allowed an authenticated developer to hide specially crafted file changes from the WebUI.

[CVE-2026-1282] [Modified: 12-02-2026] [Analyzed] [V3.1 S3.5:LOW] GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.6 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that could have allowed an authenticated user to inject malicious content into project labels titles.

[CVE-2026-1387] [Modified: 12-02-2026] [Analyzed] [V3.1 S6.5:MEDIUM] GitLab has remediated an issue in GitLab EE affecting all versions from 15.6 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that could have allowed an authenticated user to cause Denial of Service by uploading a malicious file and repeatedly querying it through GraphQl.

[CVE-2026-1456] [Modified: 12-02-2026] [Analyzed] [V3.1 S6.5:MEDIUM] GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 before 18.7.4, and 18.8 before 18.8.4 that could have allowed an unauthenticated user to cause denial of service through CPU exhaustion by submitting specially crafted markdown files that trigger exponential processing in markdown preview.

[CVE-2026-1458] [Modified: 12-02-2026] [Analyzed] [V3.1 S6.5:MEDIUM] GitLab has remediated an issue in GitLab CE/EE affecting all versions from 8.0 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that, under certain conditions could have allowed an unauthenticated user to cause denial of service by uploading malicious files.

[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