Elevated code execution via fsck_msdos memory corruption
Published Dec 23, 2021 · Updated Aug 5, 2024
Memory corruption in Apple macOS before 10.13 allows local users to execute arbitrary code with elevated privileges through fsck_msdos. Apple has not disclosed the malformed input, memory operation, or specific code path in fsck_msdos that corrupts memory. Exploitation requires a user to run an application that reaches the local filesystem-checking utility, after which injected code executes with elevated privileges.
Summary
What happened
Memory corruption in Apple macOS before 10.13 allows local users to execute arbitrary code with elevated privileges through fsck_msdos. Apple has not disclosed the malformed input, memory operation, or specific code path in fsck_msdos that corrupts memory. Exploitation requires a user to run an application that reaches the local filesystem-checking utility, after which injected code executes with elevated privileges.
The record
- CVE
- CVE-2017-13835
- Published
- Dec 23, 2021
- Updated
- Aug 5, 2024
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-119, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 23, 2021CVE publishedPublication date reported by the CVE source.
- Aug 5, 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.13
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
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