Kernel code execution via Wi-Fi type confusion
Published Sep 8, 2021 · Updated Aug 3, 2024
Type confusion in the Wi-Fi component of Apple macOS before 11.3 allows local users to execute arbitrary code with kernel privileges. Apple says Wi-Fi mishandles state and causes type confusion but has not published the affected function, object types, or trigger input. Exploitation requires an application to run locally; successful abuse crosses into kernel privilege and permits kernel-level code execution.
Summary
What happened
Type confusion in the Wi-Fi component of Apple macOS before 11.3 allows local users to execute arbitrary code with kernel privileges. Apple says Wi-Fi mishandles state and causes type confusion but has not published the affected function, object types, or trigger input. Exploitation requires an application to run locally; successful abuse crosses into kernel privilege and permits kernel-level code execution.
The record
- CVE
- CVE-2021-1829
- Published
- Sep 8, 2021
- Updated
- Aug 3, 2024
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-843, T1068
- 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.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.
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