CVE-2025-61932 CrowdStrike LogScale · LogScale

Detect Motex LANSCOPE Endpoint Manager - Improper Verification of Communication Channel Source (CVE-2025-61932) in CrowdStrike LogScale

CVE-2025-61932 is an Improper Verification of Source of a Communication Channel (CWE-940) vulnerability in Motex LANSCOPE Endpoint Manager. This flaw allows an attacker to send commands or data through a communication channel without proper verification of the channel's origin, potentially enabling unauthorized control over managed endpoints. The vulnerability is listed in CISA's Known Exploited Vulnerabilities catalog, indicating active exploitation in the wild. Attackers may abuse this to impersonate the LANSCOPE management server and push malicious instructions to endpoint agents.

MITRE ATT&CK

Tactic
Initial Access Lateral Movement Impact

LogScale Detection Query

CrowdStrike LogScale (LogScale)
cql
#event_simpleName=NetworkConnectIP4 OR #event_simpleName=DnsRequest
| ImageFileName=/lanscope|lsepagent|epagent|lsep/i
| RemotePort in (80, 443, 8080, 8443)
| stats count() as connection_count, array_agg(RemoteAddressIP4) as remote_ips, array_agg(RemotePort) as remote_ports by aid, ComputerName, ImageFileName, UserName
| where connection_count > 0
| sort connection_count desc
| limit 500
high severity medium confidence

CrowdStrike Falcon query to identify LANSCOPE Endpoint Manager process network activity, supporting detection of CVE-2025-61932 where agents may be communicating with unauthorized command sources.

Data Sources

CrowdStrike Falcon EDRFalcon Data ReplicatorCrowdStrike Event Search

Required Tables

NetworkConnectIP4DnsRequestProcessRollup2

False Positives & Tuning

  • Normal LANSCOPE agent heartbeat and check-in traffic to authorized management servers
  • CrowdStrike sensor running alongside LANSCOPE on the same host causing process name collisions
  • LANSCOPE installations where the binary naming convention differs from expected patterns
  • Agents performing bulk data upload during policy synchronization windows

Other platforms for CVE-2025-61932


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 LANSCOPE Agent Connection to Rogue Management Server

    Expected signal: DeviceNetworkEvents showing outbound connection to 192.0.2.100:8443 from powershell.exe; Sysmon Event ID 3 network connection; Windows Firewall log entry for outbound blocked/allowed connection

  2. Test 2LANSCOPE Agent Configuration Tampering via Registry

    Expected signal: Sysmon Event ID 13 (Registry value set) for HKCU\SOFTWARE\TestLANSCOPE keys; Windows Security Event ID 4657 (registry value modified) if audit registry is enabled; EDR registry modification alert

  3. Test 3DNS Query to Suspicious LANSCOPE Management Domain

    Expected signal: DNS query logs showing resolution attempt for test-mgmt.example-lab.local; network connection attempt to port 8080; process execution logs showing nslookup/dig/curl invocation; endpoint network telemetry from EDR

Unlock Pro Content

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

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections