LiveActive security incident?Get immediate response
CVE Record

CVE-2022-4920: Heap buffer overflow in Blink in Google Chrome prior to 101.0.4951.41 allowed a remote attacker who convinc...

Heap buffer overflow in Blink in Google Chrome prior to 101.0.4951.41 allowed a remote attacker who convinced a user to engage in specific UI gestures to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)

CriticalCVSS 9.6Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This Chrome flaw could let a malicious web page break out of Chrome’s sandbox after convincing a user to perform specific UI gestures. That raises the business risk from browser compromise to possible broader system impact. The source bundle does not show confirmed active exploitation.

Executive priority

Prioritize remediation quickly because browser sandbox escape issues can convert routine web browsing into high-impact endpoint risk. The urgency is high, but the provided evidence does not support claiming active exploitation.

Technical view

CVE-2022-4920 is a CWE-787 heap buffer overflow in Blink affecting Google Chrome before 101.0.4951.41. The CVSS 3.1 score is 9.6 with network attack vector, required user interaction, changed scope, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely on endpoints running Google Chrome older than 101.0.4951.41. Fedora package references indicate downstream package relevance, but the supplied sources do not provide enough detail to name additional affected products beyond Chrome.

Exploitation context

The described attack requires a crafted HTML page and user engagement with specific UI gestures. CISA KEV is false in the supplied bundle, and no cited source here confirms active exploitation. Treat exploit availability as unproven from this evidence.

Researcher notes

Key constraints are user interaction and specific UI gestures. The public description is high level, and the Chromium bug reference may not expose full technical detail. Validate by version and package state, not by attempting exploitation.

Mitigation direction

  • Upgrade Google Chrome to 101.0.4951.41 or later.
  • Confirm managed browser update policies are enforcing the fixed version.
  • For Fedora Chromium packages, check the cited Fedora advisories and apply available updates.
  • Prioritize internet-facing user endpoints and high-privilege administrator workstations.
  • Follow current vendor guidance if newer downstream package instructions differ.

Validation and detection

  • Inventory Chrome versions across endpoint management and vulnerability tools.
  • Flag Chrome installations older than 101.0.4951.41.
  • Verify patched endpoints report the updated browser version after restart.
  • Check Fedora systems for relevant Chromium package advisory status.
  • Review browser crash or security telemetry, without assuming exploitation.
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
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-4920 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
Critical
CVSS
9.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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
9.6CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H2.86Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.6Critical
CVSS 3.1 vector shape for CVE-2022-4920Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleChrome101.0.4951.41Listed
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.