Kernel-memory corruption via CommCenter out-of-bounds write
Published May 8, 2023 · Updated Jan 29, 2025
An out-of-bounds write in Apple CommCenter allows local users to terminate affected macOS, iOS, or iPadOS systems or write kernel memory. CommCenter insufficiently validates app-supplied input before a memory write, allowing the write to exceed its intended bounds. Execution of an app on an affected device is required; Apple reports outcomes limited to unexpected system termination or modification of kernel memory.
Summary
What happened
An out-of-bounds write in Apple CommCenter allows local users to terminate affected macOS, iOS, or iPadOS systems or write kernel memory. CommCenter insufficiently validates app-supplied input before a memory write, allowing the write to exceed its intended bounds. Execution of an app on an affected device is required; Apple reports outcomes limited to unexpected system termination or modification of kernel memory.
The record
- CVE
- CVE-2023-27936
- Published
- May 8, 2023
- Updated
- Jan 29, 2025
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-787, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 8, 2023CVE publishedPublication date reported by the CVE source.
- Jan 29, 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 <15.7
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