Kernel code execution via undisclosed memory corruption
Published Mar 18, 2022 · Updated Aug 3, 2024
Memory corruption in the Apple kernel in iOS and iPadOS before 15.4 and watchOS before 8.5 allows local users to execute kernel code. Apple states that improved validation corrected the corruption but has not disclosed the faulty validation path, data structure, or untrusted input. Exploitation requires executing an application on the device and grants kernel privileges, crossing the application sandbox boundary.
Summary
What happened
Memory corruption in the Apple kernel in iOS and iPadOS before 15.4 and watchOS before 8.5 allows local users to execute kernel code. Apple states that improved validation corrected the corruption but has not disclosed the faulty validation path, data structure, or untrusted input. Exploitation requires executing an application on the device and grants kernel privileges, crossing the application sandbox boundary.
The record
- CVE
- CVE-2022-22596
- Published
- Mar 18, 2022
- Updated
- Aug 3, 2024
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
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?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
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