SafeBreach specialisten ontdekte een gevaarlijke bug in McAfee antivirus producten. De kwetsbaarheid CVE-2019-3648 treft McAfee Total Protection (MTP), McAfee Anti-Virus Plus (AVP), en McAfee Internet Security (WAT) beveiligingsoplossingen.
De oorzaak van het probleem is dat McAfee-producten het DLL-bestand proberen te laden (wbemcomn.dll) met het verkeerde bestandspad.
'In onze verkenning, we found that multiple services of the McAfee software which run as signed processes and as NT AUTHORITY\ SYSTEM try to load c:\Windows\System32\wbem\wbemcomn.dll, which cannot be found (since it is actually located in System32 and not in the System32\Wbem folder)”, – schrijven SafeBreach specialisten.
Als gevolg, the attacker gets the opportunity to create his own malicious version of wbemcomn.dll, place it in a directory where the antivirus is trying to detect the file, which will ultimately lead to the file downloading and its launch without any checks.
Lees ook: Genoemd drie Amerikaanse antivirus producenten, gekraakt door Fxmsp band
To exploit the vulnerability, attacker will need administrator rights. If this condition has been met, the bug allows bypassing the protective mechanisms of McAfee antivirus products and load unsigned DLLs into various services working with NT AUTHORITY\SYSTEM rights.
“We suspected that a vulnerability could be exploited if we could load an arbitrary unsigned DLL into these processes. This would enable us to bypass the self-defense mechanism of the antivirus software, mainly because the folders of the McAfee software are protected by a mini-filter filesystem driver, which restricts writing operations even by an Administrator”, – explain SafeBreach researchers.
This ability might be abused by an attacker for different purposes such as execution and evasion, Bijvoorbeeld: Application Whitelisting Bypass.
It will also provide the attacker with a stable presence in the system, because malicious code from the DLL will be executed with every restart of the services.
Researchers told McAfee specialists about the problem back in August of this year, and by now the vulnerability has already been fixed. Users of vulnerable products are advised to upgrade to version 16.0.R22 Refresh 1.
