Restricted-memory disclosure via crafted audio file
Published Apr 2, 2021 · Updated Aug 4, 2024
Out-of-bounds read in the Audio component of Apple operating systems allows attackers to disclose restricted memory through a crafted audio file. The component processes attacker-controlled audio data without adequate bounds validation, causing a read beyond the intended buffer. Exploitation requires a targeted device to process the file; published evidence limits the consequence to memory disclosure.
Summary
What happened
Out-of-bounds read in the Audio component of Apple operating systems allows attackers to disclose restricted memory through a crafted audio file. The component processes attacker-controlled audio data without adequate bounds validation, causing a read beyond the intended buffer. Exploitation requires a targeted device to process the file; published evidence limits the consequence to memory disclosure.
The record
- CVE
- CVE-2020-29610
- Published
- Apr 2, 2021
- Updated
- Aug 4, 2024
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-125, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 2, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.3
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.
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