CVE-2025-2562
Published: 26 March 2025
Summary
CVE-2025-2562 is a medium-severity Insufficient Logging (CWE-778) vulnerability in Devolutions Remote Desktop Manager. Its CVSS base score is 5.4 (Medium).
Operationally, ranked in the top 47.1% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-8233
Vulnerability details
Insufficient logging in the autotyping feature in Devolutions Remote Desktop Manager on Windows allows an authenticated user to use a stored password without generating a corresponding log event, via the use of the autotyping functionality. This issue affects Remote Desktop…
more
Manager versions from 2025.1.24 through 2025.1.25, and all versions up to 2024.3.29.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Audit policy requires defining and implementing logging of security-relevant events, directly reducing insufficient logging.
Providing proof of performed actions necessitates sufficient logging of security-relevant events with attribution details.
Retaining audit records for a defined period ensures security-relevant events remain available for after-the-fact investigations, directly mitigating the risk that attackers can hide actions due to missing or purged log data.
Directly requires generation of audit records for specified events, preventing the absence of logging that allows undetected malicious activity.
Directly implements detailed session logging to address the weakness of insufficient logging.
Provides alternate logging mechanism to maintain audit trails when primary capability fails, directly reducing insufficient logging.
Employing coordination mechanisms ensures consistent and sufficient logging practices are applied when audit information crosses organizational boundaries.
This control requires identifying, specifying, and justifying event types for logging with a focus on adequacy for post-incident investigations, directly mitigating insufficient logging.