Telegram Desktop vulnerabilities

Telegram Desktop before 7.2.9 contains an IPC record-separator injection vulnerability in Core::Sandbox that allows remote attackers to inject OPEN: records via crafted tg:// links containing unescaped semicolons. Attackers can reach the interpret: scheme handler to upload local files, including tdata session keys, to an attacker channel, enabling account takeover.

Telegram Desktop 2.9.2 contains a denial of service vulnerability that allows attackers to crash the application by sending an oversized message payload. Attackers can generate a 9 million byte buffer and paste it into the messaging interface to trigger an application crash.

Telegram Desktop before 6.9.4 allows XSS in the HTML exporter. This occurs in button.text.toUtf8 in export_output_html.cpp. Exploitation cannot occur unless HTML export was used by a victim, but the exploit payload can be exported if a message were forwarded into a group by a member.

In Telegram Desktop up to 6.7.5, the RequestButton function in url_auth_box.cpp of the Bot API component, when manipulating the login_url argument, leads to a null pointer dereference. The attack can be initiated remotely and the exploit has been publicly disclosed. There is ongoing doubt about the real existence of this vulnerability, and the vendor states it only causes a one-time crash without security consequences.