Home Cyber Security News Researcher Disclosed Telegram Vulnerability, Refused Bounty For Staying Quiet

Researcher Disclosed Telegram Vulnerability, Refused Bounty For Staying Quiet

by Abeerah Hashim
Telegram vulnerability

A researcher discovered a severe vulnerability in the self-destruct message feature of Telegram, leaving deleted messages in the cache. While Telegram patched the flaw, it didn’t appropriately reward the researcher for the bug report.

Telegram Vulnerability In ‘Self-Destruct’ Feature

Elaborating the details in a blog post, security researcher Dmitrii discovered how the vulnerability in self-destruct feature allowed Telegram users to retrieve deleted data.

While inspecting the Telegram for Android client soon after the release of self-destruct update, the researcher found that the self-destruct feature would only work visually at the app level. In reality, the deleted messages would remain in the device folder /Storage/Emulated/0/Telegram/Telegram Image.

The researcher tested the vulnerability by setting the self-destruct timer for 24 hours. As observed, the sent-then-deleted picture remained in the device cache at both the sender’s and receiver’s end.

Dmitrii evaluated this feature on several devices running on Android 7 to 10 and would get the same results. The following video demonstrates the exploit.

As mentioned, this is a different but similar bug to the previously reported (and fixed) CVE-2019-16248 reported in 2019.

Researcher Denied The Bounty

Upon discovering the vulnerability, the researcher reached out to Telegram officials. However, he explained that the service didn’t respond adequately.

Specifically, Dmitrii reported the bug to Telegram in March 2021, which the firm even acknowledged. However, it didn’t fix the bug for several months despite recurrent updates for the Telegram client.

The researcher kept reminding of the vulnerability to telegram officials. Eventually, the service fixed the bug in a subsequent beta version released in August 2021 that the researcher confirmed.

Nonetheless, problems began when Telegram tried to restrict the researcher from disclosing the vulnerability at the time of rewarding the bug bounty, even after the fix. In response, the researcher sent some questions to Telegram regarding the agreement he was supposed to sign, but Dmitrii never got a response.

The researcher even noticed a lesser bounty offered to him (Euro 1000) for the bug than what the service offered previously for a similar flaw (Euro 2500).

Eventually, the researcher went ahead for full public disclosure for this vulnerability CVE-2021-41861.

Users should ensure using at least the Telegram app version 7.8 that includes the fix for it. (Though, Telegram hasn’t mentioned any such bug fix in the changelog.) Also, the researcher advised users not to rely on the self-destruct feature for media privacy. Instead, users should opt for manual deletion of messages that they don’t want the recipient to retain.

Let us know your thoughts in the comments.

You may also like

Leave a Comment

Latest Hacking News

Privacy Preference Center


The __cfduid cookie is used to identify individual clients behind a shared IP address and apply security settings on a per-client basis.

cookie_notice_accepted and gdpr[allowed_cookies] are used to identify the choices made from the user regarding cookie consent.

For example, if a visitor is in a coffee shop where there may be several infected machines, but the specific visitor's machine is trusted (for example, because they completed a challenge within your Challenge Passage period), the cookie allows Cloudflare to identify that client and not challenge them again. It does not correspond to any user ID in your web application, and does not store any personally identifiable information.

__cfduid, cookie_notice_accepted, gdpr[allowed_cookies]


DoubleClick by Google refers to the DoubleClick Digital Marketing platform which is a separate division within Google. This is Google’s most advanced advertising tools set, which includes five interconnected platform components.

DoubleClick Campaign Manager: the ad-serving platform, called an Ad Server, that delivers ads to your customers and measures all online advertising, even across screens and channels.

DoubleClick Bid Manager – the programmatic bidding platform for bidding on high-quality ad inventory from more than 47 ad marketplaces including Google Display Network.

DoubleClick Ad Exchange: the world’s largest ad marketplace for purchasing display, video, mobile, Search and even Facebook inventory.

DoubleClick Search: is more powerful than AdWords and used for purchasing search ads across Google, Yahoo, and Bing.

DoubleClick Creative Solutions: for designing, delivering and measuring rich media (video) ads, interactive and expandable ads.



The _ga is asssociated with Google Universal Analytics - which is a significant update to Google's more commonly used analytics service. This cookie is used to distinguish unique users by assigning a randomly generated number as a client identifier. It is included in each page request in a site and used to calculate visitor, session and campaign data for the sites analytics reports. By default it is set to expire after 2 years, although this is customisable by website owners.

The _gat global object is used to create and retrieve tracker objects, from which all other methods are invoked. Therefore the methods in this list should be run only off a tracker object created using the _gat global variable. All other methods should be called using the _gaq global object for asynchronous tracking.

_gid works as a user navigates between web pages, they can use the gtag.js tagging library to record information about the page the user has seen (for example, the page's URL) in Google Analytics. The gtag.js tagging library uses HTTP Cookies to "remember" the user's previous interactions with the web pages.

_ga, _gat, _gid