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

> Unauthenticated users can retrieve unsalted password hashes via getACL() when Digest Authentication is enabled, exposing sensitive credentials.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-0201, DLA-1801-1, DSA-4461-1, GHSA-2hw2-62cp-p9p7, UBUNTU-CVE-2019-0201

## What is CVE-2019-0201?

CVE-2019-0201 is a medium-severity vulnerability in Apache Activemq, published on 23 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2019-0201?

4 open source packages ship an affected version, including org.apache.zookeeper:zookeeper. It affects 10 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.zookeeper:zookeeper` | Maven | From 1.0.0 | 3.4.14 |
| `org.apache.zookeeper:zookeeper` | Maven | From 1.0.0 | 3.4.14 |
| `org.apache.zookeeper:zookeeper` | Maven | From 3.5.0 | 3.5.5 |
| `org.apache.zookeeper:zookeeper` | Maven | From 3.5.0 | 3.5.5 |

Products: Apache Activemq, Apache Drill, Apache Zookeeper, Debian Debian Linux, Netapp Element Software, Netapp Hci Bootstrap Os, Oracle Goldengate Stream Analytics, Oracle Siebel Core - Server Framework, Oracle Timesten In-Memory Database, Redhat Fuse.

## How do I fix CVE-2019-0201?

Upgrade org.apache.zookeeper:zookeeper to a fixed version for your release line: 3.4.14 or 3.5.5.

## Is CVE-2019-0201 being exploited?

There is no known exploitation of CVE-2019-0201 in the wild and no public exploit code.

## Other vulnerabilities in Apache Activemq

- [CVE-2023-46604](https://insights.sbomify.com/CVE-2023-46604/): Apache ActiveMQ Deserialization of Untrusted Data (critical 10.0, exploited in the wild)
- [CVE-2016-3088](https://insights.sbomify.com/CVE-2016-3088/): Apache ActiveMQ Improper Input Validation (critical 9.8, exploited in the wild)
- [CVE-2026-34197](https://insights.sbomify.com/CVE-2026-34197/): Apache ActiveMQ Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2020-11998](https://insights.sbomify.com/CVE-2020-11998/): Remote code execution in Apache ActiveMQ (critical 9.8)
- [CVE-2013-7285](https://insights.sbomify.com/CVE-2013-7285/): Command Injection in Xstream (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-0201 and fix it if it is affected.

What it is: CVE-2019-0201 is a medium-severity vulnerability in Apache Activemq, published on 23 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-0201 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.zookeeper:zookeeper (Maven): affected from 1.0.0; fixed in 3.4.14
- org.apache.zookeeper:zookeeper (Maven): affected from 1.0.0; fixed in 3.4.14
- org.apache.zookeeper:zookeeper (Maven): affected from 3.5.0; fixed in 3.5.5
- org.apache.zookeeper:zookeeper (Maven): affected from 3.5.0; fixed in 3.5.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-0201/ (Markdown: https://insights.sbomify.com/CVE-2019-0201/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-0201
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-0201
- OSV: https://osv.dev/vulnerability/CVE-2019-0201

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-0201/
Summaries are generated and may contain mistakes; the official description above is the record.