Heap corruption via crafted Model I/O file
Published Apr 2, 2021 · Updated Aug 4, 2024
Model I/O in macOS before 11.2 and iOS, iPadOS, and tvOS before 14.3 allows attackers to corrupt heap memory via a crafted file. Apple identifies the affected component and says improved checks resolved the issue, but it does not disclose the parsing operation or validation failure that corrupts the heap. A victim must cause Model I/O to process the attacker-supplied file; reported consequences are bounded to heap corruption, with no vendor claim of code execution.
Summary
What happened
Model I/O in macOS before 11.2 and iOS, iPadOS, and tvOS before 14.3 allows attackers to corrupt heap memory via a crafted file. Apple identifies the affected component and says improved checks resolved the issue, but it does not disclose the parsing operation or validation failure that corrupts the heap. A victim must cause Model I/O to process the attacker-supplied file; reported consequences are bounded to heap corruption, with no vendor claim of code execution.
The record
- CVE
- CVE-2020-29614
- Published
- Apr 2, 2021
- Updated
- Aug 4, 2024
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 2, 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 <14.3
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