CVE-2018-17780

Exp

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.

Published: 2018-09-29 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2018-17780 is rated High Exploit Risk (68.8/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 1.78%). 1 public exploit reference(s) are indexed (Exploit-DB). EPSS rose +1.41% over the last day, indicating growing attacker interest. Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2018-17780

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2018-17780

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.37% 1.78% +1.41%
2 2025-11-21 0.49% 0.37% -0.12%
3 2025-11-18 — 0.49% —

Full EPSS history (11 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2018-17780

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.0 MEDIUM
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 3.6 [email protected]
4.0 2.0 MEDIUM
AV:N/AC:L/Au:S/C:P/I:N/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:S)
A single authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
 8.0 2.9 [email protected]

Weakness enumeration for CVE-2018-17780

OS Trackers for CVE-2018-17780

vendor priority summary link
debian not yet assigned CVE-2018-17780 not yet assigned priority: Debian including 1 source packages (telegram-desktop), 4 status rows across 4 suites (bookworm, bullseye, forky, sid): resolved 4. https://security-tracker.debian.org/tracker/CVE-2018-17780
ubuntu low CVE-2018-17780 low priority: Ubuntu including 1 source packages (telegram-desktop), 19 status rows across 19 suites (bionic, cosmic, disco, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 8, ignored 7, needed 3, released 1. https://ubuntu.com/security/CVE-2018-17780

Affected software / configurations for CVE-2018-17780

Vendor Product Version Raw CPE
telegram telegram_desktop 1.3.14 cpe:2.3:a:telegram:telegram_desktop:1.3.14:*:*:*:*:*:*:*
telegram telegram_messenger 3.3.0.0 cpe:2.3:a:telegram:telegram_messenger:3.3.0.0:*:*:*:*:windows:*:*

References for CVE-2018-17780

cvelogic Threat Intelligence