ChromeWeb browser · Google
CVE-2022-3049
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 · uneditedUse after free in SplitScreen 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 a crafted HTML page.
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 confidenceUse-after-free vulnerability in Chrome's SplitScreen feature (Chrome OS/Lacros) prior to version 105.0.5195.52 allows a remote attacker who tricks a user into specific UI interactions via a crafted HTML page to potentially exploit 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
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 Google Chrome versionOpen chrome://version in the browser address bar or navigate to Chrome menu > Help > About Google Chrome. Locate the version number listed.Affected if The displayed version is less than 105.0.5195.52
-
Verify Chrome installation package version on FedoraIf running Fedora 37, run the command: rpm -q google-chrome-stableAffected if No package is returned or the installed version is lower than 105.0.5195.52-1
-
Confirm environment is Chrome OS or LacrosThis vulnerability affects Chrome OS and Lacros (a lightweight Chrome shell on Chrome OS). Check the OS by looking at the system UI or running: cat /etc/os-release on Linux or viewing system information.Affected if The browser is running on Chrome OS or Lacros with the SplitScreen feature available
-
Determine if SplitScreen feature is in useThe vulnerability requires interaction with the SplitScreen feature. On Chrome OS, SplitScreen is activated by dragging a window to the left or right edge of the screen, or via the overview mode (press Overview key or Search+Equals).Affected if The user has used or is using SplitScreen functionality in Chrome OS or Lacros while running an affected version
A user is affected if they are running Google Chrome or Lacros on Chrome OS with a version lower than 105.0.5195.52 and have access to or use the SplitScreen feature.
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/Lacros to version 105.0.5195.52 or later; apply browser security patches through standard patch management.
Chrome 105.0.5195.52 or later
- Update Google Chrome to version 105.0.5195.52 or later. On Linux systems with Chrome installed from repositories (including Fedora 37), run: sudo dnf update google-chrome-stable or sudo dnf update chrome-*. The Chrome browser also auto-updates; verify current version by navigating to chrome://settings/help
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3049 — 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-3049 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