Detect Motex LANSCOPE Endpoint Manager - Improper Verification of Communication Channel Source (CVE-2025-61932) in Elastic Security
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
Elastic Detection Query
sequence by host.name, process.name with maxspan=5m
[network where process.name like~ "*lanscope*" or process.name like~ "*lsepagent*" or process.name like~ "*epagent*"
and destination.port in (80, 443, 8080, 8443)
and not destination.ip like "10.*" and not destination.ip like "192.168.*" and not destination.ip like "172.16.*"]
[network where process.name like~ "*lanscope*" or process.name like~ "*lsepagent*" or process.name like~ "*epagent*"
and destination.port in (80, 443, 8080, 8443)]EQL sequence detection for LANSCOPE agent processes making repeated external network connections, potentially to adversary-controlled infrastructure mimicking the LANSCOPE management server.
Data Sources
Required Tables
False Positives & Tuning
- LANSCOPE agents communicating with cloud-hosted legitimate management servers over public IPs
- Split-tunnel VPN configurations routing LANSCOPE traffic through external gateways
- Endpoint roaming scenarios where devices connect to management infrastructure over the internet
- Initial agent enrollment connecting to vendor cloud endpoints for license validation
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.
- 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
- 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
- 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.