sudo cscli collections install crowdsecurity/windows-cveInstalls 2 parsers and 2 scenarios.
View Windows - CVE Detection →sudo cscli scenarios install crowdsecurity/windows-CVE-2022-30190-msdtThen reload CrowdSec: sudo systemctl reload crowdsec
Sign in to see which of your engines run it →Hover a line or a note to see what each field does.
type: triggername: crowdsecurity/CVE-2022-30190-msdtdescription: "Detect CVE-2022-30190 from sysmon events"filter: |evt.Meta.service == 'sysmon' && evt.Parsed.EventID == '1' &&Upper(evt.Parsed.Image) endsWith 'MSDT.EXE' &&Upper(evt.Parsed.ParentImage) endsWith 'WINWORD.EXE' &&(Upper(evt.Parsed.CommandLine) contains 'PCWDIAGNOSTIC' && Upper(evt.Parsed.CommandLine) contains 'IT_REBROWSEFORFILE' && Upper(evt.Parsed.CommandLine) contains 'IT_BROWSEFORFILE')labels:type: rcenotification: trueconfidence: 3spoofable: 0classification:- attack.T1059- attack.T1203- cve.CVE-2022-30190behavior: "windows:rce"label: "CVE-2022-30190"service: windowsscope:type: user_accountexpression: evt.Parsed.User
Sign in to see the Security Engines that run this attack scenario, the version they run and whether it was modified locally.
This scenario detects some attempts at exploiting CVE-2022-30190 on Windows.
It does so by parsing sysmon logs, more specifically the one with event ID 1 (process creation).
This means that you need a working sysmon installation to be able to use this scenario.