VulnerabilityPublished 23 Jan 2024Updated 30 May 2025

CVE-2024-0741: Mozilla Firefox · Out of Bounds Write in ANGLE

Affects Mozilla FirefoxSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium · fixed in 122 : update Mozilla Firefox when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 2.1% chance of exploitation in 30 days – higher than 82% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 122, 115.7

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade the Debian to 122 (debian/firefox package) or 115.7 (debian/thunderbird package).

Affected software

Product	Affected	Fixed in
Debiandebian/firefox`pkg:deb/debian/firefox`Other threats	Affected <122	Fixed in 122
Debiandebian/thunderbird`pkg:deb/debian/thunderbird`Other threats	Affected <115.7	Fixed in 115.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should prioritize updating Mozilla Firefox and Thunderbird to versions 122 and 115.7 respectively, or later, as soon as official patches are released. If you cannot patch yet, organizations can mitigate risk by implementing the following measures: 1) Restrict use of Firefox and Thunderbird to trusted sites and email sources, employing web filtering and email security gateways to block malicious content. 2) Employ endpoint protection solutions capable of detecting anomalous memory corruption behaviors or crashes related to ANGLE. 3) Educate users about the risks of interacting with suspicious web content or email attachments to reduce the likelihood of triggering the vulnerability. 4) Consider disabling or limiting hardware acceleration or ANGLE usage in Firefox settings as a temporary workaround, if feasible, to reduce attack surface. 5) Monitor application crash logs and security telemetry for signs of exploitation attempts. 6) Maintain robust backup and incident response plans to quickly recover from potential denial-of-service or compromise incidents. These targeted mitigations go beyond generic advice by focusing on the specific attack vectors and technical characteristics of this vulnerability.

Description

An out of bounds write in ANGLE could have allowed an attacker to corrupt memory leading to a potentially exploitable crash. This vulnerability affects Firefox < 122, Firefox ESR < 115.7, and Thunderbird < 115.7.

Impact

For European organizations, this vulnerability poses a risk primarily to users of affected Mozilla products, especially Firefox and Thunderbird, which are widely used across enterprises and public sectors. The out-of-bounds write can cause denial of service through application crashes, disrupting business operations, communications, and access to web resources. Although the vulnerability does not directly compromise confidentiality or integrity, the potential for memory corruption could be leveraged in targeted attacks to execute arbitrary code, especially in environments where users interact with untrusted web content or email attachments. This could lead to further compromise of endpoints, lateral movement, or data exfiltration. Organizations relying on Firefox ESR for stability and security updates may be particularly impacted if patches are not applied promptly. Additionally, sectors such as government, finance, healthcare, and critical infrastructure in Europe, which often use Firefox and Thunderbird for secure communications, may face increased risk from exploitation attempts. The requirement for user interaction means that phishing or social engineering could be vectors for triggering the vulnerability, emphasizing the need for user awareness and technical controls.

CWE-787Out-of-bounds Write (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #5
The product writes data past the end, or before the beginning, of the intended buffer.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Jul 2025, 19:41 UTC

WeaknessesCWE-787

Technical details

References

Community reviews

Related threats