Content Security Policy bypass via WebKit state error
Published Mar 8, 2024 · Updated Apr 2, 2026
Protection mechanism failure in WebKit on affected Apple platforms allows remote attackers to bypass Content Security Policy via crafted web content. Apple identifies only a logic error corrected through improved state management and does not disclose the WebKit locus or incorrect state transition. A user must cause an affected WebKit client to process the content; published evidence establishes policy bypass but not native code execution or data disclosure.
Summary
What happened
Protection mechanism failure in WebKit on affected Apple platforms allows remote attackers to bypass Content Security Policy via crafted web content. Apple identifies only a logic error corrected through improved state management and does not disclose the WebKit locus or incorrect state transition. A user must cause an affected WebKit client to process the content; published evidence establishes policy bypass but not native code execution or data disclosure.
The record
- CVE
- CVE-2024-23284
- Published
- Mar 8, 2024
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-693, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 8, 2024CVE publishedPublication date reported by the CVE source.
- Apr 2, 2026Record 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=0 <16.7.6
- Affected versionversion=0 <17.4
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