CVE-2017-5637

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of service disruption.

Exploit odds

73.1% chance of exploitation in the next 30 days (EPSS). Higher than most.

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2017-10-10 01:30 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 01:20 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 73.1% in the next 30 days (EPSS).
• Severity: 7.5 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2017-10-10 01:30 UTC

Last modified

2026-06-17 01:20 UTC

Exploit probability

73.1% · EPSS, next 30 days

Weakness

CWE-306 · Missing authentication

Record status

Modified

Affected

• Apache Zookeeper 3.4.0
• Apache Zookeeper 3.4.1
• Apache Zookeeper 3.4.2
• Apache Zookeeper 3.4.3
• Apache Zookeeper 3.4.4
• Apache Zookeeper 3.4.5
• Apache Zookeeper 3.4.6
• Apache Zookeeper 3.4.7

Attack profile CVSS 3.0 · 7.5

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2017-5637.md and follow it. Check whether this project is affected by CVE-2017-5637. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge