Security readout for executives and security teams
Plain-English summary
This Chrome flaw could let an attacker read potentially sensitive local file information after convincing a Windows user to install a malicious extension and visit crafted content. It is not a drive-by-only browser bug, but it matters because the possible impact is high confidentiality exposure.
Executive priority
Treat as a moderate-priority endpoint hygiene issue. Prioritize patch confirmation and extension governance across Windows fleets, but do not escalate as known actively exploited based on the provided evidence.
Technical view
CVE-2022-2160 is insufficient policy enforcement in Chrome DevTools on Windows before 103.0.5060.53. The CVSS 3.1 vector is 6.5 medium, requiring network delivery and user interaction, with no privileges, unchanged scope, high confidentiality impact, and no integrity or availability impact.
Likely exposure
Exposure is mainly Windows endpoints running Google Chrome before 103.0.5060.53, especially where users can install unapproved extensions. The source bundle lists affected versions as unspecified, so exact vulnerable build ranges beyond “prior to 103.0.5060.53” are not provided.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. The described attack requires persuading a user to install a malicious extension and interact with a crafted HTML page, so social engineering and extension control are central to risk.
Researcher notes
The public description identifies DevTools policy enforcement and CWE-362, but does not provide enough detail here to validate root cause. Avoid assuming exploitability without the malicious extension prerequisite and the Windows-specific affected product statement.
Mitigation direction
- Update Google Chrome on Windows to 103.0.5060.53 or later.
- Apply relevant Fedora or Gentoo browser package updates where those advisories apply.
- Restrict Chrome extension installation to approved extensions only.
- Review vendor guidance for any additional enterprise policy recommendations.
Validation and detection
- Inventory Windows Chrome versions and flag builds older than 103.0.5060.53.
- Check endpoint extension inventories for unapproved or suspicious Chrome extensions.
- Confirm browser update policies are enforcing current Chrome releases.
- Review security telemetry for recent unauthorized extension installation events.
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.
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 lookupCVE-2022-2160 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
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N2.83.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://chromereleases.googleblog.com/2022/06/stable-channel-update-for-desktop_21.htmlCVE reference, Chrome · x_refsource_MISC
- https://crbug.com/1116450CVE reference, Chrome · x_refsource_MISC
- FEDORA-2022-0102ccc2a2CVE reference, Chrome · vendor-advisory, x_refsource_FEDORA
- FEDORA-2022-1d3d5a0341CVE reference, Chrome · vendor-advisory, x_refsource_FEDORA
- GLSA-202208-25CVE reference, Chrome · vendor-advisory, x_refsource_GENTOO
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.
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.