Code execution via malicious dfont processing
Published Oct 19, 2021 · Updated Aug 3, 2024
Code execution in FontParser in Apple macOS Big Sur before 11.6 and Catalina allows context-dependent attackers to run code via a dfont file. FontParser accepts the crafted font during dfont processing, but Apple has not published which parser check is missing or what unsafe operation follows. Exploitation requires a user to process the file, after which code runs with the affected application's privileges.
Summary
What happened
Code execution in FontParser in Apple macOS Big Sur before 11.6 and Catalina allows context-dependent attackers to run code via a dfont file. FontParser accepts the crafted font during dfont processing, but Apple has not published which parser check is missing or what unsafe operation follows. Exploitation requires a user to process the file, after which code runs with the affected application's privileges.
The record
- CVE
- CVE-2021-30842
- Published
- Oct 19, 2021
- Updated
- Aug 3, 2024
- Vendor
- Apple
- Product
- macOS
- Classifications
- T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 19, 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 <11.6
- Affected versionversion=unspecified <14.8
- Affected versionversion=unspecified <15
- Affected versionversion=unspecified <2021
- Affected versionversion=unspecified <8
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