LiveActive security incident?Get immediate response
CVE Record

CVE-2022-2857: Use after free in Blink in Google Chrome prior to 104.0.5112.101 allowed a remote attacker to potentially e...

Use after free in Blink in Google Chrome prior to 104.0.5112.101 allowed a remote attacker 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

CVE-2022-2857 is a high-severity Chrome browser flaw in Blink. A malicious web page could trigger memory corruption if a user visits it, potentially affecting confidentiality, integrity, and availability. The supplied sources identify Chrome before 104.0.5112.101 as affected.

Executive priority

Treat this as a routine high-priority browser patching issue. The impact could be serious if outdated browsers remain in use, but the supplied evidence does not show active exploitation or KEV listing.

Technical view

The CVE describes a Blink use-after-free leading to potential heap corruption via crafted HTML. CVSS 3.1 is 8.8 with network attack vector, low complexity, no privileges, and required user interaction. The record also maps to CWE-362, indicating a race-condition classification in the source data.

Likely exposure

Organizations are exposed where Google Chrome versions prior to 104.0.5112.101 remain installed or OS browser packages have not received the vendor update. The bundle does not identify other affected products beyond Google Chrome.

Exploitation context

The source bundle supports remote exploitation through a crafted HTML page, with user interaction required. CISA KEV status is false, and the provided sources do not establish known active exploitation in the wild.

Researcher notes

The public description is limited: Blink use-after-free, crafted HTML trigger, and heap corruption outcome. The Chromium bug references are included, but the bundle does not provide enough detail to assess root cause, exploit reliability, or variant coverage.

Mitigation direction

  • Update Google Chrome to 104.0.5112.101 or later.
  • Apply browser updates from Fedora or other trusted OS package channels.
  • Prioritize managed endpoints where users browse untrusted websites.
  • Check Google and OS vendor guidance for any environment-specific remediation.

Validation and detection

  • Inventory Chrome versions across managed desktops and servers with browsers installed.
  • Confirm Chrome reports version 104.0.5112.101 or later.
  • Review Linux package status against the Fedora advisory where applicable.
  • Check patch deployment coverage for unmanaged or BYOD endpoints.
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-2857 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-2857Attack 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.