Skip to main content
CVE-2024-6612VulnerabilityPublished Updated

CVE-2024-6612: Mozilla Firefox · Information Exposure

Affects Mozilla FirefoxSource CVE Database V5

0

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

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 42% 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:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Jul 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Upgrade Mozilla Firefox to 128.

Affected software

ProductAffectedFixed in
Mozilla FirefoxAffected
  • <128
Fixed in
  • 128

AI-suggested

To mitigate CVE-2024-6612, European organizations should prioritize updating Mozilla Firefox and Thunderbird to version 128 or later once the patches are released, as this will directly address the DNS prefetch leakage issue. If you cannot patch yet, organizations can reduce risk by disabling DNS prefetching in Firefox and Thunderbird settings (e.g., setting 'network.dns.disablePrefetch' to true in about:config) to prevent automatic DNS queries triggered by console links. Additionally, restricting access to developer tools or limiting the use of developer consoles in managed environments can reduce exposure. Network-level monitoring and filtering of suspicious DNS queries related to CSP violation domains may help detect or block potential information leaks. Security teams should also educate users about the risks of visiting untrusted websites that may cause CSP violations and monitor browser update advisories from Mozilla. Incorporating CSP violation monitoring and logging at the web application level can help detect attempts to bypass security policies without relying solely on browser console data.

Description

CSP violations generated links in the console tab of the developer tools, pointing to the violating resource. This caused a DNS prefetch which leaked that a CSP violation happened. This vulnerability affects Firefox < 128 and Thunderbird < 128.

References

Community reviews

Loading reviews…