Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2022-22587 is a critical-severity Out-of-bounds Write (CWE-787) vulnerability in Apple Macos. 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 4% 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-22587 is a memory corruption vulnerability resulting from insufficient input validation, assigned CWE-787. It affects iOS and iPadOS prior to version 15.3 as well as macOS Big Sur prior to 11.6.3 and macOS Monterey prior to 12.2, with a CVSS 3.1 base score of 9.8 reflecting network-accessible impact on confidentiality, integrity, and availability.
A malicious application can exploit the flaw to execute arbitrary code with kernel privileges on an unpatched device. The vulnerability requires no user interaction or special privileges beyond the ability to run the application.
Apple security updates HT213053, HT213054, and HT213055 address the issue through improved input validation in the listed releases. The advisories note that Apple is aware of reports indicating the vulnerability may have been actively exploited in the wild. The associated EPSS probability rose from a low baseline after disclosure to a peak of 0.0184 on 2023-01-01 before receding to its current value of 0.0041.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-27732
Vulnerability Data
A memory corruption issue was addressed with improved input validation. This issue is fixed in iOS 15.3 and iPadOS 15.3, macOS Big Sur 11.6.3, macOS Monterey 12.2. A malicious application may be able to execute arbitrary code with kernel privileges.…
more
Apple is aware of a report that this issue may have been actively exploited..
- CWE(s)
- KEV Date Added
- 28 January 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.