Kernel privilege escalation via out-of-bounds write
Published May 26, 2022 · Updated Aug 3, 2024
Out-of-bounds write in the macOS Monterey kernel before 12.4 allows local users with Recovery code execution to gain kernel privileges. The kernel performs an out-of-bounds memory write because the affected bounds check fails to constrain the operation; Apple has not disclosed the function or input. Exploitation requires prior code execution in macOS Recovery and grants kernel-level control rather than initial access from the normal desktop.
Summary
What happened
Out-of-bounds write in the macOS Monterey kernel before 12.4 allows local users with Recovery code execution to gain kernel privileges. The kernel performs an out-of-bounds memory write because the affected bounds check fails to constrain the operation; Apple has not disclosed the function or input. Exploitation requires prior code execution in macOS Recovery and grants kernel-level control rather than initial access from the normal desktop.
The record
- CVE
- CVE-2022-26743
- Published
- May 26, 2022
- Updated
- Aug 3, 2024
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 26, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <12.4
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo