Code execution via AppleVA file processing
Published Jan 23, 2024 · Updated Nov 4, 2025
Memory corruption in AppleVA in Apple macOS before 14.2 allows attackers to crash an app or execute arbitrary code by processing a file. Apple identifies faulty memory handling in AppleVA but has not disclosed the affected parser, memory operation, or file format. Exploitation requires local file processing and user interaction; successful execution can run attacker-controlled code in the affected app's context.
Summary
What happened
Memory corruption in AppleVA in Apple macOS before 14.2 allows attackers to crash an app or execute arbitrary code by processing a file. Apple identifies faulty memory handling in AppleVA but has not disclosed the affected parser, memory operation, or file format. Exploitation requires local file processing and user interaction; successful execution can run attacker-controlled code in the affected app's context.
The record
- CVE
- CVE-2023-42881
- Published
- Jan 23, 2024
- Updated
- Nov 4, 2025
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-119, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 23, 2024CVE 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?
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