CVE-2020-17448 json
Telegram Desktop through 2.1.13 allows a spoofed file type to bypass the Dangerous File Type Execution protection mechanism, as demonstrate…
published 6y ago modified 4mo ago also EUVD-2020-9400
- cvss
- 7.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.3%
- EPSS 2.3% chance of exploitation in 30 days, percentile 83%
- public exploits
- 0
- none known
Summary
Telegram Desktop through 2.1.13 allows a spoofed file type to bypass the Dangerous File Type Execution protection mechanism, as demonstrated by use of the chat window with a filename that lacks an extension.
Patch / fix
- telegram-desktop Debian 14, Debian 12 2.2.0+ds-1
debian advisories DEBIAN-CVE-2020-17448
Is CVE-2020-17448 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
2.28% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
References
-
security.gentoo.org
/glsa/202101-34
vendor-advisory, third-party-advisory
-
telegram.org
vendor-advisory
-
github.com
/VijayT007/Vulnerability-Database/blob/master/Telegram-CVE-2020-17448
third-party-advisory
-
github.com
/telegramdesktop/tdesktop/releases/tag/v2.2.0
release-notes, third-party-advisory
Sources
- CVE List CVE-2020-17448
- NVD CVE-2020-17448
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.