Describe the behaviour you want to detect. SARA writes a starting Sigma rule with MITRE tags, false-positive guidance, and detection-engineering context. Anonymous, no account, best-effort generic detection.
VALIDT1203T1203.002
Sigma rule
title: Potential CVE-2009-1537 Exploitation via Office Web Components ActiveX
id: 52c62ea7-ca08-490c-af54-654ecab3e87a
status: experimental
description: |
Detects potential exploitation of CVE-2009-1537 (CISA KEV listed), a remote code execution vulnerability in Microsoft Office Web Components (OWC) ActiveX controls.
This rule looks for the instantiation of the vulnerable OWC10.dll or OWC11.dll controls by Office applications or Internet Explorer, which may indicate exploitation via a malicious document or web page.
Note: This rule is a starting point — tune for your environment. OWC is a legacy component and may not be present on modern systems; presence of these DLLs loading via Office/IE is highly suspicious.
references:
- https://nvd.nist.gov/vuln/detail/CVE-2009-1537
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog
author: SARA Detection Engineering
date: 2026-08-15
tags:
- attack.execution
- attack.t1203
- attack.t1203.002
logsource:
category: image_load
product: windows
detection:
selection_vulnerable_dll:
ImageLoaded|endswith:
- '\OWC10.dll'
- '\OWC11.dll'
selection_host_process:
Image|endswith:
- '\WINWORD.EXE'
- '\EXCEL.EXE'
- '\POWERPNT.EXE'
- '\iexplore.exe'
filter_legitimate_office_components:
Image|endswith:
- '\WINWORD.EXE'
- '\EXCEL.EXE'
- '\POWERPNT.EXE'
ImageLoaded|contains:
- '\Office10\'
- '\Office11\'
condition: selection_vulnerable_dll and selection_host_process and not filter_legitimate_office_components
falsepositives:
- Legacy applications that legitimately rely on Office Web Components for embedded spreadsheet or chart functionality (rare in modern environments).
level: high
Sigma is the open, vendor-neutral format for log-based detections. One rule, written once, converts to Splunk SPL, Elastic ES|QL, KQL for Microsoft Sentinel, Sumo, Chronicle, QRadar, and more. Detection engineers love it for the same reason ATT&CK is the lingua franca for tactics — Sigma is the lingua franca for the queries that detect them.
GuideHow to use this tool
Describe the behaviour you want to detect in plain English. Be specific — "PowerShell encoded command spawned by an Office process" wins over "PowerShell abuse".
SARA writes a starting Sigma rule with the right logsource, fields, MITRE ATT&CK tags, and false-positive guidance.
Copy the YAML or convert to your target backend. Then tune the rule for your environment — the output is a starting point, not a tested artifact.
When to useWhen is the Sigma generator the right move?
Closing a coverage gap fast
You've got a fresh write-up of a TTP and need a starting detection in your stack today. Generate, tune, ship.
Onboarding a junior detection engineer
Pair-program with SARA: the generator produces the skeleton, the engineer learns by tuning, the team commits the result.
Translating between backends
You have a rule in one query language; describe it in English and get the Sigma version + conversions to every other backend.
Sanity-checking a hypothesis
Sketch a detection idea in 30 seconds before investing in a full DE sprint.
API
Want this in your SOAR or SIEM?
SARA Open ships an OpenAI-compatible API. Call POST /api/v1/sigma — Plain English in, valid Sigma YAML out, with MITRE tags and false-positive guidance.