How to block below from ENS. Not able to find below rule
07/03/2018 23:07:34 mfetp(12560.14136) <SYSTEM> TmpLogger.BoBl.Activity: Content update request received. Verifying the content package (C:\ProgramData\McAfee\Agent\Current\ENDPCNT_1000\DAT\0000\EXP_20180206_08231_ENDP_AM_1000.zip).
07/03/2018 23:07:39 mfetp(12560.14136) <SYSTEM> TmpLogger.BoBl.Activity: Content package verified, applying update...
07/03/2018 23:08:32 mfetp(12560.14136) <SYSTEM> TmpLogger.BoBl.Activity: Content update succeeded. Exploit Prevention content version: 10.5.0.8231
08/03/2018 07:06:45 mfetp(12560.9488) <SYSTEM> TmpLogger.Gbop.Activity: ExP:Illegal API Use was detected as an attempt to exploit C:\WINDOWS\SYSWOW64\WINDOWSPOWERSHELL\V1.0\POWERSHELL.EXE, which targeted the AtlComPtrAssign API. It wasn't blocked because Exploit Prevention was set to Report Only.
08/03/2018 07:06:45 mfetp(12560.9488) <SYSTEM> TmpLogger.Gbop.Activity: ExP:Illegal API Use was detected as an attempt to exploit C:\WINDOWS\SYSWOW64\WINDOWSPOWERSHELL\V1.0\POWERSHELL.EXE, which targeted the AtlComPtrAssign API. It wasn't blocked because Exploit Prevention was set to Report Only.
08/03/2018 15:40:50 mfetp(12560.9488) <SYSTEM> TmpLogger.Gbop.Activity: ExP:Illegal API Use was detected as an attempt to exploit C:\WINDOWS\SYSWOW64\WINDOWSPOWERSHELL\V1.0\POWERSHELL.EXE, which targeted the AtlComPtrAssign API. It wasn't blocked because Exploit Prevention was set to Report Only.
08/03/2018 15:40:50 mfetp(12560.9488) <SYSTEM> TmpLogger.Gbop.Activity: ExP:Illegal API Use was detected as an attempt to exploit C:\WINDOWS\SYSWOW64\WINDOWSPOWERSHELL\V1.0\POWERSHELL.EXE, which targeted the AtlComPtrAssign API. It wasn't blocked because Exploit Prevention was set to Report Only.
08/03/2018 15:42:05 mfetp(12560.9488) <SYSTEM> TmpLogger.Gbop.Activity: ExP:Heap Blocked an attempt to exploit C:\WINDOWS\SYSWOW64\MSIEXEC.EXE, which targeted the VirtualProtect API.
08/03/2018 18:01:22 mfetp(6364.10440) <SYSTEM> TmpLogger.Gbop.Activity: ExP:Illegal API Use was detected as an attempt to exploit C:\WINDOWS\SYSWOW64\WINDOWSPOWERSHELL\V1.0\POWERSHELL.EXE, which targeted the AtlComPtrAssign API. It wasn't blocked because Exploit Prevention was set to Report Only.
08/03/2018 18:01:22 mfetp(6364.10440) <SYSTEM> TmpLogger.Gbop.Activity: ExP:Illegal API Use was detected as an attempt to exploit C:\WINDOWS\SYSWOW64\WINDOWSPOWERSHELL\V1.0\POWERSHELL.EXE, which targeted the AtlComPtrAssign API. It wasn't blocked because Exploit Prevention was set to Report Only.
Solved! Go to Solution.
Hello,
Recently I had the same issue and this is what I found out:
1. By default this Exploit Prevention rule ID 6073 is disabled.
2. It indicates the following vulnerability:
3. The execution policy bypass is associated with some types of malware activity so it could be an indication of exploit. You can find additional details about Execution policy details here:
https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.security/set-executionpolicy...
4. The API reported is this one:
https://msdn.microsoft.com/en-us/library/40d27a83.aspx
5. In case the alarm still pops up on this or multiple systems, you can perform deeper investigation and collect samples from that machine to check for ongoing malware activity.
Same here. Getting this multiple times per day from different computers. I am hesitant to permit it especially with a category of host intrusion buffer overflow. Only on Win 10 so far.
i am assuming this is firing on the Generic Buffer Overflow Protection rule.
Gbop = Generic Buffer Overflow Protection
Powershell being a defined protected process.
is the Generic Buffer Overflow Protection rule set to report only in the assigned EP policy?
6070 - Hidden Powershell Detected rule is firing. Block and Report.
Hello,
Recently I had the same issue and this is what I found out:
1. By default this Exploit Prevention rule ID 6073 is disabled.
2. It indicates the following vulnerability:
3. The execution policy bypass is associated with some types of malware activity so it could be an indication of exploit. You can find additional details about Execution policy details here:
https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.security/set-executionpolicy...
4. The API reported is this one:
https://msdn.microsoft.com/en-us/library/40d27a83.aspx
5. In case the alarm still pops up on this or multiple systems, you can perform deeper investigation and collect samples from that machine to check for ongoing malware activity.
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: