Kernel code execution via ppp out-of-bounds write
Published Nov 1, 2022 · Updated Apr 21, 2025
Memory corruption in the ppp component of Apple macOS before 13 allows local users with root privileges to execute kernel code. The component performs an out-of-bounds write during memory handling, but Apple has not disclosed the affected function or input. Exploitation requires an already root-privileged app and permits arbitrary instructions to run in the kernel, beyond normal user-space controls.
Summary
What happened
Memory corruption in the ppp component of Apple macOS before 13 allows local users with root privileges to execute kernel code. The component performs an out-of-bounds write during memory handling, but Apple has not disclosed the affected function or input. Exploitation requires an already root-privileged app and permits arbitrary instructions to run in the kernel, beyond normal user-space controls.
The record
- CVE
- CVE-2022-42830
- Published
- Nov 1, 2022
- Updated
- Apr 21, 2025
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Nov 1, 2022CVE publishedPublication date reported by the CVE source.
- Apr 21, 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 <13
- 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.
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