# CVE-2018-17780: Information disclosure in n/a

> Telegram Desktop leaks user IP addresses during calls due to unsafe default P2P connection settings, exposing private network information.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-17780, GHSA-r3p8-5cf3-rwmg, UBUNTU-CVE-2018-17780

## What is CVE-2018-17780?

CVE-2018-17780 is a medium-severity vulnerability in n/a, published on 29 Sep 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Telegram Desktop (aka tdesktop) 1.3.14, and Telegram 3.3.0.0 WP8.1 on Windows, leaks end-user public and private IP addresses during a call because of an unsafe default behavior in which P2P connections are accepted from clients outside of the My Contacts list.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2018-17780?

It affects 2 products.


Products: Telegram Telegram Desktop, Telegram Telegram Messenger.

## How do I fix CVE-2018-17780?

Apply the vendor's patch.

## Is CVE-2018-17780 being exploited?

There is no known exploitation of CVE-2018-17780 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2018-17613](https://insights.sbomify.com/CVE-2018-17613/): Information disclosure in n/a (critical 9.8)
- [CVE-2020-17448](https://insights.sbomify.com/CVE-2020-17448/): Security feature bypass in n/a (high 7.8)
- [CVE-2018-17231](https://insights.sbomify.com/CVE-2018-17231/): Denial of service in n/a (high 7.5)
- [CVE-2021-47793](https://insights.sbomify.com/CVE-2021-47793/): Telegram Desktop 2.9.2 - Denial of Service (PoC) (medium 4.6)
- [CVE-2020-25824](https://insights.sbomify.com/CVE-2020-25824/): Missing authorization in n/a (low 2.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-17780 and fix it if it is affected.

What it is: CVE-2018-17780 is a medium-severity vulnerability in n/a, published on 29 Sep 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-17780 in the wild and no public exploit code.

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-2018-17780/ (Markdown: https://insights.sbomify.com/CVE-2018-17780/index.md)
```

## Sources

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

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