Process-memory disclosure or termination via bounds-check failure
Published Jun 10, 2024 · Updated Aug 19, 2024
Out-of-bounds read in AppleScript in Apple macOS before 12.5 allows local users to disclose process memory or terminate a process. The AppleScript processing path reads beyond valid bounds because its prior bounds checks do not reject the triggering script data; Apple has not published the affected function. Exploitation requires local processing and user interaction, and the consequence is limited to process-memory disclosure or process termination.
Summary
What happened
Out-of-bounds read in AppleScript in Apple macOS before 12.5 allows local users to disclose process memory or terminate a process. The AppleScript processing path reads beyond valid bounds because its prior bounds checks do not reject the triggering script data; Apple has not published the affected function. Exploitation requires local processing and user interaction, and the consequence is limited to process-memory disclosure or process termination.
The record
- CVE
- CVE-2022-48578
- Published
- Jun 10, 2024
- Updated
- Aug 19, 2024
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-125
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 10, 2024CVE publishedPublication date reported by the CVE source.
- Aug 19, 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=0 <12.5
- Affected versionversion=unspecified <12.5
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