ClearanceKit vulnerabilities

In ClearanceKit before version 5.0.10, the ECDSA key used to sign the policy database is stored in the macOS keychain without ACL restrictions. Any root process can use this key to sign arbitrary policy content.

In ClearanceKit before version 5.0.10, ECDSA signatures for SQLite database tables lack a version counter or freshness binding. An attacker can replace the database and signatures with an older, legitimately signed version, which will be accepted by the system.

In ClearanceKit before 5.0.6, the opfilter system extension can be suspended with SIGSTOP or killed with SIGKILL/SIGTERM by any process running as root. While suspended, AUTH Endpoint Security events time out and default to allow, silently disabling file-access policy enforcement.

ClearanceKit versions prior to 5.0.4-beta-1f46165 have a flaw in the Endpoint Security event handler where only the source path of dual-path file operations is checked, and the destination path is ignored. This allows any local process to bypass file-access protection using rename, link, copyfile, exchangedata, or clone operations.

ClearanceKit has a startup defect where only compile-time rules are enforced until user interacts with GUI. MDM and user-defined rules are not applied.