CVE-2022-4187 json
Insufficient policy enforcement in DevTools in Google Chrome on Windows prior to 108.0.5359.71 allowed a remote attacker to bypass filesyst…
published 3y ago modified 4mo ago also EUVD-2022-51548
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 56%
- public exploits
- 0
- none known
Summary
Insufficient policy enforcement in DevTools in Google Chrome on Windows prior to 108.0.5359.71 allowed a remote attacker to bypass filesystem restrictions via a crafted HTML page. (Chromium security severity: Medium)
Patch / fix
- Google Chrome 108.0.5359.71
- chromium Debian 14, Debian 13, Debian 12 108.0.5359.71-1
debian advisories DEBIAN-CVE-2022-4187
- chromium-browser Ubuntu 18.04 LTS 108.0.5359.71-0ubuntu0.18.04.5
ubuntu advisories UBUNTU-CVE-2022-4187
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- chromium openSUSE Tumbleweed 108.0.5359.71-1.1
- chromium openSUSE Tumbleweed 113.0.5672.92-1.1
- chromium Package Hub 15 SP4, Package Hub 15 SP3, openSUSE Leap 15.4 +1 more 108.0.5359.71-bp154.2.49.1
opensuse advisories openSUSE-SU-2024:12545-1openSUSE-SU-2024:12948-1openSUSE-SU-2022:10229-1
Is CVE-2022-4187 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-4187 updated cvss 6.5
chromium-browser: Insufficient policy enforcement in DevTools
-
Red Hat All currently supported Red Hat productsnot 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
Exploit prediction
0.79% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N |
Affected products
- Google Chrome
Classification
- Technology feeds
References
-
security.gentoo.org
/glsa/202305-10
vendor-advisory
-
security.gentoo.org
/glsa/202311-11
vendor-advisory
-
chromereleases.googleblog.com
/2022/11/stable-channel-update-for-desktop_29.html
release-notes, vendor-advisory
-
crbug.com
/1381217
issue-tracking, permissions-required
Sources
- CVE List CVE-2022-4187
- NVD CVE-2022-4187
Fencer Intel 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.