GHSA-2hw2-62cp-p9p7 — zookeeper
MEDIUMGHSA-2hw2-62cp-p9p7 is a medium-severity (CVSS 5.9) CWE-862 vulnerability in org.apache.zookeeper:zookeeper. A fix is available for org.apache.zookeeper:zookeeper — see the affected versions and patch details below.
Access control bypass in Apache ZooKeeper
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-2hw2-62cp-p9p7 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 376,715 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.apache.zookeeper:zookeeper☕org.apache.zookeeper:zookeeperReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.zookeeper:zookeeper | ≥ 1.0.0&&< 3.4.14 | 3.4.14org.apache.zookeeper:zookeeper:3.4.14 |
| ☕Maven | org.apache.zookeeper:zookeeper | ≥ 3.5.0&&< 3.5.5 | 3.5.5org.apache.zookeeper:zookeeper:3.5.5 |
Detection & mitigation playbook
Open-source dependencyDetect
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 GHSA-2hw2-62cp-p9p7 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2hw2-62cp-p9p7 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-2hw2-62cp-p9p7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
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.
| 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 |
Frequently Asked Questions
Is GHSA-2hw2-62cp-p9p7 in your dependencies?
O3 Security finds GHSA-2hw2-62cp-p9p7 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.