Local code execution via undisclosed IOKit logic flaws
Published Sep 8, 2021 · Updated Aug 3, 2024
Logic flaws in IOKit in Apple macOS Big Sur before 11.5 allow local users to execute code on the Apple T2 Security Chip. Apple identifies multiple logic issues in IOKit but has not published the affected functions, inputs, or incorrect operations. Exploitation requires local access and an Intel-based Mac containing a T2 chip; the documented consequence is code execution on that security coprocessor.
Summary
What happened
Logic flaws in IOKit in Apple macOS Big Sur before 11.5 allow local users to execute code on the Apple T2 Security Chip. Apple identifies multiple logic issues in IOKit but has not published the affected functions, inputs, or incorrect operations. Exploitation requires local access and an Intel-based Mac containing a T2 chip; the documented consequence is code execution on that security coprocessor.
The record
- CVE
- CVE-2021-30784
- Published
- Sep 8, 2021
- Updated
- Aug 3, 2024
- Vendor
- Apple
- Product
- macOS
- Classifications
- Unavailable
- 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 <11.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
No sourced classifications are available.
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