Incorrect institutional recovery key presence reporting
Published Dec 23, 2021 · Updated Aug 4, 2024
Logic error in fdesetup in Apple macOS before 10.14 allows local users to receive an incorrect report that an institutional recovery key is present. The fdesetup status path mishandles internal state when checking for an institutional FileVault recovery key and reports that an absent key is present. The check is local, and its false-positive result can cause administrators to rely on a recovery mechanism that is not configured.
Summary
What happened
Logic error in fdesetup in Apple macOS before 10.14 allows local users to receive an incorrect report that an institutional recovery key is present. The fdesetup status path mishandles internal state when checking for an institutional FileVault recovery key and reports that an absent key is present. The check is local, and its false-positive result can cause administrators to rely on a recovery mechanism that is not configured.
The record
- CVE
- CVE-2019-8643
- Published
- Dec 23, 2021
- Updated
- Aug 4, 2024
- Vendor
- Apple
- Product
- macOS
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 23, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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=unspecified <10.14
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
No sourced classifications are available.
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