Arbitrary code execution via crafted image processing
Published Apr 2, 2021 · Updated Aug 3, 2024
Arbitrary code execution in Apple ImageIO on affected iOS, iPadOS, and macOS releases allows attackers to run code via a crafted image. Apple identifies ImageIO as the affected image-processing component but discloses only that improved checks address the flaw, not the failed check or malformed field. Exploitation requires the target to process an attacker-supplied image; successful exploitation executes code in the context of the processing application.
Summary
What happened
Arbitrary code execution in Apple ImageIO on affected iOS, iPadOS, and macOS releases allows attackers to run code via a crafted image. Apple identifies ImageIO as the affected image-processing component but discloses only that improved checks address the flaw, not the failed check or malformed field. Exploitation requires the target to process an attacker-supplied image; successful exploitation executes code in the context of the processing application.
The record
- CVE
- CVE-2021-1754
- Published
- Apr 2, 2021
- Updated
- Aug 3, 2024
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 2, 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 <14.4
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