CVE-2022-32917
Memory Safety in Apple Macos 11.0 – 11.7
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2022-32917 is a high-severity Out-of-bounds Write (CWE-787) vulnerability in Apple Macos. Its CVSS base score is 7.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 8% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.
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-2022-32917 is an out-of-bounds write vulnerability (CWE-787) that was addressed through improved bounds checks. It affects multiple Apple platforms, specifically macOS Monterey prior to version 12.6, iOS and iPadOS prior to 15.7, iOS prior to 16, and macOS Big Sur prior to 11.7. The flaw carries a CVSS score of 7.8 and could allow an application to execute arbitrary code with kernel privileges.
A local attacker who can execute an application on a vulnerable device may exploit the issue to gain arbitrary code execution at kernel level, resulting in complete system compromise without requiring user interaction.
Apple has published fixes in the versions noted above, along with corresponding security advisories that list the affected components and updated builds. Full disclosure entries on public mailing lists reference the same patches and confirm the scope of remediation.
Apple has stated it is aware of reports indicating the vulnerability may have been actively exploited in the wild. The associated EPSS score shows only minor fluctuation between its current value of 0.0092 and peak of 0.0146.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-35983
Vulnerability Data
The issue was addressed with improved bounds checks. This issue is fixed in macOS Monterey 12.6, iOS 15.7 and iPadOS 15.7, iOS 16, macOS Big Sur 11.7. An application may be able to execute arbitrary code with kernel privileges. Apple…
more
is aware of a report that this issue may have been actively exploited..
- CWE(s)
- KEV Date Added
- 14 September 2022
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Out-of-bounds writes that corrupt control flow or inject shellcode are rendered non-executable by the same memory protections.
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 (static analysis, bounds checking, code review) are the primary means of preventing out-of-bounds writes.
Vulnerability scanning and recording can discover out-of-bounds write flaws so they can be remediated.
Patching or replacing vulnerable software directly eliminates known instances of this coding weakness.
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 and prevent out-of-bounds write defects.
Secure development life cycle mandates practices that prevent out-of-bounds writes.
Application security requirements can specify bounds-checking and safe memory handling.
Secure architecture and engineering principles reduce the likelihood of buffer overflows.
Secure coding directly addresses out-of-bounds writes through language choice and coding standards.
Change management can enforce review gates that catch unsafe memory operations before deployment.