Memory disclosure via crafted USD file
Published Nov 1, 2022 · Updated Apr 22, 2025
Information disclosure in Apple Model I/O in macOS before 13 and tvOS before 16.1 allows attackers to read memory via a crafted USD file. Apple identifies the Model I/O USD-processing path and inadequate memory handling, but has not disclosed the affected function or precise unsafe operation. Exploitation requires a user to process the file, and the documented consequence is limited to disclosure of process-accessible memory contents.
Summary
What happened
Information disclosure in Apple Model I/O in macOS before 13 and tvOS before 16.1 allows attackers to read memory via a crafted USD file. Apple identifies the Model I/O USD-processing path and inadequate memory handling, but has not disclosed the affected function or precise unsafe operation. Exploitation requires a user to process the file, and the documented consequence is limited to disclosure of process-accessible memory contents.
The record
- CVE
- CVE-2022-42810
- Published
- Nov 1, 2022
- Updated
- Apr 22, 2025
- Vendor
- Apple
- Product
- tvOS
- Classifications
- CWE-200, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 1, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 2025Record 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.7
- Affected versionversion=unspecified <16.1
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