CVE-2024-52940
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAnyDesk 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAnyDesk through version 8.1.0 on Windows contains an information disclosure vulnerability when the 'Allow Direct Connections' feature is enabled. The application inadvertently exposes the user's public IP address in network traffic, allowing an attacker who knows the victim's AnyDesk ID to discover their public IP address through network traffic analysis.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm AnyDesk installationCheck for AnyDesk.exe in the default installation directory (C:\Program Files\AnyDesk\AnyDesk.exe) or search for AnyDesk in Programs and Features.Affected if AnyDesk is installed on the system.
-
Identify installed AnyDesk versionRight-click AnyDesk.exe, select Properties, and view the File Version on the Details tab. Alternatively, open AnyDesk, go to About, or run 'AnyDesk.exe --version' from command line if supported.Affected if The installed version is 8.1.0 or any earlier version through 8.1.0.
-
Verify Allow Direct Connections setting is enabledOpen AnyDesk, navigate to Settings (gear icon) > Connection > Network. Check if the 'Allow Direct Connections' checkbox is ticked. On some versions, this may be in Settings > Privacy or Settings > Connection settings.Affected if The 'Allow Direct Connections' option is enabled (checked/ON).
-
Verify direct connections are possibleAttempt to establish a direct peer-to-peer connection to this AnyDesk client using its AnyDesk ID from another AnyDesk instance. Observe if the connection succeeds without routing through relays.Affected if Direct connections can be established, indicating the feature is functional and the public IP may be exposed in traffic.
The system is affected if AnyDesk version 8.1.0 or earlier is installed AND the 'Allow Direct Connections' feature is enabled, allowing the public IP address to be disclosed to attackers who know the AnyDesk ID.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataDisable the 'Allow Direct Connections' setting in AnyDesk preferences to prevent exposure of the public IP address in peer-to-peer connections. This forces connections through AnyDesk's relay servers, masking the client's public IP.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-52940 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-52940 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data