On some azure machines at work, I removed the OMI updater crontab entry for root, killed running procs and deleted everything in /opt/omi
I hope that should do it...
I hope that should do it...
It's worth mentioning many of these features which deploy OMI do so in a way that does not set up a listening port. Therefore, the impact of the vulnerability is pretty low. Indeed, I just spun up a Ubuntu VM and while it got a vulnerable version of OMI, it doesn't have an open port.
The LA table VMBoundPort will let you assess if you've got one configured for listening on the OMI ports. I think a lot of the people in this thread, and possibly the people writing the articles aren't Azure SME's, hence all the panic and grumbling and eye rolling.
Also I don't care about the monitoring and analytics, so there's that