3 ms·
This article is atrocious. It has a clear agenda motivating its publication that is simply at odds with facts. 1. This is not a vulnerability with Telegram. Th
by dsacco 9y ago
This article is atrocious. It has a clear agenda motivating its publication that is simply at odds with facts.
1. This is not a vulnerability with Telegram. The headline is deliberate clickbait, and the article’s Telegram-centric presentation doesn’t redeem it.
2. This is not a remote code exeution vulnerability, or even a “0-day” (for whatever meaning that term still has...). This vulnerability is a malicious file upload combined with a clever phishing vector.
The reporting is exceptionally bad - so much so that it is difficult for me to attribute it to simple ignorance. It is very clearly trying to hit several checkboxes for what is otherwise a non-story:
* Telegram
* Cybercrime
* Cryptocurrencies/Mining
The entire narrative is carefully constructed with keywords that have no hard relation to the vulnerability whatsoever - it feels like I’m reading a bug bounty report where someone extrapolates a minor endpoint security or phishing vulnerability to whatever they think will get the most attention to the report.
Reporting like this almost makes me wish for Gell-Mann Amnesia in my own field.