Skip to content

Access control bypass in Apache ZooKeeper

Moderate severity GitHub Reviewed Published May 29, 2019 to the GitHub Advisory Database • Updated Feb 1, 2023

Package

maven org.apache.zookeeper:zookeeper (Maven)

Affected versions

>= 1.0.0, < 3.4.14
>= 3.5.0, < 3.5.5

Patched versions

3.4.14
3.5.5

Description

An issue is present in Apache ZooKeeper 1.0.0 to 3.4.13 and 3.5.0-alpha to 3.5.4-beta. ZooKeeper?s getACL() command doesn?t check any permission when retrieves the ACLs of the requested node and returns all information contained in the ACL Id field as plaintext string. DigestAuthenticationProvider overloads the Id field with the hash value that is used for user authentication. As a consequence, if Digest Authentication is in use, the unsalted hash value will be disclosed by getACL() request for unauthenticated or unprivileged users.

References

Published by the National Vulnerability Database May 23, 2019
Reviewed May 29, 2019
Published to the GitHub Advisory Database May 29, 2019
Last updated Feb 1, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.093%
(40th percentile)

Weaknesses

CVE ID

CVE-2019-0201

GHSA ID

GHSA-2hw2-62cp-p9p7

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.