LiveActive security incident?Get immediate response
CVE Record

CVE-2022-3075: Insufficient data validation in Mojo in Google Chrome prior to 105.0.5195.102 allowed a remote attacker who...

Insufficient data validation in Mojo in Google Chrome prior to 105.0.5195.102 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page.

CriticalCVSS 9.6Known exploitedUpdated
Glexia's TakeHuman reviewedcritical

Security readout for executives and security teams

Plain-English summary

CVE-2022-3075 is a Chrome sandbox escape risk. A malicious web page could help an attacker who already compromised Chrome's renderer break out of browser isolation. Because CISA lists it as known exploited and the CVSS score is 9.6, unpatched Chrome before 105.0.5195.102 should be treated as urgent.

Executive priority

Treat this as a critical browser patching priority. CISA KEV status means exploitation has been observed, and browser sandbox escapes can turn routine web exposure into endpoint compromise risk. Patch broadly and verify coverage rather than relying on automatic updates alone.

Technical view

The flaw is insufficient data validation in Chrome's Mojo component before 105.0.5195.102. The CVSS vector is network-based, low complexity, no privileges required, user interaction required, scope changed, and high impact to confidentiality, integrity, and availability. The record describes sandbox escape after renderer compromise via crafted HTML.

Likely exposure

Exposure is most likely on user workstations, VDI images, and managed endpoints running Google Chrome before 105.0.5195.102. Linux environments using vendor-packaged Chromium/browser builds should review the Gentoo and Fedora advisories. The bundle does not identify other affected products.

Exploitation context

Active exploitation is supported by CISA KEV. The provided sources do not describe the exploit chain, target sectors, or public exploit availability. The vulnerability still requires user interaction and an already compromised renderer process, so it is most relevant in browser compromise chains.

Researcher notes

The strongest evidence is the CVE description, Chrome stable release reference, and KEV listing. The bug tracker reference is included, but the bundle provides no detailed root-cause analysis, proof-of-concept, or exploit telemetry. Avoid assuming exploitation mechanics beyond renderer compromise and crafted HTML.

Mitigation direction

  • Update Google Chrome to 105.0.5195.102 or later.
  • Apply OS vendor browser package updates where Gentoo or Fedora advisories apply.
  • Prioritize patching managed endpoints, VDI images, and shared workstations.
  • Check current vendor guidance for any additional mitigations or supported fixed versions.
  • Retire or isolate systems that cannot receive supported browser updates.

Validation and detection

  • Inventory Chrome versions across endpoint management and vulnerability tooling.
  • Confirm no managed endpoint reports Chrome earlier than 105.0.5195.102.
  • Review Linux package versions against Gentoo and Fedora advisory guidance.
  • Verify browser update policies are enabled and successfully applying updates.
  • Track remediation against CISA KEV obligations where applicable.
Prepared
Reviewed
Confidence
high
Sources
7

Michael Williams reviewed this cited source version on .

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.

description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-3075 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
Critical
CVSS
9.6 (3.1)
Known Exploited
Yes
Published

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

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

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

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
9.6CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H2.86Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.6Critical
CVSS 3.1 vector shape for CVE-2022-3075Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

No CWE listed

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