CVE-2024-1672: Inappropriate implementation in Content Security Policy
Chromium: CVE-2024-1672 Inappropriate implementation in Content Security Policy
Other sources
Inappropriate implementation in Content Security Policy in Google Chrome prior to 122.0.6261.57 allowed a remote attacker to bypass content security policy via a crafted HTML page. (Chromium security severity: Medium)
— MITRE
This CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information.
— Microsoft
Credit
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Google Chrome (Trace Event)to a version that resolves this vulnerability.Fixed in 122.0.6261.57 - Upgrade
Upgrade
Google Chrome/Chromium-based browsersto a version that resolves this vulnerability.Fixed in 122.0.6261.57Patch CVE-2024-1672
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
What is the severity of CVE-2024-1672?
CVE-2024-1672 has a severity rating that indicates it poses a significant risk to affected systems.
How do I fix CVE-2024-1672?
To fix CVE-2024-1672, update Google Chrome to version 122.0.6261.57 or later, or apply relevant updates from Microsoft Edge or Fedora.
Which software is affected by CVE-2024-1672?
CVE-2024-1672 affects Microsoft Edge (Chromium-based) and Google Chrome versions prior to 122.0.6261.57, as well as Fedora versions 38 and 39.
Is there a workaround for CVE-2024-1672?
Currently, no specific workaround is recommended for CVE-2024-1672 other than applying the available updates.
How does CVE-2024-1672 impact system security?
CVE-2024-1672 can lead to inappropriate implementation issues that may compromise system security and user privacy.