Detect Motex LANSCOPE Endpoint Manager - Improper Verification of Communication Channel Source (CVE-2025-61932) in IBM QRadar
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
QRadar Detection Query
SELECT DATEFORMAT(starttime,'YYYY-MM-dd HH:mm:ss') as EventTime, sourceip, destinationip, destinationport, username, "Application" as app_name, "EventID" as event_id, CATEGORYNAME(category) as category_name, logsourcename(logsourceid) as log_source
FROM events
WHERE LOGSOURCETYPENAME(devicetype) IN ('Microsoft Windows Security Event Log', 'Sysmon', 'CrowdStrike Falcon')
AND (LOWER("Application") LIKE '%lanscope%' OR LOWER("Application") LIKE '%lsepagent%' OR LOWER("Application") LIKE '%epagent%')
AND destinationport IN (80, 443, 8080, 8443)
AND starttime > NOW() - 86400000
ORDER BY starttime DESC
LIMIT 1000QRadar AQL query to identify LANSCOPE Endpoint Manager agent communication events for review against known-good management server baselines, supporting detection of CVE-2025-61932 exploitation attempts.
Data Sources
Required Tables
False Positives & Tuning
- Legitimate LANSCOPE management traffic from newly provisioned or relocated servers
- Remote work scenarios where agents connect over internet to management infrastructure
- Third-party security tools running within LANSCOPE agent processes or sharing process names
- QRadar DSM parsing issues causing process name fields to reflect unexpected values
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.