Skip to content
Server Security Center
KEVhigh8.8

CVE-2022-3723: Google Chromium V8 Type Confusion

Google Chromium V8 · listed in the CISA catalog of actively exploited vulnerabilities since 2022-10-28.

CVSS v3.1 (CVE record)
8.8
high
EPSS (exploit probability, 30 days)
7.9%
higher than 94.8% of all CVEs
Added to CISA KEV
2022-10-28
US federal due date 2022-11-18
Ubuntu priority
medium

CVE-2022-3723 explained

CVE-2022-3723 is a type confusion flaw in the V8 JavaScript engine used by Google Chrome and Chromium before 107.0.5304.87. A remote attacker could use a crafted HTML page to potentially exploit heap corruption. CISA lists it as known to be exploited, so patching browsers promptly matters.

Impact

An attacker who gets a user to open a crafted HTML page could potentially corrupt heap memory in the browser. Per the CVSS components, the attack works over the network, needs low complexity and no privileges, but requires user interaction. A successful attack can have high impact on confidentiality, integrity and availability within the affected browser's scope.

Who is affected

The facts list one affected release: Ubuntu 18.04 LTS, source package chromium-browser. A fixed version, 107.0.5304.87-0ubuntu11.18.04.1, is published in the standard archive. Standard support for Ubuntu 18.04 LTS has ended, and further fixes for that release are only available 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

Type confusion in V8 in Google Chrome prior to 107.0.5304.87 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

CISA required action: Apply updates per vendor instructions.

CISA notes

Upstream versions (CVE record)

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

  • Google Chrome
    Affected
    • < 107.0.5304.87
    Fixed in
    • 107.0.5304.87

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. Update chromium-browser on Ubuntu 18.04 LTS to 107.0.5304.87-0ubuntu11.18.04.1 or later.
  2. Close and restart all running Chromium instances so the patched code is loaded.
  3. Plan an upgrade to a supported Ubuntu release, or enable Ubuntu Pro (ESM) for continued fixes on 18.04.
  4. Follow the vendor and distribution advisories for any later Chromium security updates.

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-843 Access of Resource Using Incompatible Type ('Type Confusion')

Questions about CVE-2022-3723

Is CVE-2022-3723 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-10-28, with a US federal due date of 2022-11-18. Its required action is to apply updates per vendor instructions. Known ransomware use is listed as unknown.
Does updating the package protect users immediately?
Only after Chromium is restarted. Browser processes already running keep using the old code until they are closed and reopened.
Why is the Ubuntu priority medium when the CVSS severity is high?
The CVSS base severity is high, while Ubuntu assigns its own priority of medium. Both are listed in the facts. Given the known exploitation, treat the update as urgent regardless.

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.