LiveActive security incident?Get immediate response
CVE Record

CVE-2022-3056: Insufficient policy enforcement in Content Security Policy in Google Chrome prior to 105.0.5195.52 allowed...

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.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Chrome flaw could let a malicious web page bypass Content Security Policy protections in vulnerable browser versions. It requires user interaction, such as visiting a crafted page, and primarily threatens integrity rather than confidentiality or availability.

Executive priority

Treat as a standard browser patching priority, not an emergency based on available evidence. The business risk is users reaching malicious web content with an outdated browser, weakening web security controls that many applications rely on.

Technical view

CVE-2022-3056 is an insufficient policy enforcement issue in Chrome Content Security Policy before 105.0.5195.52. The CVSS 3.1 score is 6.5, network exploitable, low complexity, no privileges required, user interaction required, with high integrity impact.

Likely exposure

Exposure is most likely on managed or unmanaged endpoints running Google Chrome versions earlier than 105.0.5195.52. Gentoo and Fedora advisories indicate downstream Linux browser packages also required attention.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. It states a remote attacker could use a crafted HTML page to bypass CSP, and includes an exploit-tagged Chromium issue reference without establishing active exploitation.

Researcher notes

Evidence supports a CSP bypass in Chrome prior to 105.0.5195.52, mapped to CWE-693. Public details are limited, and the cited issue trackers should not be treated as proof of active exploitation without additional vendor confirmation.

Mitigation direction

  • Update Chrome to 105.0.5195.52 or later.
  • Apply vendor browser package updates from Linux distributions.
  • Check vendor advisories for any platform-specific remediation notes.
  • Prioritize managed endpoints where browser updates are delayed.
  • Retire or isolate unsupported Chrome installations.

Validation and detection

  • Inventory Chrome versions across endpoints.
  • Confirm no installed Chrome version is below 105.0.5195.52.
  • Verify Gentoo and Fedora browser packages are updated where applicable.
  • Check browser management reports for failed or deferred updates.
  • Review exposure of high-risk users to outdated browsers.
Prepared
Confidence
high
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-693: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-3056 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2022-3056Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleChromeunspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-693 · source CWE mapping

Protection Mechanism Failure

Protection Mechanism Failure represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.