dbcve.org
ChromeWeb browser · Google

CVE-2022-4176

HIGH · 8.8 CVSS v3.1 Published 2022-11-30
Fix available
A fix is available. Upgrade to 108.0.5359.71 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Out of bounds write in Lacros Graphics in Google Chrome on Chrome OS and Lacros prior to 108.0.5359.71 allowed a remote attacker who convinced a user to engage in specific UI interactions to potentially exploit heap corruption via UI interactions. (Chromium security severity: High)

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is an out-of-bounds write vulnerability in the Lacros Graphics component of Google Chrome on Chrome OS. Lacros is the browser window process separate from the Chrome OS shell. The flaw allows a remote attacker who tricks a user into specific UI interactions to write beyond allocated memory boundaries, potentially corrupting the heap and achieving arbitrary code execution.

MitigationUpdate Google Chrome/Lacros to version 108.0.5359.71 or later. In enterprise environments, ensure Chrome OS update policies are enforced across all affected devices.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ChromeWeb browser
Affected:< 108.0.5359.71

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Google Chrome version
    Navigate to chrome://settings/help in the browser address bar, or use the menu: Help > About Google Chrome. The version number will be displayed on the page that opens.
    Affected if The displayed version is earlier than 108.0.5359.71 (for example, 107.0.5354.134 or lower).
  2. Confirm running on Chrome OS
    Open chrome://os-settings in the browser address bar. If the page loads successfully with Chrome OS settings, the browser is running on Chrome OS.
    Affected if The browser is running on Chrome OS. This vulnerability only applies to the Lacros component on Chrome OS, not to standard Chrome on other platforms.
  3. Verify Lacros is enabled
    Navigate to chrome://flags/#lacros-profile-selection in the address bar. Look for the 'Lacros' or 'Lacros profile selection' flag. If the flag is present and set to Enabled, Lacros is active.
    Affected if Lacros is enabled on the Chrome OS device. The vulnerability exists specifically within the Lacros Graphics component, so Lacros must be running for the flaw to be exploitable.
  4. Check Chrome browser channel
    In chrome://settings/help, look for the version details. It may indicate 'Stable', 'Beta', 'Dev', or 'Canary' channel. Alternatively, check the Chrome OS version in Settings > About Chrome OS.
    Affected if The browser is on a channel other than Stable (such as Beta, Dev, or Canary), as these channels often receive updates later or may run pre-release versions that could be affected.

A user is affected if they are running Google Chrome on Chrome OS with Lacros enabled and the Chrome version is earlier than 108.0.5359.71.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 108.0.5359.71 or later
Fixed in 108.0.5359.71
Interim mitigation

Update Google Chrome/Lacros to version 108.0.5359.71 or later. In enterprise environments, ensure Chrome OS update policies are enforced across all affected devices.

Recommended fix High confidence

108.0.5359.71 or later

  1. Open Chrome and navigate to chrome://settings/help to check the current version
  2. If the version is lower than 108.0.5359.71, click 'Update Google Chrome' to install the latest version
  3. Restart Chrome to complete the update
  4. Verify the version is now 108.0.5359.71 or later via chrome://settings/help

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-4176 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-4176 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data