Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2022-32894 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 13% 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.
An out-of-bounds write vulnerability addressed through improved bounds checking affects Apple iOS, iPadOS, and macOS Monterey. The flaw is present in versions prior to iOS 15.6.1, iPadOS 15.6.1, and macOS Monterey 12.5.1, and it carries a CVSS 3.1 score of 7.8 under CWE-787.
A local attacker can exploit the issue by supplying a malicious application that triggers the out-of-bounds write. Successful exploitation grants the application arbitrary code execution with kernel privileges; the attack requires user interaction to open or install the application.
Apple security updates HT213412 and HT213413, along with corresponding Full Disclosure mailings, direct administrators to install the fixed releases for iOS, iPadOS, and macOS Monterey. No additional configuration changes or workarounds are documented in the advisories.
Apple has stated it is aware of reports that the vulnerability may have been actively exploited in the wild. The associated EPSS score rose from a low baseline after disclosure to a peak of 0.0136 on 2023-01-01 before receding to its current value of 0.0033.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-35960
Vulnerability Data
An out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in iOS 15.6.1 and iPadOS 15.6.1, macOS Monterey 12.5.1. An application may be able to execute arbitrary code with kernel privileges. Apple is aware of a…
more
report that this issue may have been actively exploited.
- CWE(s)
- KEV Date Added
- 18 August 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.