CVE-2024-52940
Published: 18 November 2024
Summary
CVE-2024-52940 is a high-severity Insertion of Sensitive Information into Log File (CWE-532) vulnerability in Anydesk (inferred from references). Its CVSS base score is 7.5 (High).
Operationally, ranked in the top 4.4% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
AnyDesk through version 8.1.0 on Windows exposes a user's public IP address in network traffic when the Allow Direct Connections setting is enabled. The flaw, tracked as CVE-2024-52940 and assigned CWE-532, carries a CVSS 7.5 score reflecting network-accessible information disclosure without authentication. The condition requires only that an attacker already knows the target's AnyDesk ID.
An attacker in possession of a valid AnyDesk ID can observe the exposed IP address in traffic generated by the application, enabling subsequent targeting such as geolocation, direct network reconnaissance, or follow-on attacks against the revealed endpoint. No authentication or user interaction on the victim side is needed beyond the default configuration that permits direct connections.
The supplied references include AnyDesk's changelog, a public tool for detecting remote IPs via the client, and related social-media discussion, but contain no explicit mitigation statements or patch details. The associated EPSS score has remained flat at 0.1996 with no material increase since disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-45974
Vulnerability details
AnyDesk through 8.1.0 on Windows, when Allow Direct Connections is enabled, inadvertently exposes a public IP address within network traffic. The attacker must know the victim's AnyDesk ID.
- 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.
Procedures mandate excluding sensitive data from logs to prevent unauthorized exposure via audit records.
Identifies insertion of sensitive data into logs, allowing detection of unauthorized disclosure.
Cross-organizational coordination enables agreement on what data to include in audit logs, directly reducing insertion of sensitive information.
Identifying logging as a data action allows prevention of sensitive information being inserted into log files.
The process of identifying and eradicating spilled information applies directly to sensitive data inserted into log files.
Specific processing rules for sensitive PII categories commonly include restrictions on logging, making insertion of such data into log files less likely.
PIAs detect planned or existing logging of PII and require removal or protection, preventing insertion of sensitive information into logs.
Limits insertion of sensitive operational details into logs by treating such data as key information requiring protection.