CVE-2024-8382
Mozilla Firefox Esr vulnerability
- Published3 Sept 2024
Description
Internal browser event interfaces were exposed to web content when privileged EventHandler listener callbacks ran for those events. Web content that tried to use those interfaces would not be able to use them with elevated privileges, but their presence would indicate certain browser features had been used, such as when a user opened the Dev Tools console. This vulnerability affects Firefox < 130, Firefox ESR < 128.2, Firefox ESR < 115.15, Thunderbird < 128.2, and Thunderbird < 115.15.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HAffected products
Remediation
References
- https://bugzilla.mozilla.org/show_bug.cgi?id=1906744
- https://lists.debian.org/debian-lts-announce/2024/09/msg00012.html
- https://lists.debian.org/debian-lts-announce/2024/09/msg00025.html
- https://www.mozilla.org/security/advisories/mfsa2024-39/
- https://www.mozilla.org/security/advisories/mfsa2024-40/
- https://www.mozilla.org/security/advisories/mfsa2024-41/
- https://www.mozilla.org/security/advisories/mfsa2024-43/
- https://www.mozilla.org/security/advisories/mfsa2024-44/
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2024-8382 being actively exploited?
CVE-2024-8382 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.60%.
How severe is CVE-2024-8382?
CVE-2024-8382 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 0.60% probability of exploitation.
Which products are affected by CVE-2024-8382?
Affected products include Mozilla Firefox, Mozilla Firefox Esr.
How do I fix CVE-2024-8382?
Upgrade affected software to a fixed version, for example Mozilla Firefox 130.0, Mozilla Firefox Esr 128.2 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2024-8382 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.