Code execution via WebKit state mismanagement
Published Dec 15, 2022 · Updated Apr 21, 2025
Memory corruption in Apple WebKit on tvOS before 16.2 and watchOS before 9.2 allows remote attackers to execute code via crafted web content. WebKit mishandles internal state while processing attacker-controlled content, corrupting memory; Apple has not publicly identified the affected routine or memory operation. Execution requires a vulnerable device to process the content and can run code in the WebKit process context.
Summary
What happened
Memory corruption in Apple WebKit on tvOS before 16.2 and watchOS before 9.2 allows remote attackers to execute code via crafted web content. WebKit mishandles internal state while processing attacker-controlled content, corrupting memory; Apple has not publicly identified the affected routine or memory operation. Execution requires a vulnerable device to process the content and can run code in the WebKit process context.
The record
- CVE
- CVE-2022-46699
- Published
- Dec 15, 2022
- Updated
- Apr 21, 2025
- Vendor
- Apple
- Product
- tvOS
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 15, 2022CVE publishedPublication date reported by the CVE source.
- Apr 21, 2025Record 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 <13.1
- Affected versionversion=unspecified <16.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