Code execution via out-of-bounds write
Published Sep 8, 2021 · Updated Aug 3, 2024
Memory corruption in Apple macOS CoreGraphics allows attackers to execute arbitrary code by opening a crafted file on affected releases. CoreGraphics fails to validate crafted file data before an out-of-bounds write corrupts memory. Affected releases include Big Sur before 11.3 and uncorrected Catalina and Mojave installations; opening the file is required, and triggering can also crash the application.
Summary
What happened
Memory corruption in Apple macOS CoreGraphics allows attackers to execute arbitrary code by opening a crafted file on affected releases. CoreGraphics fails to validate crafted file data before an out-of-bounds write corrupts memory. Affected releases include Big Sur before 11.3 and uncorrected Catalina and Mojave installations; opening the file is required, and triggering can also crash the application.
The record
- CVE
- CVE-2021-1847
- Published
- Sep 8, 2021
- Updated
- Aug 3, 2024
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 8, 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.3
- Affected versionversion=unspecified <2021
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