Kernel code execution via undisclosed type confusion
Published Jan 10, 2024 · Updated Aug 26, 2024
Type confusion in Apple operating-system kernels allows local users to execute arbitrary code with kernel privileges through an app. Apple identifies inadequate type checks but has not published the kernel locus, confused types, or malformed input that reaches the operation. Exploitation requires a user to run or otherwise interact with a malicious app; successful code executes with kernel privileges.
Summary
What happened
Type confusion in Apple operating-system kernels allows local users to execute arbitrary code with kernel privileges through an app. Apple identifies inadequate type checks but has not published the kernel locus, confused types, or malformed input that reaches the operation. Exploitation requires a user to run or otherwise interact with a malicious app; successful code executes with kernel privileges.
The record
- CVE
- CVE-2023-41075
- Published
- Jan 10, 2024
- Updated
- Aug 26, 2024
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-843, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 10, 2024CVE publishedPublication date reported by the CVE source.
- Aug 26, 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.7
- Affected versionversion=unspecified <16.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
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