ClearanceKit's signed policy tables lack monotonic counter, allowing replay of older legitimately-signed snapshots
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.152% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Craigjbass
Craigjbass clearancekit |
|
| Vendors & Products |
Craigjbass
Craigjbass clearancekit |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | ClearanceKit intercepts file-system access events on macOS and enforces per-process access policies. Prior to version 5.0.10, each table in the on-disk SQLite policy store (`/Library/Application Support/clearancekit/store.db`) is verified using an ECDSA signature stored in the `data_signatures` table. The signed payload contains only the canonical row content, with no version counter or freshness binding. An attacker who can write `store.db` and the matching `data_signatures` row — feasible during the opfilter-update window when the Endpoint Security filter is offline, or via offline-boot / decrypted-backup scenarios — can substitute a previously-captured legitimately-signed snapshot. opfilter accepts the older snapshot as fully valid on next boot because the existing signatures still verify. Version 5.0.10 patches the issue. | |
| Title | ClearanceKit's signed policy tables lack monotonic counter, allowing replay of older legitimately-signed snapshots | |
| Weaknesses | CWE-294 | |
| References |
| |
| Metrics |
cvssV4_0
|