Local privilege escalation via undisclosed state-management logic
Published Dec 11, 2024 · Updated Apr 2, 2026
A logic issue in LaunchServices in Apple macOS before 15.2 allows local users to elevate privileges through a locally run app. Apple identifies improper LaunchServices state management but has not disclosed the affected function, state transition, or validation failure. Exploitation requires local execution of a crafted app, and the resulting privilege level has not been specified publicly.
Summary
What happened
A logic issue in LaunchServices in Apple macOS before 15.2 allows local users to elevate privileges through a locally run app. Apple identifies improper LaunchServices state management but has not disclosed the affected function, state transition, or validation failure. Exploitation requires local execution of a crafted app, and the resulting privilege level has not been specified publicly.
The record
- CVE
- CVE-2024-54465
- Published
- Dec 11, 2024
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-281, T1068
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 11, 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 <15.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