Kernel code execution via out-of-bounds write
Published Aug 24, 2021 · Updated Aug 3, 2024
An out-of-bounds write in IOMobileFrameBuffer in Apple iOS and iPadOS before 15.2 allows attackers to execute code with kernel privileges. IOMobileFrameBuffer writes beyond an intended buffer because its bounds checking is insufficient; Apple has not disclosed the affected function or input. Execution of a malicious application is required, after which attacker-controlled code runs in the kernel rather than the application sandbox.
Summary
What happened
An out-of-bounds write in IOMobileFrameBuffer in Apple iOS and iPadOS before 15.2 allows attackers to execute code with kernel privileges. IOMobileFrameBuffer writes beyond an intended buffer because its bounds checking is insufficient; Apple has not disclosed the affected function or input. Execution of a malicious application is required, after which attacker-controlled code runs in the kernel rather than the application sandbox.
The record
- CVE
- CVE-2021-30985
- Published
- Aug 24, 2021
- Updated
- Aug 3, 2024
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-787, T1404
- 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.
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