CVE-2017-5637

Description

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.

Category

7.5
CVSS
Severity: High
CVSS 3.0 •
CVSS 2.0 •
EPSS 19.98% Top 5%
Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory debian.org Vendor Advisory apache.org
Affected: Apache Software Foundation Apache ZooKeeper
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2017-5637?
CVE-2017-5637 has been scored as a high severity vulnerability.
How to fix CVE-2017-5637?
To fix CVE-2017-5637, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2017-5637 being actively exploited in the wild?
It is possible that CVE-2017-5637 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~20% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2017-5637?
CVE-2017-5637 affects Apache Software Foundation Apache ZooKeeper.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.