Skip to content
Fencer Vulns
high 8.8

CVE-2024-1672 json

Inappropriate implementation in Content Security Policy in Google Chrome prior to 122.0.6261.57 allowed a remote attacker to bypass content…

published 2024-02-21 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-17407

cvss
8.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 59%
public exploits
0
none known

Summary

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)

Patch / fix

  • Google Chrome 122.0.6261.57
  • chromium Debian 12 122.0.6261.57-1~deb12u1
  • chromium Debian 14, Debian 13 122.0.6261.57-1

debian advisories DEBIAN-CVE-2024-1672

  • chromium openSUSE Tumbleweed 122.0.6261.111-1.1
  • chromium Package Hub 15 SP5, openSUSE Leap 15.5 122.0.6261.128-bp155.2.75.1
  • llvm17 Package Hub 15 SP5, openSUSE Leap 15.5 17.0.6-bp155.2.2

opensuse advisories openSUSE-SU-2024:13764-1openSUSE-SU-2024:13766-1openSUSE-SU-2024:0084-1

  • qt6-qtwebengine Alpine 3.19 6.6.1-r8
  • qt6-qtwebengine Alpine 3.24, Alpine 3.23, Alpine 3.22 +2 more 6.6.2-r1

alpine advisories ALPINE-CVE-2024-1672

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-1672 updated cvss 6.5

chromium-browser: Inappropriate implementation in Content Security Policy

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
total
Assessed
2 y ago

Exploit prediction

0.88% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • chromereleases.googleblog.com https://chromereleases.googleblog.com/2024/02/stable-channel-update-for-desktop_20.html referenced PoC, tagged "exploit" by a source, unverified
  • issues.chromium.org https://issues.chromium.org/issues/41485789 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CISA ADP 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
CNA 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected products

  • Google Chrome

Classification

Weakness
  • CWE-474 Use of Function with Inconsistent Implementations
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.