Arbitrary code execution via crafted dfont processing
Published Oct 19, 2021 · Updated Aug 3, 2024
Arbitrary code execution in Apple macOS FontParser before 11.6 allows attackers to run code by processing a maliciously crafted dfont file. Apple identifies FontParser as the locus and says improved checks resolved the issue, but has not disclosed the failed check or parser operation. User interaction is required to process the file, and successful exploitation runs arbitrary code in the affected processing context.
Summary
What happened
Arbitrary code execution in Apple macOS FontParser before 11.6 allows attackers to run code by processing a maliciously crafted dfont file. Apple identifies FontParser as the locus and says improved checks resolved the issue, but has not disclosed the failed check or parser operation. User interaction is required to process the file, and successful exploitation runs arbitrary code in the affected processing context.
The record
- CVE
- CVE-2021-30841
- 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