CVE Tools
Track your stack

CVE-2017-5637

Exploitation likely. EPSS gives it a 73% chance of exploitation in the next 30 days. Fixed in 3.4.10.

CVSS 3.07.5HighEPSS percentile99th73% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix3.4.10Upgrade to this build
Check it yourself

OpenVAS · 5 checks

e.g. OID 1.3.6.1.4.1.25623.1.0.703871

Run the check

Published Updated Sources: CVE.org, NVD, GitHub, BDU

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • Apache Software Foundation Apache ZooKeeperAffected: 3.4.0 to 3.4.9Upgrade to: not statedAffected: 3.5.0 to 3.5.2Upgrade to: not statedStated by: CVE record
  • Maven org.apache.zookeeper:zookeeperAffected: ≥ 3.4.0, < 3.4.10Upgrade to: 3.4.10Stated by: GitHub advisory
  • Сообщество свободного программного обеспечения Debian GNU/LinuxAffected: 8Upgrade to: not statedStated by: BDU
  • ООО «Ред Софт» РЕД ОСAffected: 7.3Upgrade to: not statedStated by: BDU
  • Oracle Corp. Siebel Core - Server FrameworkAffected: от 21.0 до 21.5 включительноUpgrade to: not statedStated by: BDU

Versions as the sources state them. 3 more products have version data. Full version matrix after sign-in

Check it yourselfA free OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

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.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS99th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

73% chance of exploitation activity in the next 30 days, which ranks it in the 99th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

8 events over 3180 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. EPSS band changemoderate → high
  3. Patch availableworkaround available, record updated
  4. Publishedweakness classified, att&ck mapped

Affected products

And 2 more affected products. See all after sign-in

Technical detail

CVSS 3.0 vector

Open in the CVSS calculator

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Scored 7.5 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality NoneNo confidentiality impact
  • Integrity NoneNo integrity impact
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

And 19 more references. See all after sign-in

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Red Hat JBoss BRMS, not every advisory.