cve.bz

CVE-2022-3056 Protection Mechanism Failure

6.5 mediumEPSS 1.2%Fix available

Medium (6.5). EPSS 1.2% estimated probability of exploitation activity in the next 30 days.

On this page
Insufficient policy enforcement in Content Security Policy in Google Chrome prior to 105.0.5195.52 allowed a remote attacker to bypass content security policy via a crafted HTML page.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
EPSS
1.2% (unchanged from 1.1% a week ago; 1.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 69th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2025-05-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-693 Protection Mechanism Failure
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2022-3056 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-3056?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-3056?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-3056 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Google Chromebefore 105.0.5195.52

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian11chromium105.0.5195.52-1~deb11u1DSA-5223-1
Debian12, 13, 14chromium105.0.5195.52-1DEBIAN-CVE-2022-3056
Ubuntu18.04:LTSchromium-browser105.0.5195.102-0ubuntu0.18.04.1UBUNTU-CVE-2022-3056
SUSEPackage Hub 15 SP3chromium105.0.5195.102-bp153.2.119.1openSUSE-SU-2022:10120-1
SUSEPackage Hub 15 SP4chromium105.0.5195.102-bp154.2.26.1openSUSE-SU-2022:10119-1
openSUSELeap 15.3chromium105.0.5195.102-bp153.2.119.1openSUSE-SU-2022:10120-1
openSUSELeap 15.4chromium105.0.5195.102-bp154.2.26.1openSUSE-SU-2022:10119-1
openSUSETumbleweedchromium105.0.5195.102-1.1openSUSE-SU-2024:12319-1
openSUSETumbleweedchromium113.0.5672.92-1.1openSUSE-SU-2024:12948-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-693 (17).

References

Check your stackJSON