Response playbooks, investigation guides, and Atomic Red Team tests are Pro-only. Upgrade to unlock the full detection package for CVE-2026-61667.

Upgrade to Pro
CVE-2026-61667 CrowdStrike LogScale · LogScale

Detect DIRAC FileCatalog DatasetManager SQL Injection to RCE (CVE-2026-61667) in CrowdStrike LogScale

Detects exploitation attempts against DIRAC's FileCatalog DatasetManager component, where a SQL injection vulnerability (CWE-89) can be chained with unsafe eval() usage (CWE-95) to achieve remote code execution. Affects DIRAC versions >=6,<8.0.79; >=8.1.0a1,<9.0.22; >=9.1.0,<9.1.10. A public PoC exists (GHSA-m4m7-4cw8-62j6). Detection focuses on anomalous SQL error signatures, injection payload patterns in DatasetManager RPC calls, and subsequent process spawning from the DIRAC service process indicative of successful eval()-based code execution.

MITRE ATT&CK

Tactic
Initial Access Execution Lateral Movement

LogScale Detection Query

CrowdStrike LogScale (LogScale)
cql
#event_simpleName=ProcessRollup2
| ParentBaseFileName=/dirac/i
| in(field=FileName, values=["python*", "python3*", "sh", "bash"])
| join(query={#event_simpleName=NetworkConnectIP4 | RemotePort=9197 OR RemotePort=9198}, field=aid, key=aid, mode=inner)
| table([ComputerName, ParentBaseFileName, FileName, CommandLine, RemoteAddressIP4, RemotePort, timestamp])
critical severity medium confidence

Correlates process creation events spawned from the DIRAC service parent process with prior network connections to DatasetManager service ports, surfacing likely post-exploitation command execution.

Data Sources

CrowdStrike Falcon process telemetryFalcon network telemetry

Required Tables

ProcessRollup2NetworkConnectIP4

False Positives & Tuning

  • Legitimate operational scripts executed by DIRAC administrators via python subprocess
  • Health-check or monitoring agents that connect to the same service ports
  • Package manager or patching tools spawning shell processes coincidentally near service restarts

Other platforms for CVE-2026-61667


Testing Methodology

Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Simulate SQL injection payload against DatasetManager endpoint

    Expected signal: HTTP request log entry on the DIRAC service showing the injected payload in the request body/message field.

  2. Test 2Simulate eval()-based code execution payload

    Expected signal: Process creation event for a python/sh process spawned from the DIRAC service parent, with command line containing 'atomic_test_marker'.

  3. Test 3Simulate follow-on outbound connection from DIRAC service host

    Expected signal: Network connection event from the DIRAC service account/process to an external or lab listener IP shortly after the injection attempt.

Unlock playbooks & atomic tests with Pro

Get the full detection package for CVE-2026-61667 — response playbook and atomic red team tests, plus investigation guidance and hunting queries.

df00tech Pro — £29/user/month

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections