Summary
ClearanceKit, a macOS file access policy enforcement tool, failed to intercept the ES_EVENT_TYPE_AUTH_EXCHANGEDATA and ES_EVENT_TYPE_AUTH_CLONE events used for certain file operations.
Local processes could leverage these unmonitored operations to bypass configured per-process file access policies, potentially accessing or manipulating files that should be restricted.
Affected context
This vulnerability affects macOS systems using ClearanceKit's opfilter system extension to enforce per-process file access controls.
It is relevant when applications rely on ClearanceKit to mediate all filesystem operations, including file cloning and data exchange, as part of their security posture.
Environments where untrusted or semi-trusted local processes run alongside sensitive data are particularly exposed, since assumptions that all file access is policy-governed do not hold for these specific event types.
Exploit preconditions
- Attack surface: Local macOS processes running on a system where ClearanceKit is installed and relied upon for filesystem access control.
- Required access: Ability to execute code or run applications on the target machine under a user context subject to ClearanceKit policies.
- Trigger point: Performing file operations that use the underlying EXCHANGEDATA or CLONE mechanisms (ES_EVENT_TYPE_AUTH_EXCHANGEDATA / ES_EVENT_TYPE_AUTH_CLONE) on files that should be policy-protected.
- Why exploitation is possible: ClearanceKit's opfilter system extension did not subscribe to these two event types, so the operations bypassed the existing policy evaluation path and were not subject to authorization checks.
Why this happens
The underlying issue is incomplete authorization coverage in ClearanceKit's event subscription and policy evaluation pipeline.
While most file operations were routed through the opfilter extension and evaluated against per-process policies, the EXCHANGEDATA and CLONE event types were omitted from the subscription set.
This maps to CWE-862: Missing Authorization, where sensitive operations are allowed without verifying whether the requesting subject is authorized, due to gaps in the enforcement mechanism's coverage of the available operation types.
Potential impact
- Local processes may read from or write to files that ClearanceKit policies were intended to restrict.
- Applications can potentially modify or replace sensitive files via clone or data-exchange semantics without triggering policy checks.
- Compromise of data integrity where protected files can be altered outside of expected access control rules.
- Escalation of impact from other local vulnerabilities by using these operations to access or tamper with restricted resources.
General mitigation guidance
Mitigation centers on ensuring that all relevant filesystem operations are consistently subject to policy evaluation and least-privilege principles.
Recommended defensive patterns include:
- Reviewing authorization enforcement layers to confirm that every supported file operation type, including less commonly used ones (such as clone and exchangedata), is covered by the same policy engine.
- Designing authorization logic so that new or overlooked event types fail closed, denying access when they are not explicitly handled.
- Regularly auditing the mapping between OS event types and enforcement hooks to detect gaps or newly introduced operation types.
- Applying defense-in-depth by combining ClearanceKit-style enforcement with native filesystem permissions and sandboxing, so that bypassing one control does not grant unrestricted access.
- Minimizing the privileges and accessible paths of local processes, reducing the impact if policy enforcement is incomplete for specific operations.
How teams detect issues like this
Detection efforts can focus on identifying unexpected filesystem operations that bypass normal access control checks, and on spotting coverage gaps in enforcement configurations.
Possible strategies include:
- Static analysis or code review of enforcement extensions and policy engines to confirm that all ES event types relevant to file operations are subscribed and routed through authorization checks.
- Configuration and policy audits that compare the intended set of controlled operations with the actual event subscriptions and filter rules.
- Runtime monitoring of filesystem activity (e.g., via macOS Endpoint Security logs or equivalent telemetry) to detect clone or exchangedata operations targeting paths that are nominally protected.
- Incorporating security tests in CI/CD that attempt restricted file operations via alternative system calls or event types to ensure consistent enforcement behavior.

