LiveActive security incident?Get immediate response
CVE Record

CVE-2022-2861: Inappropriate implementation in Extensions API in Google Chrome prior to 104.0.5112.101 allowed an attacker...

Inappropriate implementation in Extensions API in Google Chrome prior to 104.0.5112.101 allowed an attacker who convinced a user to install a malicious extension to inject arbitrary scripts into WebUI via a crafted HTML page.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-2861 is a Chrome Extensions API flaw fixed before version 104.0.5112.101. If a user installed a malicious extension, an attacker could use a crafted HTML page to inject scripts into Chrome WebUI. The main business concern is browser integrity compromise on endpoints running outdated Chrome with weak extension controls.

Executive priority

Treat this as a routine but important endpoint hygiene issue. Prioritize browser patch compliance and extension governance, not emergency incident response, unless local telemetry shows suspicious extension activity.

Technical view

Google describes this as an inappropriate implementation in Chrome's Extensions API, classified as CWE-79. The attack requires user interaction: installing a malicious extension and visiting crafted content. The CVSS 3.1 score is 6.5, with high integrity impact and no stated confidentiality or availability impact.

Likely exposure

Exposure is most likely on managed or unmanaged endpoints running Google Chrome before 104.0.5112.101, especially where users can install unapproved extensions. Fedora Chromium package consumers should also review the referenced Fedora advisory.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation. The documented path requires persuading a user to install a malicious extension, then leveraging crafted HTML to inject scripts into WebUI.

Researcher notes

Public details are limited. The Chrome bug reference is included, but the bundle does not provide exploit mechanics. The validated facts are the affected pre-104.0.5112.101 Chrome condition, Extensions API/WebUI script injection impact, CWE-79 mapping, and user-assisted malicious extension prerequisite.

Mitigation direction

  • Update Chrome to 104.0.5112.101 or later.
  • Apply relevant distribution browser updates, including Fedora guidance where applicable.
  • Restrict extension installation to approved, trusted extensions.
  • Review vendor guidance for any additional mitigations or affected package details.

Validation and detection

  • Inventory Chrome versions and flag anything earlier than 104.0.5112.101.
  • Review enterprise extension policies for unmanaged installation paths.
  • Audit installed extensions for unapproved or suspicious entries.
  • Confirm Linux package versions against the Fedora advisory if Fedora Chromium is used.
Prepared
Confidence
medium
Sources
5

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 · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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-2861 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
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:N/I:H/A:N

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
4Source 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
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2022-2861Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

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.