CVE-2019-0201: Access control bypass in Apache ZooKeeper

CVE-2019-0201 · Severity: low · CVSS 3 · Published 2019-05-29

Access control bypass in Apache ZooKeeper

Technologies: org.apache.zookeeper:zookeeper (Maven). Vendors: Maven.

Quick answers

Is CVE-2019-0201 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2019-0201 being exploited in the wild.
How severe is CVE-2019-0201?
Low severity, with a CVSS score of 3, published 29 May 2019.
Which products and versions are affected?
org.apache.zookeeper:zookeeper (Maven) ECOSYSTEM:introduced=1.0.0,fixed=3.4.14.
Is there a fix for CVE-2019-0201?
Yes. org.apache.zookeeper:zookeeper (Maven): upgrade to 3.4.14 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2019-0201?
Check whether you run org.apache.zookeeper:zookeeper (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.apache.zookeeper:zookeeper (Maven): upgrade to 3.4.14 or later
    # set org.apache.zookeeper:zookeeper to 3.4.14 in your pom.xml or build.gradle

Affected products

  • org.apache.zookeeper:zookeeper (Maven) ECOSYSTEM:introduced=1.0.0,fixed=3.4.14

Identifiers

  • CVE-2019-0201
  • GHSA-2hw2-62cp-p9p7

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.