Restricted-memory disclosure via faulty CoreAudio validation
Published Sep 8, 2021 · Updated Aug 3, 2024
CoreAudio memory corruption in affected iOS, iPadOS, tvOS, watchOS, and macOS releases allows malicious applications to read restricted memory. Apple identifies faulty validation in CoreAudio but has not published the malformed input, code path, or exact memory operation that causes corruption. Execution of a malicious application is required, and the documented consequence is disclosure of memory that the application is not permitted to read.
Summary
What happened
CoreAudio memory corruption in affected iOS, iPadOS, tvOS, watchOS, and macOS releases allows malicious applications to read restricted memory. Apple identifies faulty validation in CoreAudio but has not published the malformed input, code path, or exact memory operation that causes corruption. Execution of a malicious application is required, and the documented consequence is disclosure of memory that the application is not permitted to read.
The record
- CVE
- CVE-2021-1809
- Published
- Sep 8, 2021
- Updated
- Aug 3, 2024
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- Unavailable
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.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