LiveActive security incident?Get immediate response
CVE Record

CVE-2022-4916: Use after free in Media in Google Chrome prior to 103.0.5060.53 allowed a remote attacker to perform arbitr...

Use after free in Media in Google Chrome prior to 103.0.5060.53 allowed a remote attacker to perform arbitrary read/write via a crafted HTML page. (Chromium security severity: High)

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-4916 is a high-severity Chrome media bug. A malicious web page could trigger memory misuse and allow arbitrary read/write in affected Chrome versions before 103.0.5060.53. For leaders, this is a browser exposure issue: reduce risk by ensuring endpoints use fixed, supported Chrome or Chromium packages.

Executive priority

Treat as high priority endpoint hygiene. It affects a widely used browser and can be triggered through web content, but the provided sources do not show active exploitation. Update and verify browser fleets promptly, especially where browser patch reporting is weak.

Technical view

The issue is a CWE-416 use-after-free in Google Chrome Media. The CVE describes remote arbitrary read/write via a crafted HTML page. CVSS 3.1 is 8.8 with network attack vector, low complexity, no privileges required, and user interaction required. Chromium severity is High.

Likely exposure

Organizations are exposed where users run Google Chrome, or downstream Chromium packages, older than 103.0.5060.53. Exposure depends on endpoint browser inventory, unmanaged devices, VDI images, and Linux distribution package status. The bundle names Chrome and Fedora package advisories, but does not enumerate all downstream Chromium-based products.

Exploitation context

The source bundle does not show known active exploitation, and KEV is false. The CVE states exploitation would require a crafted HTML page and user interaction. No source in the bundle provides public exploit maturity, attack campaign details, or exploitation-in-the-wild evidence.

Researcher notes

Evidence is limited to the CVE description, Chrome stable release reference, Chromium bug link, and Fedora advisories. The bundle does not provide deeper root-cause details, exploit primitives beyond arbitrary read/write, or confirmation of exploitation. Avoid expanding affected scope beyond Chrome and cited downstream packages.

Mitigation direction

  • Update Google Chrome to 103.0.5060.53 or later.
  • Apply relevant Fedora Chromium package updates where Fedora systems are in scope.
  • Check vendor guidance for other Chromium-based browsers before assuming coverage.
  • Prioritize managed endpoints, VDI images, kiosks, and shared workstations.
  • Ensure browser auto-update policies are enabled and reporting successfully.

Validation and detection

  • Inventory Chrome and Chromium versions across managed endpoints.
  • Confirm Chrome reports 103.0.5060.53 or a later supported build.
  • Review Linux package manager records for applied Chromium security updates.
  • Check EDR or device management data for stale browser versions.
  • Verify browser update policies cover unmanaged or exception groups.
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-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-4916 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-4916Attack 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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleChrome103.0.5060.53Listed
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.