org.apache.zookeeper:zookeeper 3.5.0-alpha vulnerabilities

Direct Vulnerabilities

Known vulnerabilities in the org.apache.zookeeper:zookeeper package. This does not include vulnerabilities belonging to this package’s dependencies.

How to fix?

Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.

Fix for free

Vulnerability	Vulnerable Version
H Authorization Bypass Through User-Controlled Key org.apache.zookeeper:zookeeper is a centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services. Affected versions of this package are vulnerable to Authorization Bypass Through User-Controlled Key when the SASL Quorum Peer authentication is enabled (`quorum.auth.enableSasl=true), an attacker can bypass the authorization check by omitting the instance part in the SASL authentication ID. This allows an arbitrary endpoint to join the cluster and propagate counterfeit changes to the leader, effectively granting it full read-write access to the data tree. Note: This is only exploitable if `quorum.auth.enableSasl=true` is set in the configuration. Quorum Peer authentication is not enabled by default. How to fix Authorization Bypass Through User-Controlled Key? Upgrade `org.apache.zookeeper:zookeeper` to version 3.7.2, 3.8.3, 3.9.1 or higher.	[,3.7.2)[3.8.0,3.8.3)[3.9.0,3.9.1)
M Access Control Bypass org.apache.zookeeper:zookeeper is a centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services. Affected versions of this package are vulnerable to Access Control Bypass. ZooKeeper’s `getACL()` method doesn’t check any permission when retrieving the ACLs of the requested node and returns all information contained in the ACL `Id` field as plain text string. If Digest Authentication is in use, the unsalted hash value will be disclosed by the `getACL()` method for unauthenticated or unprivileged users. How to fix Access Control Bypass? Upgrade `org.apache.zookeeper:zookeeper` to version 3.4.14, 3.5.5 or higher.	[,3.4.14)[3.5.0-alpha,3.5.5)
H Authentication Bypass org.apache.zookeeper:zookeeper is a centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services. Affected versions of this package are vulnerable to Authentication Bypass. No authentication/authorization is enforced when a server attempts to join a quorum, as a result an arbitrary end point could join the cluster and begin propagating counterfeit changes to the leader. How to fix Authentication Bypass? Upgrade `org.apache.zookeeper:zookeeper` to version 3.4.10, 3.5.4-beta or higher.	[,3.4.10)[3.5.0-alpha,3.5.4-beta)
H Denial of Service (DoS) org.apache.zookeeper:zookeeper is a centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services. Affected versions of this package are vulnerable to Denial of Service (DoS). Four letter zookeeper commands (such as `wchp`/`wchc` ) are not properly handled, which leads to the server unable to serve legitimate client requests. How to fix Denial of Service (DoS)? Upgrade `org.apache.zookeeper:zookeeper` to version 3.4.10, 3.5.3-beta or higher.	[3.4.6,3.4.10)[3.5.0-alpha,3.5.3-beta)
M Insufficiently Protected Credentials org.apache.zookeeper:zookeeper is a centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services. Affected versions of this package are vulnerable to Insufficiently Protected Credentials. The logs cleartext admin passwords, which allows local users to obtain sensitive information by reading the log. How to fix Insufficiently Protected Credentials? Upgrade `org.apache.zookeeper:zookeeper` to version 3.4.7, 3.5.1-alpha or higher.	[3.3.0,3.4.7)[3.5.0-alpha,3.5.1-alpha)

Vulnerability

Vulnerable Version

Authorization Bypass Through User-Controlled Key

org.apache.zookeeper:zookeeper is a centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services.

Affected versions of this package are vulnerable to Authorization Bypass Through User-Controlled Key when the SASL Quorum Peer authentication is enabled (`quorum.auth.enableSasl=true), an attacker can bypass the authorization check by omitting the instance part in the SASL authentication ID. This allows an arbitrary endpoint to join the cluster and propagate counterfeit changes to the leader, effectively granting it full read-write access to the data tree.

Note:

This is only exploitable if quorum.auth.enableSasl=true is set in the configuration.
Quorum Peer authentication is not enabled by default.

How to fix Authorization Bypass Through User-Controlled Key?

Upgrade org.apache.zookeeper:zookeeper to version 3.7.2, 3.8.3, 3.9.1 or higher.

[,3.7.2)[3.8.0,3.8.3)[3.9.0,3.9.1)

Access Control Bypass

org.apache.zookeeper:zookeeper is a centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services.

Affected versions of this package are vulnerable to Access Control Bypass. ZooKeeper’s getACL() method doesn’t check any permission when retrieving the ACLs of the requested node and returns all information contained in the ACL Id field as plain text string. If Digest Authentication is in use, the unsalted hash value will be disclosed by the getACL() method for unauthenticated or unprivileged users.

How to fix Access Control Bypass?

Upgrade org.apache.zookeeper:zookeeper to version 3.4.14, 3.5.5 or higher.

[,3.4.14)[3.5.0-alpha,3.5.5)

Authentication Bypass

org.apache.zookeeper:zookeeper is a centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services.

Affected versions of this package are vulnerable to Authentication Bypass. No authentication/authorization is enforced when a server attempts to join a quorum, as a result an arbitrary end point could join the cluster and begin propagating counterfeit changes to the leader.

How to fix Authentication Bypass?

Upgrade org.apache.zookeeper:zookeeper to version 3.4.10, 3.5.4-beta or higher.

[,3.4.10)[3.5.0-alpha,3.5.4-beta)

Denial of Service (DoS)

org.apache.zookeeper:zookeeper is a centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services.

Affected versions of this package are vulnerable to Denial of Service (DoS). Four letter zookeeper commands (such as wchp/wchc ) are not properly handled, which leads to the server unable to serve legitimate client requests.

How to fix Denial of Service (DoS)?

Upgrade org.apache.zookeeper:zookeeper to version 3.4.10, 3.5.3-beta or higher.

[3.4.6,3.4.10)[3.5.0-alpha,3.5.3-beta)

Insufficiently Protected Credentials

org.apache.zookeeper:zookeeper is a centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services.

Affected versions of this package are vulnerable to Insufficiently Protected Credentials. The logs cleartext admin passwords, which allows local users to obtain sensitive information by reading the log.

How to fix Insufficiently Protected Credentials?

Upgrade org.apache.zookeeper:zookeeper to version 3.4.7, 3.5.1-alpha or higher.

[3.3.0,3.4.7)[3.5.0-alpha,3.5.1-alpha)

org.apache.zookeeper:zookeeper@3.5.0-alpha vulnerabilities

latest version

latest non vulnerable version

first published

latest version published

licenses detected

package manager

Direct Vulnerabilities

How to fix?