CVE-2024-4778
Mozilla Firefox ≤ 126.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2024-4778 is a critical-severity Improper Handling of Overlap Between Protected Memory Ranges (CWE-1260) vulnerability in Mozilla Firefox. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Process Injection (T1055); ranked at the 36th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SC-39 (Process Isolation) and SI-16 (Memory Protection) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-44371
Vulnerability Data
Memory safety bugs present in Firefox 125. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code. This vulnerability affects Firefox < 126.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Process isolation depends on correct non-overlapping memory protection domains.
Memory protection mechanisms must correctly handle ranges to block unauthorized execution or access.
Access enforcement directly stops bypass of memory protections that overlapping ranges would enable.
Isolating security functions requires non-overlapping protected memory ranges to avoid bypass.
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 development practices directly prevent flawed memory-range overlap logic in kernels and hypervisors.
Vulnerability identification can surface overlap defects after they are introduced but does not stop them at design time.
Enforcing access-control policy can include memory-range permissions, yet the weakness is an implementation flaw inside that enforcement.
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 and acceptance can detect overlap issues but does not itself prevent them.
Secure system architecture and engineering principles require explicit memory-range separation and protection mechanisms that directly prevent overlapping protected regions.
Secure coding standards mandate checks for address-range overlap and proper memory-protection configuration, mitigating the weakness at implementation time.
Information access restriction policies rely on correct memory protection; eliminating overlap strengthens enforcement but does not define the policy.