VulnerabilityPublished 18 Nov 2024Updated 23 Nov 2024

CVE-2024-52940: anydesk · Sensitive Data in Logs

Affects anydeskSource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 8.1.1 soon.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 1.2% chance of exploitation in 30 days – higher than 69% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 8.1.1

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade anydesk/anydesk to 8.1.1.

Affected software

Product	Affected	Fixed in
GitHubanydesk/anydesk`pkg:github/anydesk/anydesk`Other threats	Affected <8.1.1	Fixed in 8.1.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-52940, organizations should consider the following specific actions: 1) Disable the 'Allow Direct Connections' feature in AnyDesk settings until a patch is available, as this is the root cause of the IP leakage. 2) Restrict AnyDesk usage to trusted networks and VPNs that mask or control public IP exposure. 3) Monitor network traffic for unexpected AnyDesk connections or unusual data flows that could indicate reconnaissance attempts. 4) Educate users about the risks of sharing their AnyDesk ID publicly or with untrusted parties. 5) Implement network-level controls such as firewall rules to limit inbound connections to AnyDesk services only from known IP ranges. 6) Stay informed on AnyDesk security advisories and apply patches promptly once released. 7) Consider alternative remote access solutions with stronger privacy protections if direct connections are essential. These steps go beyond generic advice by focusing on configuration changes, network controls, and user awareness tailored to this specific vulnerability.

Description

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.

Impact

The primary impact of CVE-2024-52940 is the exposure of the victim's public IP address, which can compromise user privacy and enable attackers to perform targeted reconnaissance. Organizations relying on AnyDesk for remote access may inadvertently reveal network topology details, increasing the risk of follow-on attacks such as targeted phishing, network intrusion attempts, or denial-of-service attacks against exposed IPs. While the vulnerability does not allow direct system compromise, the leaked IP can be a critical piece of intelligence for attackers. This is particularly concerning for organizations handling sensitive or regulated data, as it may violate privacy policies or regulatory requirements. The ease of exploitation without authentication or user interaction broadens the attack surface, especially for organizations with widely distributed remote workforces. The lack of known exploits in the wild reduces immediate risk but does not eliminate the potential for future exploitation. Overall, the vulnerability poses a significant privacy and security risk that could facilitate more severe attacks if combined with other vulnerabilities or social engineering tactics.

CWE-532Insertion of Sensitive Information into Log File (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A09:2025: Security Logging & Alerting Failures (opens in a new tab)
The product writes sensitive information to a log file.
Architecture and Design · Implementation
Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
Distribution
Remove debug log files before deploying the application into production.
Operation
Protect log files against unauthorized read/write.
OWASP Cheat Sheets
Application Logging Vocabulary (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V7.1.1 (opens in a new tab)
V7.1.2 (opens in a new tab)
V8.3.5 (opens in a new tab)
Attack patterns
Fuzzing for application mapping (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Feb 2026, 01:41 UTC

WeaknessesCWE-532

Technical details

References

Community reviews

Related threats