Security readout for executives and security teams
Plain-English summary
This is a Google Chrome Blink flaw that could let a malicious web page spoof parts of the user interface. The business risk is phishing or user deception, not confirmed system takeover. Chrome versions before 99.0.4844.51 are the stated concern.
Executive priority
Treat this as routine but necessary browser patching. It supports phishing-style deception and should be closed through standard endpoint update controls, especially on user workstations with broad internet access.
Technical view
CVE-2022-4922 is described as an inappropriate implementation in Blink allowing remote UI spoofing via crafted HTML. Chromium rated it Medium. The bundle provides no CVSS, CWE, or detailed root-cause data, and the Chromium bug may not be fully public.
Likely exposure
Organizations are most exposed where managed desktops or laptops still run Google Chrome before 99.0.4844.51. Fedora users should also review the referenced distribution package advisory for applicable Chromium package status.
Exploitation context
The sources describe remote exploitation through a crafted HTML page, but do not state active exploitation. The CVE is not listed as KEV in the provided bundle, so active exploitation should not be assumed.
Researcher notes
Evidence is limited to a concise CVE description, Chrome release reference, Chromium bug reference, and Fedora package advisory. No exploit details, CVSS vector, CWE, or public proof-of-concept status are provided in the bundle.
Mitigation direction
- Update Google Chrome to 99.0.4844.51 or later.
- Check vendor and distribution advisories for exact fixed package versions.
- Use browser management tooling to enforce updates across endpoints.
- Prioritize outdated browsers used for email, web, and privileged administration.
Validation and detection
- Inventory Chrome versions across managed endpoints.
- Confirm Chrome is 99.0.4844.51 or later.
- Review Fedora Chromium package status if Fedora systems are in scope.
- Check browser management reports for update failures or unmanaged browsers.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2022-4922 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://chromereleases.googleblog.com/2022/03/stable-channel-update-for-desktop.htmlCVE reference
- https://crbug.com/1261191CVE reference
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PQKT7EGDD2P3L7S3NXEDDRCPK4NNZNWJ/CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.