CVE-2025-40551 Google Chronicle · YARA-L

Detect CVE-2025-40551 — SolarWinds Web Help Desk Deserialization RCE in Google Chronicle

Detects exploitation of CVE-2025-40551, a deserialization of untrusted data vulnerability in SolarWinds Web Help Desk. Successful exploitation allows unauthenticated or low-privileged attackers to achieve remote code execution on the WHD server. This CVE is listed in CISA KEV, indicating active exploitation in the wild.

MITRE ATT&CK

Tactic
Initial Access Execution Persistence

YARA-L Detection Query

Google Chronicle (YARA-L)
yaral
rule cve_2025_40551_whd_deserialization_rce {
  meta:
    author = "df00tech"
    description = "Detects potential CVE-2025-40551 SolarWinds Web Help Desk deserialization RCE via suspicious child processes"
    severity = "CRITICAL"
    reference = "https://www.solarwinds.com/trust-center/security-advisories/cve-2025-40551"
  events:
    $parent.metadata.event_type = "PROCESS_LAUNCH"
    re.regex($parent.principal.process.file.full_path, `(?i)(java|javaw|tomcat|whd)`) nocase
    re.regex($parent.target.process.file.full_path, `(?i)(cmd\.exe|powershell\.exe|wscript\.exe|cscript\.exe|mshta\.exe|certutil\.exe|bitsadmin\.exe|whoami\.exe|curl\.exe|wget\.exe)`) nocase
  condition:
    $parent
}
critical severity high confidence

Chronicle YARA-L 2.0 rule to detect suspicious process spawning from SolarWinds Web Help Desk Java/Tomcat processes, indicative of CVE-2025-40551 deserialization exploitation.

Data Sources

Chronicle UDMEndpoint Detection

Required Tables

UDM Events

False Positives & Tuning

  • Legitimate administrative scripts executed through the WHD service account
  • Security tools spawning under the Tomcat or Java process
  • Automated deployment or update tooling invoking shell processes
  • Developer environments running WHD locally with non-standard tooling

Other platforms for CVE-2025-40551


Testing Methodology

Validate this detection against 4 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 WHD Deserialization RCE — Whoami Execution

    Expected signal: ProcessCreate event with ParentImage=java.exe and Image=whoami.exe; captured by Sysmon EventID 1 or Defender DeviceProcessEvents

  2. Test 2Simulate WHD Deserialization RCE — PowerShell Reverse Shell Stub

    Expected signal: ProcessCreate with ParentImage=java.exe, Image=powershell.exe, CommandLine containing '-NoProfile'; network telemetry if actual reverse shell payload used

  3. Test 3Simulate WHD Web Shell Drop via Java Process

    Expected signal: FileCreate event for shell.jsp under WHD webapps directory, initiated by java.exe; Sysmon EventID 11 or DeviceFileEvents

  4. Test 4Simulate WHD Outbound C2 Callback from Java Process (Linux)

    Expected signal: Network connection from java or curl process to external IP on non-standard port; captured by auditd, Falco, or network flow telemetry

Unlock Pro Content

Get the full detection package for CVE-2025-40551 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections