Arbitrary code execution via CoreAudio buffer overflow
Published Aug 24, 2021 · Updated Aug 3, 2024
A buffer overflow in Apple CoreAudio on macOS, iOS, iPadOS, and watchOS allows attackers to execute arbitrary code by processing a maliciously crafted audio file. CoreAudio performs unsafe memory handling while processing attacker-supplied audio data, allowing the overflow to corrupt memory. Exploitation requires local user interaction with the crafted file and can provide code execution in the affected process context.
Summary
What happened
A buffer overflow in Apple CoreAudio on macOS, iOS, iPadOS, and watchOS allows attackers to execute arbitrary code by processing a maliciously crafted audio file. CoreAudio performs unsafe memory handling while processing attacker-supplied audio data, allowing the overflow to corrupt memory. Exploitation requires local user interaction with the crafted file and can provide code execution in the affected process context.
The record
- CVE
- CVE-2021-30957
- Published
- Aug 24, 2021
- Updated
- Aug 3, 2024
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-120, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 24, 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 <15.2
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