Local code injection via unhardened bundled binaries
Published Jan 10, 2024 · Updated Jun 20, 2025
Code injection in AppleMobileFileIntegrity in Apple macOS allows local users to inject code into sensitive Xcode-bundled binaries. AppleMobileFileIntegrity did not force the affected binaries to use hardened runtime, leaving their processes open to injected code. Execution requires a local malicious app and user interaction; injected code runs in a sensitive developer-tool binary's process.
Summary
What happened
Code injection in AppleMobileFileIntegrity in Apple macOS allows local users to inject code into sensitive Xcode-bundled binaries. AppleMobileFileIntegrity did not force the affected binaries to use hardened runtime, leaving their processes open to injected code. Execution requires a local malicious app and user interaction; injected code runs in a sensitive developer-tool binary's process.
The record
- CVE
- CVE-2023-32383
- Published
- Jan 10, 2024
- Updated
- Jun 20, 2025
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-94, T1055
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 10, 2024CVE publishedPublication date reported by the CVE source.
- Jun 20, 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 <11.7
- Affected versionversion=unspecified <12.6
- Affected versionversion=unspecified <13.4
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