CVE-2017-5637
HighSummary
Two four-letter commands 'wchp/wchc' are CPU intensive and can cause a spike in CPU utilization on the Apache ZooKeeper server if abused, leading to the server being unable to serve legitimate client requests.
Risk Assessment
Abuse of these commands can lead to server overload, resulting in service unavailability for users. Organizations may experience downtime and reduced system performance.
Recommendation
It is recommended to upgrade to versions 3.4.10, 3.5.3, or later to mitigate this vulnerability. Monitoring CPU usage and restricting access to these commands can also help manage the risk.
Other vulnerabilities in Apache ZooKeeper
See all- CVE-2016-5017High
Buffer overflow in the C cli shell in Apache Zookeeper before version 3.4.9 and 3.5.x before version 3.5.3, occurring when using the 'cmd:' batch mode syntax, allows attackers to have unspecified impact via a long command string.
- CVE-2026-24308High
In Apache ZooKeeper versions 3.8.5 and 3.9.4, improper handling of configuration values in ZKConfig allows an attacker to expose sensitive information stored in client configuration in the client's logfile. Configuration values are exposed at INFO level logging, potentially affecting production systems.
- CVE-2026-24281High
In Apache ZooKeeper, hostname verification in ZKTrustManager falls back to reverse DNS (PTR) when IP SAN validation fails, allowing attackers who control or spoof PTR records to impersonate ZooKeeper servers or clients with a valid certificate for the PTR name. The attacker must present a certificate trusted by ZKTrustManager, making the attack vector harder to exploit.
Original NVD description (English source)
Two four letter word commands "wchp/wchc" are CPU intensive and could cause spike of CPU utilization on Apache ZooKeeper server if abused, which leads to the server unable to serve legitimate client requests. Apache ZooKeeper thru version 3.4.9 and 3.5.2 suffer from this issue, fixed in 3.4.10, 3.5.3, and later.