ChromeWeb browser · Google
CVE-2022-3051
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 · uneditedHeap buffer overflow in Exosphere in Google Chrome on Chrome OS, Lacros prior to 105.0.5195.52 allowed a remote attacker who convinced a user to engage in specific UI interactions to potentially exploit heap corruption via crafted UI interactions.
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 confidenceHeap buffer overflow vulnerability in Exosphere (Chrome OS graphics/compositing layer) in Google Chrome on Chrome OS and Lacros browsers prior to version 105.0.5195.52. A remote attacker can exploit this by tricking users into specific UI interactions, potentially leading to heap corruption.
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
< 105.0.5195.52
Linux And Chrome OsOperating system
all versions
FedoraOperating system
= 37CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Chrome browser versionNavigate to chrome://settings/help or run 'google-chrome --version' in terminalAffected if Version is less than 105.0.5195.52 and browser is running on Chrome OS or Lacros
-
Identify the operating systemRun 'uname -a' or check system information to determine if running Chrome OS or Linux with Lacros browserAffected if System is Chrome OS or Linux with Lacros enabled (Lacros is the Chrome OS graphics layer for Linux)
-
Verify Exosphere component presenceOn Chrome OS, check if Exosphere (graphics/compositing) is active by examining system logs or chrome://gpu outputAffected if Exosphere is loaded as the graphics compositor on the system
-
Check Fedora Chrome installationOn Fedora 37, run 'rpm -qa | grep google-chrome' to see if Chrome is installed, then check its versionAffected if Google Chrome is installed on Fedora 37 with version prior to 105.0.5195.52
User is affected if running Google Chrome on Chrome OS or Lacros with version below 105.0.5195.52, or on Fedora 37 with an unpatched Chrome version.
Generated from the published advisory. Verify against your own configuration.
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 · scoped105.0.5195.52
Update Google Chrome on Chrome OS and Lacros to version 105.0.5195.52 or later. Organizations should ensure auto-updates are enabled or push the browser update via their patch management systems.
Chrome 105.0.5195.52 or later
- Check current Chrome version by navigating to chrome://settings/help
- Upgrade Google Chrome to version 105.0.5195.52 or later via the browser's built-in update mechanism or from the official Chrome download page
- Restart the browser after the update completes
- For Fedora systems, ensure the system package manager is updated: sudo dnf update google-chrome-* (once a patched package is available in Fedora repositories)
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3051 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-3051 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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