Arbitrary code execution via WebKit memory corruption
Published Sep 8, 2021 · Updated Aug 3, 2024
WebKit memory corruption in iOS and iPadOS before 14.6 and macOS Big Sur before 11.4 allows attackers to execute arbitrary code. Apple identifies multiple memory-corruption issues in WebKit's handling of malicious web content but has not published the affected functions or faulty memory operations. Execution requires a user or application to cause WebKit to process attacker-controlled web content, and the resulting code runs in the WebKit process context.
Summary
What happened
WebKit memory corruption in iOS and iPadOS before 14.6 and macOS Big Sur before 11.4 allows attackers to execute arbitrary code. Apple identifies multiple memory-corruption issues in WebKit's handling of malicious web content but has not published the affected functions or faulty memory operations. Execution requires a user or application to cause WebKit to process attacker-controlled web content, and the resulting code runs in the WebKit process context.
The record
- CVE
- CVE-2021-30734
- Published
- Sep 8, 2021
- Updated
- Aug 3, 2024
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
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.6
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