CVE-2024-1672

CVE-2024-1672 is a medium-severity vulnerability in Google Chrome with a CVSS 3.x base score of 5.4. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-474.

Key facts

Description

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)

Frequently asked questions

What is CVE-2024-1672?
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)
How severe is CVE-2024-1672?
CVE-2024-1672 has a CVSS 3.x base score of 5.4, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is low, integrity low, and availability none.
Is CVE-2024-1672 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (55th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-1672?
CVE-2024-1672 primarily affects Google Chrome. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2024-1672?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2024-1672 have an EU (EUVD) identifier?
Yes. CVE-2024-1672 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-17407.
When was CVE-2024-1672 published?
CVE-2024-1672 was published on 2024-02-21 and last updated on 2026-06-17.

References

Affected products (3)

More vulnerabilities in Google Chrome

All CVEs affecting Google Chrome →

Other CWE-474 vulnerabilities

Browse all CWE-474 vulnerabilities →