Bug 1216161 (CVE-2023-44981) - VUL-0: CVE-2023-44981: zookeeper: authorization bypass in SASL
Summary: VUL-0: CVE-2023-44981: zookeeper: authorization bypass in SASL
Status: RESOLVED WONTFIX
Alias: CVE-2023-44981
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents (show other bugs)
Version: unspecified
Hardware: Other Other
: P3 - Medium : Normal
Target Milestone: ---
Assignee: Security Team bot
QA Contact: Security Team bot
URL: https://smash.suse.de/issue/381553/
Whiteboard: CVSSv3.1:SUSE:CVE-2023-44981:6.5:(AV:...
Keywords:
Depends on:
Blocks:
 
Reported: 2023-10-12 06:46 UTC by SMASH SMASH
Modified: 2023-11-06 09:20 UTC (History)
4 users (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description SMASH SMASH 2023-10-12 06:46:41 UTC 
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.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44981
https://bugzilla.redhat.com/show_bug.cgi?id=2243436