Arbitrary code execution via malformed font processing
Published Apr 2, 2021 · Updated Aug 4, 2024
CoreText in iOS and iPadOS before 14.2, tvOS before 14.2, watchOS before 7.1, and affected macOS releases allows attackers to execute code. CoreText incorrectly manages parser state while processing untrusted font data; Apple has not identified the affected routine or state transition. An attacker must cause an affected device to process a crafted font file; successful exploitation runs arbitrary code in the parsing context.
Summary
What happened
CoreText in iOS and iPadOS before 14.2, tvOS before 14.2, watchOS before 7.1, and affected macOS releases allows attackers to execute code. CoreText incorrectly manages parser state while processing untrusted font data; Apple has not identified the affected routine or state transition. An attacker must cause an affected device to process a crafted font file; successful exploitation runs arbitrary code in the parsing context.
The record
- CVE
- CVE-2020-27922
- Published
- Apr 2, 2021
- Updated
- Aug 4, 2024
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- T1203, 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.2
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