Kernel code execution via insufficient input validation
Published Mar 18, 2022 · Updated Aug 3, 2024
Kernel memory corruption before iOS/tvOS 15.4, macOS 12.3, and watchOS 8.5 allows local users to execute code with kernel privileges. Insufficient validation in the Kernel permits an out-of-bounds write that corrupts kernel memory. A user must run or interact with a crafted local application; successful exploitation crosses the application boundary and gains kernel privileges.
Summary
What happened
Kernel memory corruption before iOS/tvOS 15.4, macOS 12.3, and watchOS 8.5 allows local users to execute code with kernel privileges. Insufficient validation in the Kernel permits an out-of-bounds write that corrupts kernel memory. A user must run or interact with a crafted local application; successful exploitation crosses the application boundary and gains kernel privileges.
The record
- CVE
- CVE-2022-22640
- Published
- Mar 18, 2022
- Updated
- Aug 3, 2024
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-787, T1404, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 18, 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 <15.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