Content security policy bypass
Published Jul 28, 2023 · Updated Feb 13, 2025
Insufficient input validation in DevTools in Google Chrome before 106.0.5249.62 allows remote attackers to bypass CSP via crafted HTML. Google identifies DevTools as the locus but has not published the specific data path or incorrect validation operation applied to page-controlled input. Exploitation requires a user to open the crafted page, and the documented consequence is limited to bypassing content security policy restrictions.
Summary
What happened
Insufficient input validation in DevTools in Google Chrome before 106.0.5249.62 allows remote attackers to bypass CSP via crafted HTML. Google identifies DevTools as the locus but has not published the specific data path or incorrect validation operation applied to page-controlled input. Exploitation requires a user to open the crafted page, and the documented consequence is limited to bypassing content security policy restrictions.
The record
- CVE
- CVE-2022-4911
- Published
- Jul 28, 2023
- Updated
- Feb 13, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-20
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 28, 2023CVE 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=106.0.5249.62 <106.0.5249.62
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