CVE-2022-22675
Apple macOS Out-of-Bounds Write Vulnerability
Apple macOS
An out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in tvOS 15.5, watchOS 8.6, macOS Big Sur 11.6.6, macOS Monterey 12.3.1, iOS 15.4.1 and iPadOS 15.4.1. An application may be able to execute arbitrary code with kernel privileges. Apple is aware of a report that this issue may have been actively exploited..
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 4 April 2022. US federal agencies were required to remediate it by 25 April 2022.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 12.5%, which is higher than 96.3% 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:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2022-22675 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2022-22675.
What does CVE-2022-22675 affect?
CVE-2022-22675 affects Apple macOS. An out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in tvOS 15.5, watchOS 8.6, macOS Big Sur 11.6.6, macOS Monterey 12.3.1, iOS 15.4.1 and iPadOS 15.4.1. An application may be able to execute arbitrary code with kernel privileges. Apple is aware of a report that this issue may have been actively exploited..
How severe is CVE-2022-22675?
CVE-2022-22675 is rated HIGH with a CVSS base score of 7.8. EPSS puts the probability of exploitation in the next 30 days at 12.5%, higher than 96.3% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 25 April 2022.
How should organisations respond to CVE-2022-22675?
Apply the vendor patch for Apple macOS 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.