EILMELDUNGEN LIVE
🐧 Linux TippsDebian AI Vote has Divided the Community(30.08.2026 um 07:23 Uhr)
🔧 AI Nachrichten Codex CLI: Use OpenAI’s AI Coding Agent in the Linux Terminal(27.08.2026 um 12:31 Uhr)
🪟 Windows TippsChina Switching from Windows to Linux(24.08.2026 um 22:16 Uhr)
🐧 Linux TippsDistribution Release: NawaOS 2.0(27.08.2026 um 10:53 Uhr)
🐧 Linux TippsDistribution Release: Butterbian 0.4.0(27.08.2026 um 13:10 Uhr)
🐧 Linux TippsDistribution Release: Liya Linux 2026.08.29(29.08.2026 um 16:48 Uhr)
🔧 AI Nachrichten DistroWatch Weekly, Issue 1188(31.08.2026 um 03:21 Uhr)
🔧 Programmierung[Unstable Update] September 2026(01.09.2026 um 15:32 Uhr)
🐧 Linux TippsDebian AI Vote has Divided the Community(30.08.2026 um 07:23 Uhr)
🔧 AI Nachrichten Codex CLI: Use OpenAI’s AI Coding Agent in the Linux Terminal(27.08.2026 um 12:31 Uhr)
🪟 Windows TippsChina Switching from Windows to Linux(24.08.2026 um 22:16 Uhr)
🐧 Linux TippsDistribution Release: NawaOS 2.0(27.08.2026 um 10:53 Uhr)
🐧 Linux TippsDistribution Release: Butterbian 0.4.0(27.08.2026 um 13:10 Uhr)
🐧 Linux TippsDistribution Release: Liya Linux 2026.08.29(29.08.2026 um 16:48 Uhr)
🔧 AI Nachrichten DistroWatch Weekly, Issue 1188(31.08.2026 um 03:21 Uhr)
🔧 Programmierung[Unstable Update] September 2026(01.09.2026 um 15:32 Uhr)

11 🕛 kürzlich 2 Min Lesezeit CVE-RADAR
0

Black Hat Asia 2026 | Payload Compromised: Full Key Recovery in Rocket.Chat E2EE

↗ Quelle (YouTube · Black Hat)
🗣️ Stimme:
📺
YouTube · Black Hat
36 YouTube-Aufrufe
Rocket.Chat is used in more than 150 countries, where many organizations rely on its end-to-end encryption (E2EE) for security-critical communication. This talk presents the first comprehensive analysis of Rocket.Chat's E2EE as deployed in real systems. By combining automated symbolic analysis with in-depth manual inspection of the implementation, we identify practical attacks that break both confidentiality and integrity.

Our most severe finding is a practical key-recovery attack.
An attacker with access to encrypted user backups can recover private keys and all derived group keys in twelve days under realistic assumptions. We validate this attack with practical proof-of-concept exploits. This results from weak offline-attack resistance combined with a biased, low-entropy password generator used to encrypt key backups. At the time of reporting, any server operating under a malicious-server threat model could execute the attack.

We also uncover structural failures in the platform's key-rotation workflow. Although E2EE passwords and a master key were rotated, the group keys protecting message content were never replaced. Clients continued to accept and redistribute compromised group keys, which were then reused to encrypt new messages and decrypt past ones. A single key recovery therefore enabled expanding and persistent compromise across group communication.

Manual analysis further revealed integrity failures, including ciphertext forgery made possible by unauthenticated AES-CBC encryption.

Beyond the technical flaws, we also reconstruct how this fragile design emerged by examining public development discussions and historical commits. This OSINT analysis explains why several fundamental E2EE principles were never integrated and how long-term structural risks accumulated.

The most severe vulnerabilities, including key recovery and broken key rotation, were fixed within six months of disclosure, and remaining integrity issues were patched after extended coordination. Attendees will learn how to analyze real-world E2EE systems, detect specification-implementation gaps, and replace password-based architectures with modern best practices.

Hayato Kimura | Researcher, National Institute of Information and Communications Technology & The University of Osaka
Ryoma Ito | Senior Researcher, National Institute of Information and Communications Technology
Kazuhiko Minematsu | Research Fellow, NEC Corporation
Takanori Isobe | Professor, The University of Osaka

https://blackhat.com/asia-26/briefings/schedule/?#payload-compromised-full-key-recovery-in-rocketchat-e2ee-50105
Vollständiger Original-Bericht
Ausführliche Details, Code-Beispiele & Hersteller-Stellungnahme auf youtube.com.
↗ Original-Artikel auf youtube.com lesen
Wie bewertest du diesen Beitrag?
1 Klick Feedback
76 Fachleser & IT-Security Experten haben diesen Report heute geteilt
Teilen mit Netzwerk & Team:

Community-Analysen & Experten-Meinungen 0

Verfasse deine eigene Analyse, teile Workarounds oder diskutiere diesen Vorfall im Blog.
Noch keine Community-Analyse verfasst. Markiere einen Textabschnitt oder klicke oben auf Eigene Analyse verfassen“!
Community Pulse: Relevanz-Einschätzung
1 Klick Experten-Votum
🔴 Akute Relevanz 52%
🟡 In Evaluierung 31%
🟢 Keine Auswirkung 12%
Spannende Innovation 5%
Verwandte Story-Cluster & Quellen (Vektor-KI)
Port 8095 Engine
1 Quelle
Debian AI Vote has Divided the Community
1 Quelle
AI Crawlers Are Bleeding The Linux Kernel Repo's Compute Power
1 Quelle
Vanilla OS 3 Comes in Hot, Packing ARM64 Support After a Long Wait