Content security policy bypass
Published Apr 17, 2024 · Updated Feb 13, 2025
Content security policy bypass in Google Chrome before 124.0.6367.60 allows remote attackers to cross WebUI policy boundaries via crafted HTML. Google has not published the exact WebUI locus or the enforcement operation that mishandles the crafted page. Exploitation requires a user to load attacker-controlled content and permits limited cross-boundary data access or modification, without a reported availability impact.
Summary
What happened
Content security policy bypass in Google Chrome before 124.0.6367.60 allows remote attackers to cross WebUI policy boundaries via crafted HTML. Google has not published the exact WebUI locus or the enforcement operation that mishandles the crafted page. Exploitation requires a user to load attacker-controlled content and permits limited cross-boundary data access or modification, without a reported availability impact.
The record
- CVE
- CVE-2024-3847
- Published
- Apr 17, 2024
- Updated
- Feb 13, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-305, CWE-79, CWE-691, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 17, 2024CVE publishedPublication date reported by the CVE source.
- Feb 13, 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=124.0.6367.60
- Affected versionversion=124.0.6367.60 <124.0.6367.60
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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