The flaw was bad news for Windows domains, with Microsoft confirming that attackers were using this vulnerability to install specially crafted packages and spread the Emotet/Trickbot/Bazaloader malware families. The Windows AppX Installer is a Windows 10 feature that allows users to install .appx packages. SEE: Windows 11: Here’s how to get Microsoft’s free operating system update In a blogpost explaining why it’s switched off the ms-appinstaller protocol for the MSIX Windows app package format, Microsoft says that an attacker can use that protocol to “spoof App Installer to install a package that the user did not intend to install”. For now, it appears Microsoft hasn’t fully addressed the vulnerability detailed in its December advisory for CVE-2021-43890. With protocol disabled, admins could see the download size for some app packages grow, and create a block for enterprises that distribute apps directly from a web page versus, say, the Microsoft Store. “We are actively working to address this vulnerability,” Microsoft says in a blogpost. “For now, we have disabled the ms-appinstaller scheme (protocol). This means that App Installer will not be able to install an app directly from a web server. Instead, users will need to first download the app to their device, and then install the package with App Installer. This may increase the download size for some packages.” As Microsoft explains, MSIX brings a “modern packaging experience” to legacy Windows apps. “The MSIX package format preserves the functionality of existing app packages and/or install files in addition to enabling new, modern packaging and deployment features to Win32, WPF, and Windows Forms apps,” Microsoft notes. Microsoft has also updated its page for installing Windows 10 apps from a web page to reflect ms-appinstaller being disabled. Microsoft has a few workarounds in mind until it is able to re-enable the protocol, including “looking into introducing a Group Policy that would allow IT administrators to re-enable the protocol and control usage of it within their organizations.” But it notes: “We recognize that this feature is critical for many enterprise organizations. We are taking the time to conduct thorough testing to ensure that re-enabling the protocol can be done in a secure manner.”
