# CVE-2024-52940: Information disclosure in n/a

> An attacker knowing the victim's ID can expose their public IP address if direct connections are enabled, requiring configuration changes to mitigate.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Nov 2024
- **Updated:** 23 Nov 2024
- **Also known as:** GHSA-r2ph-vgmf-8gqh

## What is CVE-2024-52940?

CVE-2024-52940 is a high-severity vulnerability in n/a, published on 18 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2024-52940?


## How do I fix CVE-2024-52940?

No fix has been published for CVE-2024-52940 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-52940 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-52940 exists.

Public exploit code:

- AnySniff is a tool for monitoring TCP connections of processes like AnyDesk on Windows. It uses the CVE-2024-52940 vulnerability to track open connections and log IPs, ports, and other details. (github_poc): https://github.com/MKultra6969/AnySniff

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-52940 and fix it if it is affected.

What it is: CVE-2024-52940 is a high-severity vulnerability in n/a, published on 18 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-52940 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-52940/ (Markdown: https://insights.sbomify.com/CVE-2024-52940/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-52940
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-52940
- OSV: https://osv.dev/vulnerability/CVE-2024-52940

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-52940/
Summaries are generated and may contain mistakes; the official description above is the record.