Summary of "The REAL reason end-to-end encryption is "allowed" (UNPATCHED)"

Privacy Vulnerability in End-to-End Encrypted Messaging Apps

The video explores a significant and largely unknown privacy vulnerability affecting popular end-to-end encrypted messaging apps like WhatsApp and Signal. Despite their encryption protecting message content, these apps leak extensive metadata through a side channel involving delivery receipts. This enables adversaries to build detailed user profiles using only a phone number.


Key Technological Concepts and Features

End-to-End Encryption Basics

Messages are encrypted on the sender’s device and decrypted only on the recipient’s device, preventing servers or intermediaries from reading message contents. WhatsApp and Signal use this model, with Signal focusing heavily on privacy.

Multi-Device Support Approaches

Delivery Receipts

There are three types of delivery receipts: - Sent: Single check mark - Delivered: Double check mark (mandatory and cannot be disabled) - Read: Colored double check mark

The delivered receipt acts as a control flow mechanism for encryption.


Privacy Vulnerabilities and Side Channel Exploits


Impact and Real-World Testing


Response from WhatsApp and Signal


Suggested Fixes and Mitigations


Limitations and User Workarounds


Main Speakers / Sources


Summary: This video reveals a critical, unpatched privacy flaw in WhatsApp and Signal where mandatory delivery receipts and message reaction mechanics leak detailed metadata through timing side channels. This allows adversaries to profile users’ device usage, habits, and social connections using only their phone number—without malware or user interaction. Despite responsible disclosure, the vulnerability remains largely unaddressed, posing serious risks to user privacy and security.

Category ?

Technology

Share this summary

Video