CVE-2024-54916

6.8 MEDIUM

📋 TL;DR

This vulnerability in Telegram Android allows a physically proximate attacker to bypass the app's passcode authentication and gain unauthorized access to the user's Telegram account and data. It affects users of Telegram Android version 11.7.0 who have passcode protection enabled. The attacker needs physical access to the unlocked device.

💻 Affected Systems

Products:
  • Telegram Android
Versions: 11.7.0
Operating Systems: Android
Default Config Vulnerable: ✅ No
Notes: Only affects users who have enabled passcode protection in Telegram settings. Default configuration without passcode is not vulnerable.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

An attacker with brief physical access to an unlocked device can bypass Telegram's passcode protection, access private messages, media, contacts, and potentially escalate to other device privileges.

🟠

Likely Case

Someone with temporary physical access to a victim's unlocked phone (e.g., colleague, family member) bypasses Telegram passcode to read private conversations and access sensitive data.

🟢

If Mitigated

With proper physical security controls and device locking, the risk is significantly reduced as the attacker needs both physical access and an unlocked device.

🌐 Internet-Facing: LOW - This is a local authentication bypass requiring physical proximity, not remotely exploitable.
🏢 Internal Only: MEDIUM - Within environments where devices are shared or physical security is lax, this poses moderate risk for unauthorized access to Telegram data.

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploit requires physical access to an unlocked Android device and manipulation of the SharedConfig class. Public proof-of-concept code is available on GitHub.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 11.7.1 and later

Vendor Advisory: https://telegram.org/blog/

Restart Required: No

Instructions:

1. Open Google Play Store 2. Search for Telegram 3. Update to version 11.7.1 or later 4. No restart required, but close and reopen Telegram app

🔧 Temporary Workarounds

Disable Telegram Passcode

android

Temporarily disable passcode protection in Telegram settings until patched

Open Telegram > Settings > Privacy and Security > Passcode Lock > Turn Off

Enable Device Screen Lock

android

Ensure device has strong screen lock (PIN/pattern/password) to prevent physical access

Settings > Security > Screen lock > Set strong PIN/password

🧯 If You Can't Patch

  • Disable Telegram passcode protection in app settings
  • Implement strict physical security controls for mobile devices

🔍 How to Verify

Check if Vulnerable:

Check Telegram version in app: Settings > (scroll down) > Telegram Version. If version is exactly 11.7.0 and passcode is enabled, you are vulnerable.

Check Version:

Open Telegram > Settings > (scroll down) > Telegram Version

Verify Fix Applied:

Update Telegram via Play Store, then verify version is 11.7.1 or higher in Settings > Telegram Version.

📡 Detection & Monitoring

Log Indicators:

  • Unusual access patterns to Telegram app without passcode entry
  • Multiple failed passcode attempts followed by successful access

Network Indicators:

  • None - this is a local authentication bypass

SIEM Query:

Not applicable for local device authentication bypass

🔗 References

📤 Share & Export