Code execution via corrupted CoreAudio processing state
Published Sep 8, 2021 · Updated Aug 3, 2024
Memory corruption in Apple CoreAudio on iOS before 14.7 and macOS before 11.5 allows attackers to execute code via a crafted audio file. CoreAudio mishandles state while processing attacker-controlled audio data, corrupting memory; Apple has not disclosed the affected routine or exact write. A target must process the malicious file, so exploitation requires user interaction or another path that submits audio to CoreAudio, and successful exploitation runs code in the affected process.
Summary
What happened
Memory corruption in Apple CoreAudio on iOS before 14.7 and macOS before 11.5 allows attackers to execute code via a crafted audio file. CoreAudio mishandles state while processing attacker-controlled audio data, corrupting memory; Apple has not disclosed the affected routine or exact write. A target must process the malicious file, so exploitation requires user interaction or another path that submits audio to CoreAudio, and successful exploitation runs code in the affected process.
The record
- CVE
- CVE-2021-30775
- Published
- Sep 8, 2021
- Updated
- Aug 3, 2024
- Vendor
- Apple
- Product
- iOS
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 8, 2021CVE 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 <14.7
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.
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