# |
CVE ID
|
CWE ID
|
# of Exploits
|
Vulnerability Type(s)
|
Publish Date
|
Update Date
|
Score
|
Gained Access Level
|
Access
|
Complexity
|
Authentication
|
Conf.
|
Integ.
|
Avail.
|
1 |
CVE-2022-43363 |
79 |
|
XSS |
2022-12-06 |
2022-12-08 |
0.0 |
None |
??? |
??? |
??? |
??? |
??? |
??? |
** DISPUTED ** Telegram Web 15.3.1 allows XSS via a certain payload derived from a Target Corporation website. NOTE: some third parties have been unable to discern any relationship between the Pastebin information and a possible XSS finding. |
2 |
CVE-2021-41861 |
|
|
|
2021-10-04 |
2021-10-08 |
2.1 |
None |
Local |
Low |
Not required |
None |
Partial |
None |
The Telegram application 7.5.0 through 7.8.0 for Android does not properly implement image self-destruction, a different vulnerability than CVE-2019-16248. After approximately two to four uses of the self-destruct feature, there is a misleading UI indication that an image was deleted (on both the sender and recipient sides). The images are still present in the /Storage/Emulated/0/Telegram/Telegram Image/ directory. |
3 |
CVE-2021-40532 |
|
|
|
2021-09-06 |
2021-09-10 |
7.5 |
None |
Remote |
Low |
Not required |
Partial |
Partial |
Partial |
Telegram Web K Alpha before 0.7.2 mishandles the characters in a document extension. |
4 |
CVE-2021-37596 |
79 |
|
XSS |
2021-07-30 |
2021-08-09 |
4.3 |
None |
Remote |
Medium |
Not required |
None |
Partial |
None |
Telegram Web K Alpha 0.6.1 allows XSS via a document name. |
5 |
CVE-2021-36769 |
326 |
|
|
2021-07-17 |
2021-07-29 |
5.0 |
None |
Remote |
Low |
Not required |
None |
Partial |
None |
A reordering issue exists in Telegram before 7.8.1 for Android, Telegram before 7.8.3 for iOS, and Telegram Desktop before 2.8.8. An attacker can cause the server to receive messages in a different order than they were sent a client. |
6 |
CVE-2021-31323 |
787 |
|
Overflow |
2021-05-18 |
2021-05-25 |
4.3 |
None |
Remote |
Medium |
Not required |
Partial |
None |
None |
Telegram Android <7.1.0 (2090), Telegram iOS <7.1, and Telegram macOS <7.1 are affected by a Heap Buffer Overflow in the LottieParserImpl::parseDashProperty function of their custom fork of the rlottie library. A remote attacker might be able to access heap memory out-of-bounds on a victim device via a malicious animated sticker. |
7 |
CVE-2021-31322 |
787 |
|
Overflow |
2021-05-18 |
2021-05-25 |
4.3 |
None |
Remote |
Medium |
Not required |
Partial |
None |
None |
Telegram Android <7.1.0 (2090), Telegram iOS <7.1, and Telegram macOS <7.1 are affected by a Heap Buffer Overflow in the LOTGradient::populate function of their custom fork of the rlottie library. A remote attacker might be able to access heap memory out-of-bounds on a victim device via a malicious animated sticker. |
8 |
CVE-2021-31321 |
787 |
|
Overflow |
2021-05-18 |
2021-05-25 |
5.8 |
None |
Remote |
Medium |
Not required |
None |
Partial |
Partial |
Telegram Android <7.1.0 (2090), Telegram iOS <7.1, and Telegram macOS <7.1 are affected by a Stack Based Overflow in the gray_split_cubic function of their custom fork of the rlottie library. A remote attacker might be able to overwrite Telegram's stack memory out-of-bounds on a victim device via a malicious animated sticker. |
9 |
CVE-2021-31320 |
787 |
|
Overflow |
2021-05-18 |
2021-05-25 |
5.8 |
None |
Remote |
Medium |
Not required |
None |
Partial |
Partial |
Telegram Android <7.1.0 (2090), Telegram iOS <7.1, and Telegram macOS <7.1 are affected by a Heap Buffer Overflow in the VGradientCache::generateGradientColorTable function of their custom fork of the rlottie library. A remote attacker might be able to overwrite heap memory out-of-bounds on a victim device via a malicious animated sticker. |
10 |
CVE-2021-31319 |
190 |
|
Overflow |
2021-05-18 |
2021-05-25 |
4.3 |
None |
Remote |
Medium |
Not required |
Partial |
None |
None |
Telegram Android <7.1.0 (2090), Telegram iOS <7.1, and Telegram macOS <7.1 are affected by an Integer Overflow in the LOTGradient::populate function of their custom fork of the rlottie library. A remote attacker might be able to access heap memory out-of-bounds on a victim device via a malicious animated sticker. |
11 |
CVE-2021-31318 |
843 |
|
|
2021-05-18 |
2021-05-25 |
4.3 |
None |
Remote |
Medium |
Not required |
Partial |
None |
None |
Telegram Android <7.1.0 (2090), Telegram iOS <7.1, and Telegram macOS <7.1 are affected by a Type Confusion in the LOTCompLayerItem::LOTCompLayerItem function of their custom fork of the rlottie library. A remote attacker might be able to access heap memory out-of-bounds on a victim device via a malicious animated sticker. |
12 |
CVE-2021-31317 |
843 |
|
|
2021-05-18 |
2021-05-25 |
4.3 |
None |
Remote |
Medium |
Not required |
Partial |
None |
None |
Telegram Android <7.1.0 (2090), Telegram iOS <7.1, and Telegram macOS <7.1 are affected by a Type Confusion in the VDasher constructor of their custom fork of the rlottie library. A remote attacker might be able to access Telegram's heap memory out-of-bounds on a victim device via a malicious animated sticker. |
13 |
CVE-2021-31315 |
787 |
|
Overflow |
2021-05-18 |
2021-05-25 |
4.3 |
None |
Remote |
Medium |
Not required |
Partial |
None |
None |
Telegram Android <7.1.0 (2090), Telegram iOS <7.1, and Telegram macOS <7.1 are affected by a Stack Based Overflow in the blit function of their custom fork of the rlottie library. A remote attacker might be able to access Telegram's stack memory out-of-bounds on a victim device via a malicious animated sticker. |
14 |
CVE-2021-30496 |
|
|
DoS |
2021-04-20 |
2023-02-02 |
3.5 |
None |
Remote |
Medium |
??? |
None |
None |
Partial |
** DISPUTED ** The Telegram app 7.6.2 for iOS allows remote authenticated users to cause a denial of service (application crash) if the victim pastes an attacker-supplied message (e.g., in the Persian language) into a channel or group. The crash occurs in MtProtoKitFramework. NOTE: the vendor's perspective is that "this behavior can't be considered a vulnerability." |
15 |
CVE-2021-27351 |
613 |
|
|
2021-02-19 |
2022-05-23 |
5.0 |
None |
Remote |
Low |
Not required |
None |
Partial |
None |
The Terminate Session feature in the Telegram application through 7.2.1 for Android, and through 2.4.7 for Windows and UNIX, fails to invalidate a recently active session. |
16 |
CVE-2020-25824 |
862 |
|
|
2020-10-14 |
2021-07-21 |
2.1 |
None |
Local |
Low |
Not required |
Partial |
None |
None |
Telegram Desktop through 2.4.3 does not require passcode entry upon pushing the Export key within the Export Telegram Data wizard. The threat model is a victim who has voluntarily opened Export Wizard but is then distracted. An attacker then approaches the unattended desktop and pushes the Export key. This attacker may consequently gain access to all chat conversation and media files. |
17 |
CVE-2020-17448 |
863 |
|
Bypass |
2020-08-11 |
2021-01-28 |
6.8 |
None |
Remote |
Medium |
Not required |
Partial |
Partial |
Partial |
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. |
18 |
CVE-2020-12474 |
20 |
|
|
2020-05-01 |
2021-07-21 |
4.3 |
None |
Remote |
Medium |
Not required |
Partial |
None |
None |
Telegram Desktop through 2.0.1, Telegram through 6.0.1 for Android, and Telegram through 6.0.1 for iOS allow an IDN Homograph attack via Punycode in a public URL or a group chat invitation URL. |
19 |
CVE-2020-10570 |
287 |
|
Bypass |
2020-03-24 |
2021-07-21 |
3.6 |
None |
Local |
Low |
Not required |
Partial |
Partial |
None |
The Telegram application through 5.12 for Android, when Show Popup is enabled, might allow physically proximate attackers to bypass intended restrictions on message reading and message replying. This might be interpreted as a bypass of the passcode feature. |
20 |
CVE-2019-16248 |
|
|
|
2019-09-11 |
2021-10-18 |
2.1 |
None |
Local |
Low |
Not required |
Partial |
None |
None |
The "delete for" feature in Telegram before 5.11 on Android does not delete shared media files from the Telegram Images directory. In other words, there is a potentially misleading UI indication that a sender can remove a recipient's copy of a previously sent image (analogous to supported functionality in which a sender can remove a recipient's copy of a previously sent message). |
21 |
CVE-2019-15514 |
200 |
|
+Info |
2019-08-23 |
2021-07-21 |
5.0 |
None |
Remote |
Low |
Not required |
Partial |
None |
None |
The Privacy > Phone Number feature in the Telegram app 5.10 for Android and iOS provides an incorrect indication that the access level is Nobody, because attackers can find these numbers via the Group Info feature, e.g., by adding a significant fraction of a region's assigned phone numbers. |
22 |
CVE-2019-10044 |
20 |
|
|
2019-03-25 |
2021-07-21 |
6.8 |
None |
Remote |
Medium |
Not required |
Partial |
Partial |
Partial |
Telegram Desktop before 1.5.12 on Windows, and the Telegram applications for Android, iOS, and Linux, is vulnerable to an IDN homograph attack when displaying messages containing URLs. This occurs because the application produces a clickable link even if (for example) Latin and Cyrillic characters exist in the same domain name, and the available font has an identical representation of characters from different alphabets. |
23 |
CVE-2018-20436 |
918 |
|
|
2018-12-24 |
2019-02-14 |
6.8 |
None |
Remote |
Medium |
Not required |
Partial |
Partial |
Partial |
** DISPUTED ** The "secret chat" feature in Telegram 4.9.1 for Android has a "side channel" in which Telegram servers send GET requests for URLs typed while composing a chat message, before that chat message is sent. There are also GET requests to other URLs on the same web server. This also affects one or more other Telegram products, such as Telegram Web-version 0.7.0. In addition, it can be interpreted as an SSRF issue. NOTE: a third party has reported that potentially unwanted behavior is caused by misconfiguration of the "Secret chats > Preview links" setting. |
24 |
CVE-2018-17780 |
200 |
|
+Info |
2018-09-29 |
2018-12-06 |
4.0 |
None |
Remote |
Low |
??? |
Partial |
None |
None |
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. |
25 |
CVE-2018-17613 |
522 |
|
|
2018-09-28 |
2019-10-03 |
5.0 |
None |
Remote |
Low |
Not required |
Partial |
None |
None |
Telegram Desktop (aka tdesktop) 1.3.16 alpha, when "Use proxy" is enabled, sends credentials and application data in cleartext over the SOCKS5 protocol. |
26 |
CVE-2018-17231 |
617 |
|
DoS |
2018-09-19 |
2019-10-03 |
5.0 |
None |
Remote |
Low |
Not required |
None |
None |
Partial |
** DISPUTED ** Telegram Desktop (aka tdesktop) 1.3.14 might allow attackers to cause a denial of service (assertion failure and application exit) via an "Edit color palette" search that triggers an "index out of range" condition. NOTE: this issue is disputed by multiple third parties because the described attack scenario does not cross a privilege boundary. |
27 |
CVE-2018-15543 |
287 |
|
Bypass |
2018-10-09 |
2018-11-24 |
4.6 |
None |
Local |
Low |
Not required |
Partial |
Partial |
Partial |
** DISPUTED ** An issue was discovered in the org.telegram.messenger application 4.8.11 for Android. The FingerprintManager class for Biometric validation allows authentication bypass through the callback method from onAuthenticationFailed to onAuthenticationSucceeded with null, because the fingerprint API in conjunction with the Android keyGenerator class is not implemented. In other words, an attacker could authenticate with an arbitrary fingerprint. NOTE: the vendor indicates that this is not an attack of interest within the context of their threat model, which excludes Android devices on which rooting has occurred. |
28 |
CVE-2018-15542 |
287 |
|
Bypass |
2018-10-09 |
2018-11-26 |
4.4 |
None |
Local |
Medium |
Not required |
Partial |
Partial |
Partial |
** DISPUTED ** An issue was discovered in the org.telegram.messenger application 4.8.11 for Android. The Passcode feature allows authentication bypass via runtime manipulation that forces a certain method's return value to true. In other words, an attacker could authenticate with an arbitrary passcode. NOTE: the vendor indicates that this is not an attack of interest within the context of their threat model, which excludes Android devices on which rooting has occurred. |
29 |
CVE-2018-3986 |
200 |
|
+Info |
2019-01-03 |
2023-02-04 |
2.1 |
None |
Local |
Low |
Not required |
Partial |
None |
None |
An exploitable information disclosure vulnerability exists in the "Secret Chats" functionality of the Telegram Android messaging application version 4.9.0. The "Secret Chats" functionality allows a user to delete all traces of a chat, either by using a time trigger or by direct request. There is a bug in this functionality that leaves behind photos taken and shared on the secret chats, even after the chats are deleted. These photos will be stored in the device and accessible to all applications installed on the Android device. |
30 |
CVE-2017-17715 |
22 |
|
Dir. Trav. |
2017-12-16 |
2018-01-04 |
6.8 |
None |
Remote |
Medium |
Not required |
Partial |
Partial |
Partial |
The saveFile method in MediaController.java in the Telegram Messenger application before 2017-12-08 for Android allows directory traversal via a pathname obtained in a file-transfer request from a remote peer, as demonstrated by writing to tgnet.dat or tgnet.dat.bak. |
31 |
CVE-2014-8688 |
200 |
|
+Info |
2017-03-14 |
2020-05-13 |
5.0 |
None |
Remote |
Low |
Not required |
Partial |
None |
None |
An issue was discovered in Telegram Messenger 2.6 for iOS and 1.8.2 for Android. Secret chat messages are available in cleartext in process memory and a .db file. |