How severe is CVE-2019-0201?

CVE-2019-0201 has a CVSS score of 5.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2019-0201?

CVE-2019-0201 affects the following packages: org.apache.zookeeper:zookeeper (Maven), org.apache.zookeeper:zookeeper (Maven). Ecosystems affected: Maven.

How do I fix CVE-2019-0201?

Update org.apache.zookeeper:zookeeper to 3.4.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-0201 is resolved across your whole dependency graph.

How do I detect CVE-2019-0201 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.zookeeper:zookeeper, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2019-0201 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2019-0201 actively exploited in the wild?

No public exploit code has been indexed for CVE-2019-0201 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2019-0201?

CVE-2019-0201 has an EPSS (Exploit Prediction Scoring System) score of 9.7%, placing it in the 96th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2019-0201?

CVE-2019-0201 is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2019-0201 published, and has it been updated?

CVE-2019-0201 was published on May 23, 2019 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2019-0201: zookeeper — Fixed in 3.4.14

EPSS Exploitation Probability

via FIRST.org ↗

9.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs96th percentile — riskier than 96% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

☕org.apache.zookeeper:zookeeper☕org.apache.zookeeper:zookeeper

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

An issue is present in Apache ZooKeeper 1.0.0 to 3.4.13 and 3.5.0-alpha to 3.5.4-beta. ZooKeeper’s getACL() command doesn’t check any permission when retrieves the ACLs of the requested node and returns all information contained in the ACL Id field as plaintext string. DigestAuthenticationProvider overloads the Id field with the hash value that is used for user authentication. As a consequence, if Digest Authentication is in use, the unsalted hash value will be disclosed by getACL() request for unauthenticated or unprivileged users.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.zookeeper:zookeeper`	≥ 1.0.0&&< 3.4.14	3.4.14`org.apache.zookeeper:zookeeper:3.4.14`
☕Maven	`org.apache.zookeeper:zookeeper`	≥ 3.5.0&&< 3.5.5	3.5.5`org.apache.zookeeper:zookeeper:3.5.5`

Affected Products

10 products · 30 configurations

Application

activemqapache

1 version

5.15.9

Application

drillapache

1 version

1.16.0

Application

zookeeperapache

≥ 1.0.0 && ≤ 3.4.13

5 versions

3.5.03.5.13.5.23.5.33.5.4

OS

debian linuxdebian

2 versions

8.09.0

Application

element softwarenetapp

all

OS

hci bootstrap osnetapp

all

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.zookeeper:zookeeper, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.zookeeper:zookeeper to 3.4.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-0201 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Workaround published by Red Hat

Use an authentication method other than Digest (e.g. Kerberos) or upgrade to zookeeper 3.4.14 or later (3.5.5 or later if on the 3.5 branch). [https://zookeeper.apache.org/security.html#CVE-2019-0201]

Source: Red Hat security advisory for CVE-2019-0201 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat Fuse 6.3	`zookeeper`	RHSA-2019:4352
Red Hat Fuse 7.5.0	`zookeeper`	RHSA-2019:3892
Red Hat JBoss Data Virtualization 6.4.8	`zookeeper`	RHSA-2019:3140

UbuntuMEDIUM

USN-6559-1Ubuntu

Frequently Asked Questions

An issue is present in Apache ZooKeeper 1.0.0 to 3.4.13 and 3.5.0-alpha to 3.5.4-beta. ZooKeeper’s getACL() command doesn’t check any permission when retrieves the ACLs of the requested node and returns all information contained in the ACL Id field as plaintext string. DigestAuthenticationProvider overloads the Id field with the hash value that is used for user authentication. As a consequence, if Digest Authentication is in use, the unsalted hash value will be disclosed by getACL() request for unauthenticated or unprivileged users.

O3 Security · Impact-Aware SCA

Is CVE-2019-0201 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2019-0201 — zookeeper

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2019-0201 in your dependencies?