Hi @vtgt ,
The vulnerability is being analyzed by Labs. We shall have an update soon.
Thanks
Was my reply helpful?
If you find this post useful, Please give it a Kudos! Also, Please don't forget to select "Accept as a solution" if this reply resolves your query!
Hello,
Does have McAfee a update on a solution? 20 hours is a long delay for a severe security issue.
Thank you
Jean-Luc
Any update yet? I would hope McAfee/Trellix would get something out for this ASAP
Hi @Pravas , any news?
Thanks!
There is a temp workaround using an Exploit Protection Custom Rule
Search Git Hub for "Block_Ofice_Code_Execution.md
Rule {
Process {
Include OBJECT_NAME { -v "WINWORD.exe" }
Include OBJECT_NAME { -v "EXCEL.exe" }
Include OBJECT_NAME { -v "OUTLOOK.exe"}
}
Target {
Match PROCESS {
Include OBJECT_NAME { -v "msdt.exe" }
Include -access "CREATE"
}
}
}
Cheers
Phil
Hi Team,
Thank you for reporting your query on the cve - CVE-2022-30190: Microsoft Windows Support Diagnostic Tool (MSDT) Remote Code Execution Vulnerability, AKA Follina.
Our McAfee Labs have specifically recommended the below expert rule as a part of our various methods to fight against this vulnerability:
https://github.com/advanced-threat-research/Expert-Rules/blob/main/Block_Office_Code_Execution.md
NOTE: Before implementing the Expert Rule, it's suggested the rule is thoroughly tested. Thorough testing ensures rule integrity. It also ensures that no legitimate application, in-house developed or otherwise, is deemed malicious and prevented from functioning in your production environment. The rule can be set in report-only mode for testing purposes to check whether it causes any conflict in the our environment. Once you confirm that the rules don't block any activity from legitimate applications, the rule can be set to block and apply these settings to all relevant systems.
Also, SHA256:4a24048f81afbe9fb62e7a6a49adbd1faf41f266b5f9feecdceb567aec096784 has been analyzed by our Labs team and we already have detection for this file as of today via GTI.
The following samples were also proactively collected and analyzed by us for detection as follows:
\document.xml.rels - MD5:5f15a9b76ad6ba5229cb427ad7c7a4f6 - W97M/Downloader.dvf
\document.xml.rels - MD5:a3e94fd11e32dd66348135f879667b1d - W97M/Downloader.dvf
\document.xml.rels - MD5:364ce0c636fef9d961a5e416e2caefdf - W97M/Downloader.dvf
\document.xml.rels - MD5:56ff69f88e33d56b8f7083ba39df16fe - W97M/Downloader.dvf
By next 2 to 3 business days, we expect the same file to be detected via DAT content as well. As of now, I have attached EXTRA DAT file that should help you with the detection effective immediately when applied.
I followed the solution from this thread: Solved: McAfee Enterprise Support Community - How to block Microsoft Store on McAfee ePo? - McAfee E...
Replace "WinStore.App.exe" with "msdt.exe." This effectively stops all execution of msdt.exe, which is not a necessary application (and now, is a red carpet attack vector). I have Endpoint Security (ENS), so I know those steps worked for me.
-------
To block the execution of Microsoft store msdt.exe, you should be having an endpoint product such as "Endpoint security " with Threat prevention module or "VirusScan Enterprise" installed in the EPO managed client machine.
To Block the execution of the an application we should know the process name. Hence, run the application and find the process name from the task manager . In this case, when I check from windows 10, it is "WinStore.App.exe" msdt.exe
Now, we will have to add the an "Access Protection" rule to block the execution of WinStore.App.exe msdt.exe
Note :
We recommend you to test this rule in one or two machines before applying it to complete organization. So, you will have to duplicate an existing policy .
How to duplicate the existing policy :
VirusScan Enterprise 8.8.0 -> Access Protection policies (If VirusScan enterprise).
How to add the Access Protection rule to the duplicated policy for "VirusScan Enterprise":
How to add the Access Protection rule to the duplicated policy for "Endpoint security":
Execute
Rename
Now, assign this policy to a single machine for testing:
Give a wakeup agent to the client machine.
From the client machine, make sure it received the policy.
Try to open the "windows store msdt.exe" application…..
It should be blocked.
Thank you for reaching us on community, Hope the above steps help you."
credit to @rfranci of McAfee
Extra DAT Follina.zip has been released if you are needed an Extra DAT file before the V3 DAT file is released
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.
Thousands of customers use our Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership: