CVE-2024-6614VulnerabilityPublished 9 Jul 2024Updated 30 Oct 2025

CVE-2024-6614: Mozilla Firefox · Vulnerability

Affects Mozilla FirefoxSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium : upgrade to 128 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

4.3Medium

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

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

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

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

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: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Jul 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 2026-10-26.

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 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 Mozilla Firefox to 128.

Affected software

Product	Affected	Fixed in
Mozilla Firefox	Affected <128	Fixed in 128

AI-suggested

To mitigate CVE-2024-6614, European organizations should prioritize updating Mozilla Firefox and Thunderbird to version 128 or later once official patches are released. If you cannot patch yet, organizations can implement the following measures: 1) Educate users about the risk of interacting with untrusted web content that may contain malicious wasm frames. 2) Employ network-level protections such as web filtering and intrusion detection systems to block or monitor suspicious wasm content. 3) Enhance logging and monitoring to detect anomalies in application behavior that may indicate exploitation attempts. 4) For development and security teams, use alternative debugging tools or browsers unaffected by this vulnerability when analyzing wasm-related issues. 5) Coordinate with Mozilla’s security advisories to apply patches promptly upon release. 6) Conduct internal audits to identify critical systems relying on affected versions and plan for timely upgrades. These targeted actions go beyond generic advice by focusing on controlling wasm content exposure and maintaining robust incident response capabilities.

Description

The frame iterator could get stuck in a loop when encountering certain wasm frames leading to incorrect stack traces. This vulnerability affects Firefox < 128 and Thunderbird < 128.

Impact

For European organizations, the primary impact of CVE-2024-6614 lies in the degradation of debugging and diagnostic capabilities due to incorrect stack traces. This can hinder developers and security teams from accurately tracing errors or malicious activity, potentially delaying incident response and forensic investigations. While the vulnerability does not allow direct compromise of systems or data leakage, the integrity of error reporting is critical for maintaining secure and stable environments. Organizations heavily reliant on Firefox and Thunderbird for daily operations, including government agencies, financial institutions, and large enterprises, may experience reduced effectiveness in troubleshooting and vulnerability management. The absence of known exploits reduces immediate risk, but the potential for future exploitation exists if attackers leverage this flaw to obfuscate their activities. Additionally, user interaction is required, which somewhat limits the attack surface but does not eliminate risk in environments with frequent user engagement with web content.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Oct 2025, 16:43 UTC

WeaknessesCWE-835

Technical details

References

Community reviews

Related threats