CVE-2023-32409
Apple Multiple Products WebKit Sandbox Escape Vulnerability
Apple Multiple Products
The issue was addressed with improved bounds checks. This issue is fixed in watchOS 9.5, tvOS 16.5, macOS Ventura 13.4, iOS 15.7.8 and iPadOS 15.7.8, Safari 16.5, iOS 16.5 and iPadOS 16.5. A remote attacker may be able to break out of Web Content sandbox. Apple is aware of a report that this issue may have been actively exploited.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 22 May 2023. US federal agencies were required to remediate it by 12 June 2023.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 16.5%, which is higher than 97% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N
Frequently asked questions
Is CVE-2023-32409 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2023-32409.
What does CVE-2023-32409 affect?
CVE-2023-32409 affects Apple Multiple Products. The issue was addressed with improved bounds checks. This issue is fixed in watchOS 9.5, tvOS 16.5, macOS Ventura 13.4, iOS 15.7.8 and iPadOS 15.7.8, Safari 16.5, iOS 16.5 and iPadOS 16.5. A remote attacker may be able to break out of Web Content sandbox. Apple is aware of a report that this issue may have been actively exploited.
How severe is CVE-2023-32409?
CVE-2023-32409 is rated HIGH with a CVSS base score of 8.6. EPSS puts the probability of exploitation in the next 30 days at 16.5%, higher than 97% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 12 June 2023.
How should organisations respond to CVE-2023-32409?
Apply the vendor patch for Apple Multiple Products as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.