CVE Vulnerabilities

CVE-2025-4087

Out-of-bounds Read

Published: Apr 29, 2025 | Modified: May 09, 2025
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
7.6 MODERATE
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:H
Ubuntu
MEDIUM

A vulnerability was identified in Thunderbird where XPath parsing could trigger undefined behavior due to missing null checks during attribute access. This could lead to out-of-bounds read access and potentially, memory corruption. This vulnerability affects Firefox < 138, Firefox ESR < 128.10, Thunderbird < 138, and Thunderbird < 128.10.

Weakness

The product reads data past the end, or before the beginning, of the intended buffer.

Affected Software

Name Vendor Start Version End Version
Firefox Mozilla * 128.10 (excluding)
Firefox Mozilla * 138.0 (excluding)
Thunderbird Mozilla * 128.10.0 (excluding)
Thunderbird Mozilla * 138.0 (excluding)
Red Hat Enterprise Linux 7 Extended Lifecycle Support RedHat firefox-0:128.10.0-1.el7_9 *
Red Hat Enterprise Linux 8 RedHat firefox-0:128.10.0-1.el8_10 *
Red Hat Enterprise Linux 9 RedHat firefox-0:128.10.0-1.el9_5 *
Red Hat Enterprise Linux 9 RedHat thunderbird-0:128.10.0-1.el9_5 *
Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions RedHat firefox-0:128.10.0-1.el9_0 *
Red Hat Enterprise Linux 9.2 Extended Update Support RedHat firefox-0:128.10.0-1.el9_2 *
Red Hat Enterprise Linux 9.4 Extended Update Support RedHat firefox-0:128.10.0-1.el9_4 *
Firefox Ubuntu focal *
Firefox Ubuntu upstream *
Mozjs102 Ubuntu esm-apps/noble *
Mozjs102 Ubuntu jammy *
Mozjs102 Ubuntu noble *
Mozjs115 Ubuntu devel *
Mozjs115 Ubuntu noble *
Mozjs115 Ubuntu oracular *
Mozjs115 Ubuntu plucky *
Mozjs52 Ubuntu esm-infra/bionic *
Mozjs52 Ubuntu focal *
Mozjs68 Ubuntu focal *
Mozjs78 Ubuntu jammy *
Mozjs91 Ubuntu jammy *
Thunderbird Ubuntu focal *
Thunderbird Ubuntu jammy *
Thunderbird Ubuntu upstream *

Potential Mitigations

  • Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
  • When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
  • Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
  • To reduce the likelihood of introducing an out-of-bounds read, ensure that you validate and ensure correct calculations for any length argument, buffer size calculation, or offset. Be especially careful of relying on a sentinel (i.e. special character such as NUL) in untrusted inputs.

References