Protected-file modification via insufficient library-injection restrictions
Published Sep 16, 2024 · Updated Apr 2, 2026
Library injection in Apple macOS Ventura before 13.7, Sonoma before 14.7, and Sequoia before 15 allows local users to modify protected files. AppleMobileFileIntegrity applies insufficient restrictions to libraries injected by an app, allowing injected code to write protected filesystem locations. Execution of a local app is required; Apple has not disclosed the affected validation path or injection technique.
Summary
What happened
Library injection in Apple macOS Ventura before 13.7, Sonoma before 14.7, and Sequoia before 15 allows local users to modify protected files. AppleMobileFileIntegrity applies insufficient restrictions to libraries injected by an app, allowing injected code to write protected filesystem locations. Execution of a local app is required; Apple has not disclosed the affected validation path or injection technique.
The record
- CVE
- CVE-2024-44168
- Published
- Sep 16, 2024
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-114, CWE-427, T1574.006
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 16, 2024CVE publishedPublication date reported by the CVE source.
- Apr 2, 2026Record 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=0 <13.7
- Affected versionversion=0 <14.7
- Affected versionversion=0 <15
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