CVE-2024-27796
Apple Macos 12.0 – 12.7.5
Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2024-27796 is a high-severity Improperly Controlled Sequential Memory Allocation (CWE-1325) vulnerability in Apple Macos. Its CVSS base score is 7.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 18th 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-6 (Resource Availability) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-24989
Vulnerability Data
The issue was addressed with improved checks. This issue is fixed in iOS 16.7.8 and iPadOS 16.7.8, iOS 17.5 and iPadOS 17.5, macOS Monterey 12.7.5, macOS Sonoma 14.5, macOS Ventura 13.6.7. An attacker may be able to elevate privileges.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V2.4.1V13.1.2V13.2.6
Mitigating Controls (NIST 800-53 r5) AI
SC-6 directly enforces resource quotas and priority allocations that stop unbounded sequential memory requests from exhausting the system.
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 require developers to enforce total memory limits during sequential allocations.
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 can detect unbounded allocation patterns, but removing the weakness does not fulfill testing obligations.
Secure development life cycle includes resource-management requirements that can prevent uncontrolled per-object allocations.
Secure architecture principles can mandate bounded resource usage, but eliminating this CWE does not address broader architectural controls.
Secure coding standards can require explicit limits on memory per object, yet fixing the weakness alone does not satisfy the full control.
Capacity management directly limits total memory consumption across objects, mitigating unbounded sequential allocations.