Protected filesystem modification via Crash Reporter state error
Published Sep 8, 2021 · Updated Aug 3, 2024
Logic error in Apple Crash Reporter before iOS and iPadOS 14.6 or macOS 11.4 allows local users to modify protected files. Crash Reporter incorrectly manages internal state, but Apple has not disclosed the affected function or state transition that permits writes into protected filesystem locations. Exploitation requires a malicious application to run locally with user interaction; the established consequence is unauthorized filesystem modification, not code execution.
Summary
What happened
Logic error in Apple Crash Reporter before iOS and iPadOS 14.6 or macOS 11.4 allows local users to modify protected files. Crash Reporter incorrectly manages internal state, but Apple has not disclosed the affected function or state transition that permits writes into protected filesystem locations. Exploitation requires a malicious application to run locally with user interaction; the established consequence is unauthorized filesystem modification, not code execution.
The record
- CVE
- CVE-2021-30727
- Published
- Sep 8, 2021
- Updated
- Aug 3, 2024
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- T1404, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 8, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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 <14.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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