I downloaded the malware sample to an endpoint running Comodo Client Security, fully updated. It doesn’t detect the sample as a threat and when I manual scan it says its clean. When turning on Windows Defender the file is detected right away and removed.
This is a concern that CCS is not detecting this potential threat even with updated definitions.
No I was merely testing signature detection/real-time protection since execution is not required with this 0-day, just having Explorer file preview open is enough to trigger the exploit:
Im just surprised since this seems to be getting a lot of attention and yet Comodo has no basic signature or real-time capability yet to detect these malicious payloads prior to execution.
I am hoping to build or get a script that deletes the ms-msdt registry key . Can someone help create this script? I have one I think might work. Can I post it here for your review?
Yes the best way to prevent an infection is to make sure your real-time protection can detect malicious code prior to it needing to executed. Containment is a great fail-safe, but no excuse to lack normal detections on a well reported 0-day especially with built in ‘free’ windows defender is detecting and quarantine them. Also will Comodo even intervene if we are talking Explorer preview pane, previewing the infected document? I don’t know I haven’t tested that, but I don’t recall Comodo running containment when previewing normal word docs in Explorer.