Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2024-8381 is a critical-severity Type Confusion (CWE-843) vulnerability in Mozilla Firefox Esr. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 10% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-8381 is a type confusion vulnerability (CWE-843) that can be triggered when performing a property name lookup on an object used as the `with` environment in the JavaScript engine. It affects Firefox versions prior to 130, Firefox ESR versions prior to 128.2 and 115.15, and Thunderbird versions prior to 128.2 and 115.15.
An unauthenticated remote attacker can exploit the flaw over the network by serving malicious web content or email that causes the browser or client to perform the unsafe lookup, resulting in arbitrary code execution with full impact to confidentiality, integrity, and availability.
Mozilla security advisories MFSA2024-39, MFSA2024-40, MFSA2024-41, and MFSA2024-43, along with the associated Bugzilla entry, direct users to upgrade to the fixed releases to eliminate the issue.
The EPSS score has remained in the 0.11–0.12 range with only a modest peak, indicating moderate but not rapidly escalating exploitation interest.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-49137
Vulnerability Data
A potentially exploitable type confusion could be triggered when looking up a property name on an object being used as the `with` environment. This vulnerability affects Firefox < 130, Firefox ESR < 128.2, Firefox ESR < 115.15, Thunderbird < 128.2,…
more
and Thunderbird < 115.15.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.5.2V3.2.3V15.3.5
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation (including fuzzing and type-aware analysis) directly finds type-confusion flaws before deployment.
Engineering principles can require use of type-safe languages, static typing, and runtime type checks that structurally avoid allocating one type and accessing another.
Memory-protection controls limit the blast radius when a type-confusion access occurs but do not stop the flaw itself.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent type-confusion flaws via safe typing, static analysis, and code review while the control itself addresses many additional weaknesses.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect type-confusion vulnerabilities through fuzzing and static analysis.
Secure SDLC mandates type-safe design and review that can catch type-confusion flaws.
Application security requirements can specify strong typing and interface contracts that reduce type confusion.
Secure architecture principles promote type-safe languages and memory-safety mechanisms that mitigate type confusion.
Secure coding standards directly forbid unsafe type casts and require static-analysis checks for type confusion.