CVE-2023-42917
Memory Safety in Apple Ipados ≤ 15.8.1
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2023-42917 is a high-severity Out-of-bounds Write (CWE-787) vulnerability in Apple Ipados. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 5% 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.
A memory corruption vulnerability addressed through improved locking affects the web content processing component in Apple's platforms. It impacts iOS and iPadOS prior to version 17.1.2, macOS Sonoma prior to 14.1.2, and Safari prior to 17.1.2. The flaw carries a CVSS score of 8.8 and is categorized under CWE-787, with successful exploitation resulting in arbitrary code execution when malicious web content is processed.
An attacker can trigger the issue remotely by serving specially crafted web content that a user visits in Safari or another affected browser. No authentication is required, though user interaction is needed to load the page, after which the attacker can achieve full code execution with the privileges of the browser process.
Apple's security updates for the listed versions resolve the issue, and full disclosure advisories published in December 2023 detail the affected builds and fixed releases. The vendor has stated that the vulnerability may have been exploited in the wild against iOS versions before 16.7.1. The current EPSS score remains low at 0.0009 with no indicated upward movement.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-47338
Vulnerability Data
A memory corruption vulnerability was addressed with improved locking. This issue is fixed in iOS 17.1.2 and iPadOS 17.1.2, macOS Sonoma 14.1.2, Safari 17.1.2. Processing web content may lead to arbitrary code execution. Apple is aware of a report that…
more
this issue may have been exploited against versions of iOS before iOS 16.7.1.
- CWE(s)
- KEV Date Added
- 04 December 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.