Sunday, February 9, 2025
HomeComputer SecurityTelegram Leaks Public & Private IP Address While Making Calls

Telegram Leaks Public & Private IP Address While Making Calls

Published on

SIEM as a Service

Follow Us on Google News

Telegram Desktop version leaking users private and public IP address by default while initiating phone calls from tdesktop and telegram for windows.

Telegram offering encrypted chats and phone calls over the internet but its desktop and windows version leaking IP address.

Telegram Desktop application allows users only making phone calls by setting the P2P connection which is available to change from “Settings > Privacy and security > Calls > peer-to-peer”

But tdesktop and telegram for windows don’t have any option like this to set up the Peer-to-peer connection.

Dhiraj Mishra, Researcher who discovered this serious flaw in Telegram stated that “Even telegram for Android will also leak your IP address if you have not set “Settings > Privacy and security > Calls > peer-to-peer >nobody” (But Peer-to-Peer settings for call option already exists in a telegram for android”

Telegram Desktop – IP Leaking Scenario 

Below example that can demonstrate from Ubuntu Desktop Telegram console while users making phone calls from Telegram desktop.

1. Open tdesktop,
2. Initiate a call to anyone,
3. You will notice the end user IP address is leaking.

In this case, Telegram desktop clients forMac, Windows, and Linux also would reveal users’ IP addresses.

So making phone calls from the desktop version and windows would leaks both users IP addresses but the mobile version will not do the same since it was set as Peer-to-peer communication by default.

He Also Explains the other following scenario that indicates the part of leaking IP address of the following.

  •  Open tdesktop in Ubuntu and login with user A
  •  Open telegram in windows phone login with user B
  •  Let user B initiate the call to user A
  •  While user A access log will have the public/private IP address of user B.  

After reporting this flaw to Telegram, Dhiraj was awarded a €2,000 bounty for his finding and issued the patch in the 1.3.17 beta and 1.4.0 versions of Telegram for Desktop where you can set your “P2P to Nobody/My Contacts.

Later CVE-2018-17780 was assigned to this vulnerability and the user requested to update their desktop clients as soon as possible in order to patch this flaw to maintain the anonymity.

Related Read

Advanced Android Malware Steal Users Facebook, Twitter, Telegram, Skype Messenger Data

Hackers Now Switching to Telegram as a Secret Communication Medium for Underground Cybercrimes

New Android RAT Spotted in Wild Abusing Telegram Protocol for Command and Control

Balaji
Balaji
BALAJI is an Ex-Security Researcher (Threat Research Labs) at Comodo Cybersecurity. Editor-in-Chief & Co-Founder - Cyber Security News & GBHackers On Security.

Latest articles

UK Pressures Apple to Create Global Backdoor To Spy on Encrypted iCloud Access

United Kingdom has reportedly ordered Apple to create a backdoor allowing access to all...

Autonomous LLMs Reshaping Pen Testing: Real-World AD Breaches and the Future of Cybersecurity

Large Language Models (LLMs) are transforming penetration testing (pen testing), leveraging their advanced reasoning...

Securing GAI-Driven Semantic Communications: A Novel Defense Against Backdoor Attacks

Semantic communication systems, powered by Generative AI (GAI), are transforming the way information is...

Cybercriminals Target IIS Servers to Spread BadIIS Malware

A recent wave of cyberattacks has revealed the exploitation of Microsoft Internet Information Services...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

Is this Website Safe: How to Check Website Safety – 2025

is this website safe? In this digital world, Check a website is safe is...

Firefox 133.0 Released with Multiple Security Updates – What’s New!

Mozilla has officially launched Firefox 133.0, offering enhanced features, significant performance improvements, and critical...

Digital Wallets Bypassed To Allow Purchase With Stolen Cards

Digital wallets enable users to securely store their financial information on smart devices and...