Code execution via FileProvider archive validation failure
Published Aug 24, 2021 · Updated Aug 3, 2024
Improper input validation in Apple FileProvider before iOS and iPadOS 15.1 and in affected macOS releases allows local users to execute code. FileProvider mishandles untrusted archive input during unpacking, but Apple has not published the precise validation failure or memory operation involved. Reaching the flaw requires a user to unpack a crafted archive; successful exploitation executes code in the affected process context.
Summary
What happened
Improper input validation in Apple FileProvider before iOS and iPadOS 15.1 and in affected macOS releases allows local users to execute code. FileProvider mishandles untrusted archive input during unpacking, but Apple has not published the precise validation failure or memory operation involved. Reaching the flaw requires a user to unpack a crafted archive; successful exploitation executes code in the affected process context.
The record
- CVE
- CVE-2021-30881
- Published
- Aug 24, 2021
- Updated
- Aug 3, 2024
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-20, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 24, 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 <15.1
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.
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