Skip to content
Server Security Center
KEVcritical9.6

CVE-2022-3075: Google Chromium Mojo Insufficient Data Validation

Google Chromium Mojo · listed in the CISA catalog of actively exploited vulnerabilities since 2022-09-08.

CVSS v3.1 (CVE record)
9.6
critical
EPSS (exploit probability, 30 days)
5.8%
higher than 93.2% of all CVEs
Added to CISA KEV
2022-09-08
US federal due date 2022-09-29
Ubuntu priority
medium

CVE-2022-3075 explained

CVE-2022-3075 is an insufficient data validation flaw in Mojo in Google Chrome before 105.0.5195.102. A remote attacker who has already compromised the renderer process could use a crafted HTML page to potentially escape the browser sandbox. It is listed in the CISA Known Exploited Vulnerabilities catalog, so prompt patching matters.

Impact

An attacker who already controls the renderer process could break out of the sandbox through a crafted HTML page. The attack works over the network, needs no privileges and has low complexity. A user must interact, for example by visiting the page. Scope is changed, so impact extends beyond the sandboxed component. Confidentiality, integrity and availability impact are all rated high.

Who is affected

The facts list one affected release. On Ubuntu 18.04 LTS, the chromium-browser source package is fixed in version 105.0.5195.102-0ubuntu0.18.04.1, published in the standard archive. Standard support for Ubuntu 18.04 LTS has ended, and further fixes for that release come only with Ubuntu Pro (ESM). No other releases or packages are listed in the facts.

Written with AI from the data on this page and checked against it automatically.

Official description

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.

Upstream versions (CVE record)

From the CVE record published by the vendor or CVE numbering authority.

  • Google Chrome
    Affected
    • < 105.0.5195.102
    Fixed in
    • 105.0.5195.102

Ubuntu and Debian releases

A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.

What to do

  1. Identify systems with the chromium-browser package installed on Ubuntu 18.04 LTS.
  2. Update chromium-browser to 105.0.5195.102-0ubuntu0.18.04.1 or later.
  3. Fully close and restart all running browser instances so the patched version is used.
  4. Plan an upgrade to a supported Ubuntu release, or enable Ubuntu Pro (ESM) to keep receiving fixes on 18.04.

Written with AI from the data on this page and checked against it automatically.

Check and fix on a server

Run on each Ubuntu or Debian server. Replace chromium-browser with the source package from the table above.

1. Show installed packages built from the source package, with their versions

dpkg-query -W -f='${binary:Package} ${Version} ${source:Package}\n' | awk '$3=="chromium-browser"'

2. Compare each installed version with the fixed version for your release from the table

I=INSTALLED_VERSION; F=FIXED_VERSION   # replace both
dpkg --compare-versions "$I" lt "$F"; case $? in 0) echo vulnerable ;; 1) echo "fixed or newer" ;; *) echo "check the versions" ;; esac

3. Install the fix

sudo apt update && sudo apt install --only-upgrade $(dpkg-query -W -f='${binary:Package} ${source:Package}\n' | awk '$2=="chromium-browser"{print $1}')

Services keep running the old code until they are restarted – restart the affected service or check with needrestart.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-20

Questions about CVE-2022-3075

Is this vulnerability being exploited?
Yes. CISA added CVE-2022-3075 to its Known Exploited Vulnerabilities catalog on 2022-09-08 and set a US federal due date of 2022-09-29. Its required action is to apply updates per vendor instructions. Whether it has been used in ransomware is unknown.
Does an attacker need prior access?
The attacker must already have compromised the renderer process. This flaw then allows a potential sandbox escape. A user must also interact, for example by loading a crafted HTML page.
Why is the CVSS severity critical when Ubuntu rates it medium?
The CVE record gives a CVSS 3.1 rating of critical. Ubuntu assigns its own priority, which is medium. Ubuntu's priority reflects its own assessment, separate from the CVSS score. Either way, a fixed package is available for Ubuntu 18.04 LTS and should be installed.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.