Kernel code execution via out-of-bounds write
Published Nov 1, 2022 · Updated Apr 22, 2025
An out-of-bounds write in the Apple kernel before macOS 13, tvOS 16.1, and watchOS 9.1 allows remote attackers to execute kernel code. Insufficient bounds checking lets the kernel write beyond an intended buffer; Apple has not disclosed the affected function or input path. No authentication or user interaction is required, and successful exploitation compromises kernel-level confidentiality, integrity, and availability.
Summary
What happened
An out-of-bounds write in the Apple kernel before macOS 13, tvOS 16.1, and watchOS 9.1 allows remote attackers to execute kernel code. Insufficient bounds checking lets the kernel write beyond an intended buffer; Apple has not disclosed the affected function or input path. No authentication or user interaction is required, and successful exploitation compromises kernel-level confidentiality, integrity, and availability.
The record
- CVE
- CVE-2022-42808
- Published
- Nov 1, 2022
- Updated
- Apr 22, 2025
- Vendor
- Apple
- Product
- tvOS
- Classifications
- CWE-787
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 1, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 2025Record 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 <16.1
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