LiveActive security incident?Get immediate response
CVE Record

CVE-2022-3049: Use after free in SplitScreen in Google Chrome on Chrome OS, Lacros prior to 105.0.5195.52 allowed a remote...

Use 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.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This Chrome issue could let a malicious web page corrupt memory if a user performs specific UI interactions. The listed scope is Chrome on Chrome OS, including Lacros, before 105.0.5195.52. It is high severity, but the provided sources do not show active exploitation.

Executive priority

Treat this as a high-priority browser patching item, especially for managed Chrome OS fleets. The business risk is user-driven compromise through web content, not confirmed widespread exploitation.

Technical view

CVE-2022-3049 is described as a use-after-free in SplitScreen causing potential heap corruption via crafted HTML. CVSS 3.1 is 8.8: network reachable, low complexity, no privileges, user interaction required. The bundle also lists CWE-362, so weakness taxonomy is not fully consistent.

Likely exposure

Organizations are exposed if managed Chrome OS or Lacros installations remain below 105.0.5195.52. General Chrome exposure beyond the named Chrome OS/Lacros scope is not clearly established by the bundle.

Exploitation context

The attack requires a remote actor to convince a user to visit crafted HTML and perform specific UI interactions. No KEV listing or provided source indicates known active exploitation.

Researcher notes

Public details are limited. The source bundle identifies SplitScreen, crafted HTML, user interaction, and heap corruption, but does not provide safe reproduction details. Note the mismatch between use-after-free wording and CWE-362 classification.

Mitigation direction

  • Update Chrome OS and Lacros to 105.0.5195.52 or later where applicable.
  • Apply vendor or distribution Chromium updates from Google, Gentoo, or Fedora channels.
  • Prioritize managed devices that browse untrusted websites or handle sensitive data.
  • Check vendor guidance for any platform-specific remediation not captured in the bundle.

Validation and detection

  • Inventory Chrome OS and Lacros versions across managed endpoints.
  • Confirm vulnerable builds are below 105.0.5195.52.
  • Verify update deployment status through endpoint or browser management telemetry.
  • Review security tooling for alerts tied to malicious HTML or Chrome heap corruption.
Prepared
Confidence
medium
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-362: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-3049 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2022-3049Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleChromeunspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-362 · source CWE mapping

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.