LiveActive security incident?Get immediate response
CVE Record

CVE-2022-2858: Use after free in Sign-In Flow in Google Chrome prior to 104.0.5112.101 allowed a remote attacker to potent...

Use after free in Sign-In Flow in Google Chrome prior to 104.0.5112.101 allowed a remote attacker to potentially exploit heap corruption via specific UI interaction.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-2858 is a high-severity Chrome flaw in the sign-in flow. A remote attacker could potentially trigger memory corruption if a user performs specific UI interaction. For executives, this is a browser exposure issue: patching managed endpoints is the main urgency, especially where Chrome updates are delayed or unmanaged.

Executive priority

High priority for browser patch management, but not an emergency based only on the supplied evidence. Address quickly through standard endpoint update controls and verify coverage across unmanaged or slow-moving systems.

Technical view

The issue is a CWE-416 use-after-free in Google Chrome Sign-In Flow before 104.0.5112.101. CVSS 3.1 is 8.8 with network attack vector, low complexity, no privileges required, and required user interaction. Sources describe potential heap corruption but provide limited public technical detail.

Likely exposure

Exposure is likely on systems running Google Chrome before 104.0.5112.101 or downstream Chromium packages that had not received vendor updates. Highest concern is unmanaged endpoints, stale desktop images, Linux package lag, and environments where browser auto-update is disabled.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. Exploitation requires user interaction through specific UI behavior. Public details are limited, so defenders should not infer reliable exploitation mechanics from the available record.

Researcher notes

The public record identifies use-after-free and heap corruption potential, but detailed bug content may be restricted. Do not assume affected forks, mobile products, exploit availability, or exploit reliability unless confirmed by vendor-specific evidence.

Mitigation direction

  • Update Google Chrome to 104.0.5112.101 or later.
  • Apply relevant Linux distribution Chromium package updates.
  • Confirm browser auto-update is enabled on managed endpoints.
  • Check Google and distribution vendor advisories for current guidance.
  • Prioritize unmanaged, kiosk, VDI, and BYOD browser coverage.

Validation and detection

  • Inventory Chrome and Chromium versions across endpoints.
  • Flag Chrome versions earlier than 104.0.5112.101.
  • Verify Fedora or other distro packages include the vendor fix.
  • Review endpoint management policies for disabled browser updates.
  • Confirm patched browser versions after reboot or relaunch.
Prepared
Confidence
medium
Sources
5

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-416: 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-2858 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
4Source 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-2858Attack 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-416 · source CWE mapping

Use After Free

Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.