Critical · published October 11, 2023
🚨 A sneaky omission could let intruders stroll right into your ZooKeeper cluster. If SASL authentication is on but the instance part is missing, the door swings wide open! 🔥 It's like having a VIP club where the bouncer only checks for names on the list but forgets to verify if the guest has a proper ID — anyone can waltz in and start changing the playlist! An attacker could join your cluster and wreak havoc, propagating false changes with full read-write access to your data tree. This could lead to corruption of vital data and a total loss of integrity for your system – absolutely devastating!
It's like having a VIP club where the bouncer only checks for names on the list but forgets to verify if the guest has a proper ID — anyone can waltz in and start changing the playlist! The vulnerability occurs when the instance part of the SASL authentication ID is omitted, causing the authorization check to be bypassed. This allows unverified entities to join the ZooKeeper cluster without proper permission.
An attacker could join your cluster and wreak havoc, propagating false changes with full read-write access to your data tree. This could lead to corruption of vital data and a total loss of integrity for your system – absolutely devastating! Upgrade your ZooKeeper installation to version 3.9.1, 3.8.3, or 3.7.2 immediately to close this loophole. Alternatively, tighten security by ensuring your ensemble election and quorum communication are protected by a firewall. You've got this! Follow these steps, and you'll have your ZooKeeper cluster secured in no time! 🛡️