Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:HSummary
CVE-2023-28206 is a high-severity Out-of-bounds Write (CWE-787) vulnerability in Apple Macos. Its CVSS base score is 8.6 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 2% 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-2023-28206 is an out-of-bounds write vulnerability addressed through improved input validation in multiple Apple operating systems. The affected platforms include macOS Monterey prior to 12.6.5, macOS Ventura prior to 13.3.1, macOS Big Sur prior to 11.7.6, iOS and iPadOS prior to 16.4.1, and iOS and iPadOS prior to 15.7.5. The flaw carries a CVSS score of 8.6 and is classified under CWE-787.
An unprivileged local attacker can exploit the issue by supplying malicious input to a vulnerable application, potentially achieving arbitrary code execution with kernel-level privileges on the target device. The attack requires user interaction such as opening a crafted file or app.
Apple security advisories for the listed updates confirm that the vulnerability has been resolved in the specified releases and recommend that users install the patches promptly. The vendor notes awareness of reports indicating the issue may have been actively exploited in the wild prior to patching.
The associated EPSS score reached a peak of 0.2631 before receding to its current value of 0.2159, consistent with sustained but not sharply escalating post-disclosure interest in the flaw.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-31914
Vulnerability Data
An out-of-bounds write issue was addressed with improved input validation. This issue is fixed in macOS Monterey 12.6.5, iOS 16.4.1 and iPadOS 16.4.1, macOS Ventura 13.3.1, iOS 15.7.5 and iPadOS 15.7.5, macOS Big Sur 11.7.6. An app may be able…
more
to execute arbitrary code with kernel privileges. Apple is aware of a report that this issue may have been actively exploited.
- CWE(s)
- KEV Date Added
- 10 April 2023
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.