CVE-2022-37968CriticalMicrosoft CVSS 10.0CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H/E:U/RL:O/RC:C

Microsoft security update for CVE-2022-37968 — Azure

Published
October 11, 2022
Last Modified
—

🔗 CVE IDs covered (1)

CVE-2022-37968 →

📋 Microsoft's advisory

EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-37968. This page also shows what EchelonGraph holds for CVE-2022-37968, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.

🎯 Affected products5

  • Azure Arc-enabled Kubernetes cluster 1.5.8
  • Azure Arc-enabled Kubernetes cluster 1.6.19
  • Azure Arc-enabled Kubernetes cluster 1.7.18
  • Azure Arc-enabled Kubernetes cluster 1.8.11
  • Azure Stack Edge

✅ Updates Microsoft lists: 5 updates

5 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.

KB articleUpdateFixed build
—Security Update1.8.11
—Security Update1.7.18
—Security Update1.5.8
—Security Update1.6.19
—Security Update2.2.2088.5593

🧭 EchelonGraph on CVE-2022-37968

EchelonGraph score
10.0 CRITICAL
CISA KEV
Not listed
Fix status
A fix is available — apply it.

Description from the CVE record (CVE.org), as published by its numbering authority

Microsoft has identified a vulnerability affecting the cluster connect feature of Azure Arc-enabled Kubernetes clusters. This vulnerability could allow an unauthenticated user to elevate their privileges and potentially gain administrative control over the Kubernetes cluster. Additionally, because Azure Stack Edge allows customers to deploy Kubernetes workloads on their devices via Azure Arc, Azure Stack Edge devices are also vulnerable to this vulnerability.

Published by Microsoft Corporation, the CVE Numbering Authority that assigned CVE-2022-37968, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).

🔗 References (3)