ClearanceKit has a policy bypass via dual-path Endpoint Security events checking only source path
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| craigjbass | clearancekit | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Craigjbass | Clearancekit |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.110% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Craigjbass
Craigjbass clearancekit |
|
| Vendors & Products |
Craigjbass
Craigjbass clearancekit |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | ClearanceKit intercepts file-system access events on macOS and enforces per-process access policies. Prior to 5.0.4-beta-1f46165, ClearanceKit's Endpoint Security event handler only checked the source path of dual-path file operations against File Access Authorization (FAA) rules and App Jail policies. The destination path was ignored entirely. This allowed any local process to bypass file-access protection by using rename, link, copyfile, exchangedata, or clone operations to place or replace files inside protected directories. This vulnerability is fixed in 5.0.4-beta-1f46165. | |
| Title | ClearanceKit has a policy bypass via dual-path Endpoint Security events checking only source path | |
| Weaknesses | CWE-863 | |
| References |
| |
| Metrics |
cvssV4_0
|