Kernel code execution via MobileAccessoryUpdater memory corruption
Published May 26, 2022 · Updated Aug 3, 2024
Memory corruption in MobileAccessoryUpdater in iOS, iPadOS, and macOS before their fixed releases allows local users to execute arbitrary code with kernel privileges. Apple identifies the affected component and says improved memory handling resolves the issue, but the precise faulty operation on untrusted input is undisclosed. Exploitation requires a malicious application running on the device; successful exploitation gives kernel-level code execution.
Summary
What happened
Memory corruption in MobileAccessoryUpdater in iOS, iPadOS, and macOS before their fixed releases allows local users to execute arbitrary code with kernel privileges. Apple identifies the affected component and says improved memory handling resolves the issue, but the precise faulty operation on untrusted input is undisclosed. Exploitation requires a malicious application running on the device; successful exploitation gives kernel-level code execution.
The record
- CVE
- CVE-2022-22672
- Published
- May 26, 2022
- Updated
- Aug 3, 2024
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
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 <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.
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