Local code execution via dylib hijacking
Published Mar 19, 2024 · Updated Mar 26, 2025
Uncontrolled library loading in Claris FileMaker Pro before 20.2 allows local users to execute code through dylib hijacking on macOS. Claris has not published which application component or search path permits an attacker-controlled dynamic library to load. Exploitation requires local low-privileged access and runs attacker code with the privileges of the FileMaker Pro process.
Summary
What happened
Uncontrolled library loading in Claris FileMaker Pro before 20.2 allows local users to execute code through dylib hijacking on macOS. Claris has not published which application component or search path permits an attacker-controlled dynamic library to load. Exploitation requires local low-privileged access and runs attacker code with the privileges of the FileMaker Pro process.
The record
- CVE
- CVE-2023-42920
- Published
- Mar 19, 2024
- Updated
- Mar 26, 2025
- Vendor
- Claris
- Product
- FileMaker Pro
- Classifications
- CWE-427, T1574.006
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 19, 2024CVE publishedPublication date reported by the CVE source.
- Mar 26, 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=0 <20.2
- Affected versionversion=unspecified <20.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