User information disclosure via otool file parsing
Published Sep 6, 2023 · Updated Sep 30, 2024
Information disclosure in otool in Apple Xcode before 14.0 allows local users to expose user information by parsing a crafted file. Apple states only that otool's file parser lacked sufficient checks; no public source identifies the malformed field or failed validation. Exploitation requires user interaction with an attacker-controlled file and is limited to information disclosure, with no reported data modification or service interruption.
Summary
What happened
Information disclosure in otool in Apple Xcode before 14.0 allows local users to expose user information by parsing a crafted file. Apple states only that otool's file parser lacked sufficient checks; no public source identifies the malformed field or failed validation. Exploitation requires user interaction with an attacker-controlled file and is limited to information disclosure, with no reported data modification or service interruption.
The record
- CVE
- CVE-2022-32920
- Published
- Sep 6, 2023
- Updated
- Sep 30, 2024
- Vendor
- Apple
- Product
- Xcode
- Classifications
- T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 6, 2023CVE publishedPublication date reported by the CVE source.
- Sep 30, 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.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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