cbcvebase.
CVE-2022-4178
published 2022-11-30

CVE-2022-4178: Use after free in Mojo in Google Chrome prior to 108.0.5359.71 allowed a remote attacker who had compromised the renderer process to potentially exploit heap…

PriorityP261high8.8CVSS 3.1
AVNACLPRNUIRSUCHIHAH
EPSS
23.92%
97.6th percentile
Use after free in Mojo in Google Chrome prior to 108.0.5359.71 allowed a remote attacker who had compromised the renderer process to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

Affected

9 ranges
VendorProductVersion rangeFixed in
chromiumchromium>= 0 < 108.0.5359.71-2~deb11u1108.0.5359.71-2~deb11u1
chromiumchromium>= 0 < 108.0.5359.71-1108.0.5359.71-1
chromiumchromium>= 0 < 108.0.5359.71-1108.0.5359.71-1
chromiumchromium>= 0 < 108.0.5359.71-1108.0.5359.71-1
debianchromium< chromium 108.0.5359.71-1 (bookworm)chromium 108.0.5359.71-1 (bookworm)
googlechrome< 108.0.5359.71108.0.5359.71
googlechrome>= unspecified < 108.0.5359.71108.0.5359.71
googlechrome_chrome——
msrcmicrosoft_edge——

Detection & IOCsextracted from sources · hover to see the quote

  • →Vulnerability requires attacker to have already compromised the renderer process; exploit chain likely involves a prior renderer RCE bug before this UAF in Mojo is triggered ↗
  • →Trigger vector is a crafted HTML page delivered remotely; monitor for suspicious HTML/JS content targeting Mojo IPC interfaces in Chrome/Edge ↗
  • →Affected component is Mojo IPC in Google Chrome versions prior to 108.0.5359.71; flag any Chrome/Edge processes running versions below this threshold ↗
  • ·Exploitation requires a pre-compromised renderer process, meaning this UAF is a sandbox escape primitive rather than an initial access vector; detection should focus on post-renderer-compromise lateral movement within the browser process ↗
  • ·The Chromium security severity is rated High but no public exploit code or in-the-wild exploitation was referenced in any of the provided sources ↗
  • ·Debian scope is listed as 'local', which may affect how enterprise detection rules are tuned for network-based vs. local exploitation scenarios ↗

CVSS provenance

nvdv3.18.8HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
osv8.8HIGH
vendor_debian8.8HIGH
vendor_msrc8.8HIGH
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.