Code execution via otool out-of-bounds read
Published Mar 18, 2022 · Updated Aug 3, 2024
An out-of-bounds read in Apple Xcode before 13.3 allows context-dependent attackers to crash otool or execute code through a malicious file. The otool binary reads beyond a buffer boundary while parsing the crafted file because its bounds checks do not reject the malformed input. Exploitation requires a user to open the file; successful processing can terminate the application or run attacker-controlled code in the user's context.
Summary
What happened
An out-of-bounds read in Apple Xcode before 13.3 allows context-dependent attackers to crash otool or execute code through a malicious file. The otool binary reads beyond a buffer boundary while parsing the crafted file because its bounds checks do not reject the malformed input. Exploitation requires a user to open the file; successful processing can terminate the application or run attacker-controlled code in the user's context.
The record
- CVE
- CVE-2022-22606
- Published
- Mar 18, 2022
- Updated
- Aug 3, 2024
- Vendor
- Apple
- Product
- Xcode
- Classifications
- CWE-125, T1203
- 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 <13.3
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