Authorization Bypass Through User-Controlled Key vulnerability in Apache ZooKeeper

Authorization Bypass Through User-Controlled Key vulnerability in Apache ZooKeeper. If SASL Quorum Peer authentication is enabled in ZooKeeper (quorum.auth.enableSasl=true), the authorization is done by verifying that the instance part in SASL authentication ID is listed in zoo.cfg server list. The instance part in SASL auth ID is optional and if it's missing, like 'eve@EXAMPLE.COM', the authorization check will be skipped. As a result an arbitrary endpoint could join the cluster and begin propagating counterfeit changes to the leader, essentially giving it complete read-write access to the data tree. Quorum Peer authentication is not enabled by default. Users are recommended to upgrade to version 3.9.1, 3.8.3, 3.7.2, which fixes the issue. Alternately ensure the ensemble election/quorum communication is protected by a firewall as this will mitigate the issue. See the documentation for more details on correct cluster administration.

CVSS 3.1

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Severity from

GitHub (reviewed advisory)

Weakness

CWE-639

Also known as

BIT-zookeeper-2023-44981, CVE-2023-44981

• nvd.nist.gov/vuln/detail/CVE-2023-44981
• github.com/apache/zookeeper
• lists.apache.org/thread/wf0yrk84dg1942z1o74kd8nycg6pgm5b
• lists.debian.org/debian-lts-announce/2023/10/msg00029.html
• security.netapp.com/advisory/ntap-20240621-0007
• www.debian.org/security/2023/dsa-5544
• www.openwall.com/lists/oss-security/2023/10/11/4