Rule ID 6044: Vulnerability in DNSAPI Allow Remote Code Execution

[Spooky10111]

Does anyone know why this rule is detecting MfeEpNfcp.sys as being vulnerable Threat Name Detecting Product Name Detecting Product Version Threat Source IP address Threat Handled Action Taken Target Path Target Parent Process Name Analyzer Rule Name Threat Target File Path ExP:NIPS Violation McAfee Endpoint Security 10.7.0.2522 10.249.184.133 TRUE Would block C:\WINDOWS\system32\drivers Vulnerability in DNSAPI Allow Remote Code Execution C:\WINDOWS\system32\drivers\MfeEpNfcp.sys

[AdithyanT]

Hi @Spooky10111,

Thank you for your post. This is a behavior by design for NIPS signature based detection and should not be taken as a false positive.

NIPS detections very, very commonly will either list MfeEpNfcp.sys as the target file, or list nothing as the target file, because in most cases this is not relevant to the detection at hand and hence we point to the driver that is used in detection. The network addresses and ports are the important piece of data to investigate when a NIPS detection is triggered. I sincerely hope this helps!

[Spooky10111]

Hi @AdithyanT  

I have both network addresses which both have TP and ATP but the ports fields are blank, how would I go about investigating these events

Kind Regards

Lesiba Sephoka

[AdithyanT]

Hi @Spooky10111,

Thank you for your response. You can refer to a similar post in community that talks about the same detection:

https://community.mcafee.com/t5/Endpoint-Security-ENS/Rule-ID-Reference/td-p/643325

Essentially, This detection is to do with the source IP trying to send a malicious request and hence your machine, being the target with ENS installed, is blocking it as it should. Any investigation on this matter should be carried against the source IP. if the source does not belong to your network, I would recommend blocking it from your Gateway Firewall.