Fwd: [liberationtech] MiTM attack on XMPP/Jabber traffic at Hetzner and Linode (DE) suggests datacenter complicity
---------- Forwarded message ---------- Date: Sun, 22 Oct 2023 10:34:44 +1300 Subject: [liberationtech] MiTM attack on XMPP/Jabber traffic at Hetzner and Linode (DE) suggests datacenter complicity Interesting and especially stealth MiTM at Hetzner (DE) and Linode, targeting Russia's largest XMPP/Jabber (civilian) chat service. The authors of the article make a reasonably compelling case that "this is lawful interception Hetzner and Linode were forced to setup." It would seem a rogue Letsencrypt chain was deployed at the last hop facing the dedicated server hosting the XMPP infrastructure, for which the LE ACME challenge would have passed without issue. This was used to hijack encrypted STARTTLS connections. The 'real' LE chain was then effectively ignored, as all traffic to/fro the running server was decrypted through the transparent MiTM proxy. In the case of Linode, it seems the target's VPS was migrated into a hostile VLAN with a monitor at the first hop. Their methodology is sound, strong forensics. - https://notes.valdikss.org.ru/jabber.ru-mitm/ A good overview of mitigation strategies here, from DNSSEC to CAA: - https://www.devever.net/~hl/xmpp-incident I feel it is worth noting that many civilian - and potentially dissident - Russian voices would have been using this service to protect themselves from Kremlin eavesdropping; a safe space. & yet here they are subject to a supposed lawful intervention by what we can assume are non-RU state actor(s). This event may undermine faith in secure community-run infrastructure, pushing RU communities to less secure group chat alternatives, including those the Kremlin has compromised. An ethically troubled case. -- Julian Oliver Consulting: https://nikau.io Projects: https://julianoliver.com PGP: https://julianoliver.com/key.asc
After checking https://crt.sh/ certificate transparency database, rogue certificates have been discovered which were not issued by any of jabber.ru servers.
The maliciously-issued certificates are slightly different from the regular ones for these domains: either the wildcard Subject Alternative Name is missing or a single certificate is issued for both jabber.ru, xmpp.ru. Moreover, MiTM configuration on xmpp.ru domain (which points to Linode servers) was slightly misconfigured: it serves only xmpp.ru certificate, yet the original server is configured to serve both jabber.ru and xmpp.ru certificates depending on requested XMPP domain.
List of rogue certificates:
Serial Used in MiTM 03:f3:68:ee:36:30:80:6a:07:81:17:81:04:0c:e3:d9:10:b1 + 04:9c:2d:af:cc:61:88:d6:67:9f:8b:97:99:ce:ad:c9:b7:e0 + 03:43:75:1f:3d:80:20:7d:11:f5:61:98:5b:87:a7:37:81:c6 ? 04:4c:1c:8a:f4:37:a0:5a:dd:83:9c:54:74:89:bd:b9:97:90 + 04:d1:d2:5d:09:95:48:9b:d6:14:cc:81:91:df:ac:7f:ec:c6 ? 04:b7:85:83:9a:fd:df:81:26:48:5b:34:28:08:53:d9:e6:79 +
18 July 2023 issuing time is about the same when Hetzner server has lost network link for several seconds.
We have a confirmation from the external network scanner that Linode servers started to serve 04:b7:85… certificate on port 5222 since at least 21 July 2023. Unfortunately, this scanner doesn’t process Hetzner ranges.
participants (1)
-
Undescribed Horrific Abuse, One Victim & Survivor of Many