Code execution via malformed file input
Published Dec 12, 2023 · Updated Nov 4, 2025
Memory corruption in AppleGraphicsControl in Apple macOS before 14.2 allows attackers to crash an app or execute code via a crafted file. The component insufficiently validates file input before memory operations, but Apple has not disclosed the affected parser or exact corruption primitive. Exploitation requires a user to process the file, and successful code execution runs in the context of the affected application.
Summary
What happened
Memory corruption in AppleGraphicsControl in Apple macOS before 14.2 allows attackers to crash an app or execute code via a crafted file. The component insufficiently validates file input before memory operations, but Apple has not disclosed the affected parser or exact corruption primitive. Exploitation requires a user to process the file, and successful code execution runs in the context of the affected application.
The record
- CVE
- CVE-2023-42901
- Published
- Dec 12, 2023
- Updated
- Nov 4, 2025
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 12, 2023CVE publishedPublication date reported by the CVE source.
- Nov 4, 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 <14.2
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.
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