CVE-2023-41992
Apple Multiple Products Kernel Privilege Escalation Vulnerability
Apple Multiple Products
The issue was addressed with improved checks. This issue is fixed in macOS Monterey 12.7, iOS 16.7 and iPadOS 16.7, macOS Ventura 13.6. A local attacker may be able to elevate their privileges. Apple is aware of a report that this issue may have been actively exploited against versions of iOS before iOS 16.7.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 25 September 2023. US federal agencies were required to remediate it by 16 October 2023.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 9.5%, which is higher than 95.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:L/UI:N/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2023-41992 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2023-41992.
What does CVE-2023-41992 affect?
CVE-2023-41992 affects Apple Multiple Products. The issue was addressed with improved checks. This issue is fixed in macOS Monterey 12.7, iOS 16.7 and iPadOS 16.7, macOS Ventura 13.6. A local attacker may be able to elevate their privileges. Apple is aware of a report that this issue may have been actively exploited against versions of iOS before iOS 16.7.
How severe is CVE-2023-41992?
CVE-2023-41992 is rated HIGH with a CVSS base score of 7.8. EPSS puts the probability of exploitation in the next 30 days at 9.5%, higher than 95.3% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 16 October 2023.
How should organisations respond to CVE-2023-41992?
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.