CVE-2022-33640

FAQ

How does this impact SCOM customers?

SCOM 2016, 2019, and 2022 customers who monitor Linux machines and use Kerberos-based authentication are impacted by this vulnerability.

How can an attacker exploit the vulnerability?

OMI supports Kerberos as one of the authentication mechanisms. This authentication mechanism is only used by SCOM, with no Azure service using it. A fixed temp file is used while keeping omi keytab in sync with the default keytab. The temp file can be manipulated by an attacker to insert a new key in the omi keytab and gain elevated privileges on the machine. The attacker must be locally logged in to the machine on which the OMI components are running.

What products are affected by this vulnerability and how can I protect myself?

The following table lists the affected services and the required customer action to protect against this vulnerability.

Does this vulnerability affect the Azure Services that use OMI?

Other Azure services are not impacted by this vulnerability as they do not use Kerberos-based authentication. A Linux VM that is being monitored by SCOM, where SCOM has been configured to use Kerberos-based authentication is the only scenario which is impacted.

What is OMI?

Open Management Infrastructure (OMI) is an open-source Web-Based Enterprise Management (WBEM) implementation for managing Linux and UNIX systems. Certain Azure Virtual Machine (VM) management extensions (listed here) use OMI to orchestrate configuration management and log collection on Linux VMs.

Refer to this link for more details: GitHub - microsoft/omi: Open Management Infrastructure