Code execution via CoreMedia out-of-bounds write
Published Jun 10, 2024 · Updated Apr 2, 2026
An out-of-bounds write in Apple CoreMedia allows attackers to crash an app or execute arbitrary code by processing a crafted file. CoreMedia insufficiently validates file input before a write, allowing memory outside the intended buffer to be overwritten; Apple has not disclosed the responsible function or file format. Exploitation requires the target to process attacker-controlled file content, and successful corruption can terminate the processing app or execute code in its context.
Summary
What happened
An out-of-bounds write in Apple CoreMedia allows attackers to crash an app or execute arbitrary code by processing a crafted file. CoreMedia insufficiently validates file input before a write, allowing memory outside the intended buffer to be overwritten; Apple has not disclosed the responsible function or file format. Exploitation requires the target to process attacker-controlled file content, and successful corruption can terminate the processing app or execute code in its context.
The record
- CVE
- CVE-2024-27831
- Published
- Jun 10, 2024
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- iOS
- Classifications
- CWE-786, CWE-787, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 10, 2024CVE publishedPublication date reported by the CVE source.
- Apr 2, 2026Record 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 <16.7.8
- Affected versionversion=0 <17.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