Code execution via crafted PDF state corruption
Published Mar 18, 2022 · Updated Aug 3, 2024
Memory corruption in iOS before 15.4, watchOS before 8.5, and affected macOS releases allows attackers to execute code via a crafted PDF. The flaw is in Accelerate Framework, but Apple has not disclosed which PDF-processing routine mishandles state or how the corruption occurs. Exploitation requires a user to open the file; successful corruption can crash the application or execute code in its context.
Summary
What happened
Memory corruption in iOS before 15.4, watchOS before 8.5, and affected macOS releases allows attackers to execute code via a crafted PDF. The flaw is in Accelerate Framework, but Apple has not disclosed which PDF-processing routine mishandles state or how the corruption occurs. Exploitation requires a user to open the file; successful corruption can crash the application or execute code in its context.
The record
- CVE
- CVE-2022-22633
- Published
- Mar 18, 2022
- Updated
- Aug 3, 2024
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 18, 2022CVE 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 <15.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.
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