Kernel code execution via out-of-bounds write
Published May 26, 2022 · Updated Aug 3, 2024
Out-of-bounds write in the macOS kernel before 12.4 allows attackers with code execution in macOS Recovery to gain kernel privileges. The kernel writes past a buffer boundary because the affected path lacks adequate bounds checks; Apple has not identified the function or input field involved. Reachability requires prior code execution in the Recovery environment, and successful exploitation elevates that foothold into kernel-context code execution.
Summary
What happened
Out-of-bounds write in the macOS kernel before 12.4 allows attackers with code execution in macOS Recovery to gain kernel privileges. The kernel writes past a buffer boundary because the affected path lacks adequate bounds checks; Apple has not identified the function or input field involved. Reachability requires prior code execution in the Recovery environment, and successful exploitation elevates that foothold into kernel-context code execution.
The record
- CVE
- CVE-2022-26708
- Published
- May 26, 2022
- Updated
- Aug 3, 2024
- Vendor
- Apple
- Product
- macOS
- Classifications
- T1068
- Attack vector
- local
- Privileges
- Unavailable
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.
Weakness, pattern, technique
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