LiveActive security incident?Get immediate response
CVE Record

CVE-2022-4909: Inappropriate implementation in XML in Google Chrome prior to 107.0.5304.62 allowed a remote attacker to po...

Inappropriate implementation in XML in Google Chrome prior to 107.0.5304.62 allowed a remote attacker to potentially perform an ASLR bypass via a crafted HTML page. (Chromium security severity: Low)

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

A flaw in Chrome's XML handling before 107.0.5304.62 could let a remote attacker use a crafted HTML page to weaken ASLR. Sources rate the Chromium issue Low. This is not described as code execution by itself, but it could reduce a protection that limits exploitation of other browser bugs.

Executive priority

Handle through normal browser patch governance, not emergency response. The issue is low severity and lacks cited active exploitation, but browsers are high-exposure assets and ASLR bypasses can support larger exploit chains. Ensure update coverage is complete.

Technical view

CVE-2022-4909 is an inappropriate implementation issue in Chrome XML processing. The reported impact is a potential ASLR bypass through crafted HTML. The bundle provides no CVSS, CWE, or public exploit details. Chrome 107.0.5304.62 is identified as the fixed desktop release; Fedora advisories indicate downstream Chromium package updates.

Likely exposure

Exposure is limited to systems running Google Chrome or relevant Chromium packages older than 107.0.5304.62. The attack surface is normal browsing of untrusted web content. The provided sources do not identify other affected products or environments.

Exploitation context

The source bundle does not show CISA KEV inclusion or other evidence of active exploitation. The described condition is remote and web-deliverable via crafted HTML, but the stated result is an ASLR bypass, not standalone compromise. Risk increases if paired with another browser exploitation primitive.

Researcher notes

The public record is sparse. Chrome describes the bug class and possible ASLR bypass, but the linked bug may restrict details. Avoid assuming memory corruption, exploitability beyond bypass, or affected products outside Chrome/Chromium without additional vendor evidence.

Mitigation direction

  • Update Google Chrome to 107.0.5304.62 or later, preferably the current supported release.
  • Apply downstream Chromium package updates from Linux distribution vendors where applicable.
  • Prioritize managed browser update compliance across user workstations and shared browsing systems.
  • If immediate update is blocked, reduce exposure to untrusted browsing until patched.

Validation and detection

  • Inventory Chrome and Chromium versions across managed endpoints.
  • Confirm installed versions are 107.0.5304.62 or later.
  • Review Linux package manager records for Fedora or downstream Chromium security updates.
  • Check vulnerability scanners for remaining CVE-2022-4909 findings after patching.
Prepared
Confidence
medium
Sources
6

Public sources used

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.

cve · low confidence lookup

CVE-2022-4909 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleChrome107.0.5304.62Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.