{"id":18792,"date":"2021-09-16T22:41:19","date_gmt":"2021-09-16T18:41:19","guid":{"rendered":"https:\/\/me-en.kaspersky.com\/blog\/vulnerabilities-in-omi-azure\/18792\/"},"modified":"2021-09-16T22:41:19","modified_gmt":"2021-09-16T18:41:19","slug":"vulnerabilities-in-omi-azure","status":"publish","type":"post","link":"https:\/\/me-en.kaspersky.com\/blog\/vulnerabilities-in-omi-azure\/18792\/","title":{"rendered":"OMI vulnerabilities threaten Linux virtual machines on Microsoft Azure"},"content":{"rendered":"<p>News <a href=\"https:\/\/www.wiz.io\/blog\/secret-agent-exposes-azure-customers-to-unauthorized-code-execution\" target=\"_blank\" rel=\"nofollow noopener\">has surfaced<\/a> of a rather dangerous practice in Microsoft Azure, whereby when a user creates a Linux virtual machine and enables certain Azure services, the Azure platform automatically installs the Open Management Infrastructure (OMI) agent on the machine. The user won\u2019t know it.<\/p>\n<p>Although a stealth installation might sound terrible on its face, this one actually wouldn\u2019t be so bad were it not for two issues: First, the agent has known vulnerabilities, and second, the agent has no automatic update mechanism in Azure. Until Microsoft solves this problem on its end, organizations using Linux virtual machines on Azure will need to take action.<\/p>\n<h2>Vulnerabilities in the Open Management Infrastructure, and how attackers can exploit them<\/h2>\n<p>On September\u2019s Patch Tuesday, Microsoft released security updates for four vulnerabilities in the Open Management Infrastructure agent. One of them, <a href=\"https:\/\/msrc.microsoft.com\/update-guide\/vulnerability\/CVE-2021-38647\" target=\"_blank\" rel=\"nofollow noopener\">CVE-2021-38647<\/a>, allows <a href=\"https:\/\/encyclopedia.kaspersky.com\/glossary\/remote-code-execution-rce\/\" target=\"_blank\" rel=\"noopener\"> remote code execution (RCE)<\/a> and is critical, and the other three, <a href=\"https:\/\/msrc.microsoft.com\/update-guide\/vulnerability\/CVE-2021-38648\" target=\"_blank\" rel=\"nofollow noopener\">CVE-2021-38648<\/a>, <a href=\"https:\/\/msrc.microsoft.com\/update-guide\/vulnerability\/CVE-2021-38645\" target=\"_blank\" rel=\"nofollow noopener\">CVE-2021-38645<\/a>, and <a href=\"https:\/\/msrc.microsoft.com\/update-guide\/vulnerability\/CVE-2021-38649\" target=\"_blank\" rel=\"nofollow noopener\">CVE-2021-38649<\/a>, can be used for <a href=\"https:\/\/encyclopedia.kaspersky.com\/glossary\/privilege-escalation\/\" target=\"_blank\" rel=\"noopener\">privilege escalation (LPE)<\/a> in multistage attacks when attackers have penetrated a victim\u2019s network in advance. These three vulnerabilities score high on the CVSS.<\/p>\n<p>When Microsoft Azure users create a Linux virtual machine and enable a series of services, OMI \u2014vulnerabilities and all \u2014 deploys in the system automatically. The services include Azure Automation, Azure Automatic Update, Azure Operations Management Suite, Azure Log Analytics, Azure Configuration Management, and Azure Diagnostics, a list that is probably far from complete. The Open Management Infrastructure agent on its own has the highest privileges in the system, and because its tasks include collecting statistics and syncing configurations, it is generally accessible from the Internet through various HTTP ports, depending on the services enabled.<\/p>\n<p>For example, if the listening port is 5986, attackers could potentially exploit the CVE-2021-38647 vulnerability and execute malicious code remotely. If the OMI is available for remote management (through port 5986, 5985, or 1270), outsiders can exploit the same vulnerability to gain access to the entire network neighborhood in Azure. Experts say the vulnerability is very easy to exploit.<\/p>\n<blockquote class=\"twitter-tweet\" data-width=\"500\" data-dnt=\"true\">\n<p lang=\"en\" dir=\"ltr\">This is even more severe. The RCE is the simplest RCE you can ever imagine. Simply remove the auth header and you are root. remotely. on all machines. Is this really 2021? <a href=\"https:\/\/t.co\/iIHNyqgew4\" target=\"_blank\" rel=\"noopener nofollow\">pic.twitter.com\/iIHNyqgew4<\/a><\/p>\n<p>\u2014 Ami Luttwak (@amiluttwak) <a href=\"https:\/\/twitter.com\/amiluttwak\/status\/1437898746747097090?ref_src=twsrc%5Etfw\" target=\"_blank\" rel=\"noopener nofollow\">September 14, 2021<\/a><\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script><\/p>\n<p>So far, no in-the-wild attacks have been reported, but with a lot of information available about how easy it exploiting these vulnerabilities would be, it probably won\u2019t be long.<\/p>\n<h2>How to protect yourself<\/h2>\n<p>Microsoft has released patches for all four vulnerabilities. However, OMI does not always automatically update, so you\u2019ll need to check to see which version is deployed on your Linux virtual machine. If it\u2019s older than 1.6.8.1, update the Open Management Infrastructure agent. To see how, refer to the description of the <a href=\"https:\/\/msrc.microsoft.com\/update-guide\/vulnerability\/CVE-2021-38647\" target=\"_blank\" rel=\"nofollow noopener\">CVE-2021-38647<\/a> vulnerability.<\/p>\n<p>Experts also recommend restricting network access to ports 5985, 5986, and 1270 to prevent anyone from running RCE.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The Open Management Infrastructure agent, with four vulnerabilities, is being automatically installed on virtual Linux machines on Microsoft Azure.<\/p>\n","protected":false},"author":2581,"featured_media":18793,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1318,1916,1917],"tags":[2493,533,38,268],"class_list":{"0":"post-18792","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-business","8":"category-enterprise","9":"category-smb","10":"tag-azure","11":"tag-linux","12":"tag-microsoft","13":"tag-vulnerabilities"},"hreflang":[{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/vulnerabilities-in-omi-azure\/18792\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/vulnerabilities-in-omi-azure\/23305\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/vulnerabilities-in-omi-azure\/25371\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/vulnerabilities-in-omi-azure\/23452\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/vulnerabilities-in-omi-azure\/22852\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/vulnerabilities-in-omi-azure\/25976\/"},{"hreflang":"it","url":"https:\/\/www.kaspersky.it\/blog\/vulnerabilities-in-omi-azure\/25558\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/vulnerabilities-in-omi-azure\/31483\/"},{"hreflang":"tr","url":"https:\/\/www.kaspersky.com.tr\/blog\/vulnerabilities-in-omi-azure\/10060\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/vulnerabilities-in-omi-azure\/41977\/"},{"hreflang":"fr","url":"https:\/\/www.kaspersky.fr\/blog\/vulnerabilities-in-omi-azure\/17610\/"},{"hreflang":"pt-br","url":"https:\/\/www.kaspersky.com.br\/blog\/vulnerabilities-in-omi-azure\/18124\/"},{"hreflang":"pl","url":"https:\/\/plblog.kaspersky.com\/vulnerabilities-in-omi-azure\/15271\/"},{"hreflang":"de","url":"https:\/\/www.kaspersky.de\/blog\/vulnerabilities-in-omi-azure\/27374\/"},{"hreflang":"ja","url":"https:\/\/blog.kaspersky.co.jp\/vulnerabilities-in-omi-azure\/31634\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/vulnerabilities-in-omi-azure\/24347\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/vulnerabilities-in-omi-azure\/29691\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/vulnerabilities-in-omi-azure\/29485\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/me-en.kaspersky.com\/blog\/tag\/vulnerabilities\/","name":"vulnerabilities"},"_links":{"self":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/18792","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/users\/2581"}],"replies":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=18792"}],"version-history":[{"count":0,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/18792\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/18793"}],"wp:attachment":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=18792"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=18792"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=18792"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}