LiveActive security incident?Get immediate response
CVE Record

CVE-2022-3051: Heap buffer overflow in Exosphere in Google Chrome on Chrome OS, Lacros prior to 105.0.5195.52 allowed a re...

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

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-3051 is a high-severity Chrome issue where crafted UI interactions could corrupt memory. An attacker would need to convince a user to perform specific interactions, but successful exploitation could affect confidentiality, integrity, and availability.

Executive priority

Treat this as a high-priority browser patching issue. It is not cited as actively exploited here, but browser memory corruption with high impact and low attack complexity warrants prompt remediation across managed endpoints.

Technical view

The CVE describes a CWE-787 heap buffer overflow in Exosphere affecting Google Chrome on Chrome OS and Lacros prior to 105.0.5195.52. CVSS 3.1 is 8.8, network reachable, low complexity, no privileges required, and user interaction required.

Likely exposure

Exposure is indicated for Chrome on Chrome OS and Lacros before 105.0.5195.52. Gentoo and Fedora references indicate downstream Chromium package updates. The bundle does not identify other affected products or deployment-specific conditions.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Exploitation is described as remote but requiring user interaction through crafted UI interactions, with potential heap corruption.

Researcher notes

Key constraints are user interaction and the Exosphere component. Public details in the bundle are limited; do not assume exploit availability, affected platforms beyond those named, or mitigations beyond vendor and distro updates.

Mitigation direction

  • Update Chrome OS/Lacros Chrome to 105.0.5195.52 or later.
  • Apply Gentoo or Fedora Chromium updates where those packages are deployed.
  • Prioritize managed browser update enforcement for affected endpoint groups.
  • Check Google and distribution advisories for any newer vendor guidance.

Validation and detection

  • Inventory Chrome OS, Lacros, and Chromium versions across managed endpoints.
  • Confirm affected Chrome installations are at least 105.0.5195.52.
  • Verify Gentoo and Fedora package updates referenced by advisories are installed.
  • Document exceptions and track them until vendor-supported remediation is complete.
Prepared
Confidence
high
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-787: 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-3051 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-3051Attack 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-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.