Apache ZooKeeper 3.7
Apache ZooKeeper 3.7
The Apache ZooKeeper 3.7 reached end of service life on Jan 19, 2024 — Apache ZooKeeper no longer ships security patches or fixes for it. Our third-party support keeps it safe to run: 24/7 engineers manage issues, remediate vulnerabilities, and help you maintain compliance.
24/7 engineers own your Apache ZooKeeper 3.7 incidents end to end.
Mitigation and patch-around guidance when the vendor no longer ships fixes.
Controls evidence and documentation that keep auditors satisfied.
Specifications
- product
- zookeeper
- release
- 3.7
- product Label
- Apache ZooKeeper
- release Label
- 3.7
- codename
- lts
- latest Version
- 3.7.2
- release Date
- 2021-03-17
- maintained
- source Url
- https://endoflife.date/zookeeper
Lifecycle Dates
- End of Service Life
- Jan 19, 2024
- Last OEM Support
- Jul 19, 2023
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for Apache ZooKeeper 3.7 — monitoring, break/fix, vulnerability work, operations and compliance, before and after EOSL.
| Feature | OEM Support | 3rd Party Support |
|---|---|---|
| Post-EOSL Support | ||
| Break/Fix Support | Until EOSL | |
| 24/7 Monitoring | ||
| Vulnerability Scanning & Remediation | ||
| Managed Operations | ||
| Procedure & Configuration Review | ||
| Compliance & Audit Documentation | Limited | |
| Discounted Migration to Other Platforms |
Why Choose 3rd Party Support for Apache ZooKeeper 3.7?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for Apache ZooKeeper 3.7 when the vendor no longer ships fixes.
Compliance Maintenance
Procedure review, controls evidence and the documentation auditors ask for — maintained continuously, not scrambled at audit time.
24/7 Expert Support
Engineers who know this release monitor, manage and fix issues around the clock — break/fix to managed operations.
Apache ZooKeeper 3.7 Support: Frequently Asked Questions
Is the Apache ZooKeeper 3.7 still supported?
Apache ZooKeeper ended support for the Apache ZooKeeper 3.7 on Jan 19, 2024 — no more patches or fixes from the vendor. Third-party support keeps it covered: our engineers manage issues, remediate vulnerabilities, and help you maintain compliance for as long as you run it.
When is the Apache ZooKeeper 3.7 end of service life (EOSL) date?
Apache ZooKeeper lists the end of service life for the Apache ZooKeeper 3.7 as Jan 19, 2024.
Can I keep using the Apache ZooKeeper 3.7 after its EOSL date?
Yes. EOSL means Apache ZooKeeper stops issuing patches and support — the software itself keeps running. Third-party support covers it from there: issue management, security vulnerability remediation, and the compliance documentation auditors ask for, for as long as you choose to run it.
How much does third-party support for the Apache ZooKeeper 3.7 cost?
Typically 40-70% below the OEM maintenance renewal price. Exact pricing depends on quantity, service level and location — request a quote and we respond within 24 hours.
Known Vulnerabilities Affecting Apache ZooKeeper 3.7
2 published CVEs affect the Apache ZooKeeper 3.7, including 1 rated critical or high severity. Apache ZooKeeper no longer ships security patches for this release — our engineers provide mitigation guidance, workarounds and hardening support.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2023-44981 | CRITICAL | 9.1 | Oct 11, 2023 | Authorization Bypass Through User-Controlled Key vulnerability in Apache ZooKeeper. If SASL Quorum Peer authentication is enabled in ZooKeeper (quorum.auth.enableSasl=true), the authorization is done by verifying that the instance part in SASL authentication ID is listed in zoo.cfg server list. The instance part in SASL auth ID is optional and if it's missing, like 'eve@EXAMPLE.COM', the authorization check will be skipped. As a result an arbitrary endpoint could join the cluster and begin propa |
| CVE-2024-23944 | MEDIUM | 5.3 | Mar 15, 2024 | Information disclosure in persistent watchers handling in Apache ZooKeeper due to missing ACL check. It allows an attacker to monitor child znodes by attaching a persistent watcher (addWatch command) to a parent which the attacker has already access to. ZooKeeper server doesn't do ACL check when the persistent watcher is triggered and as a consequence, the full path of znodes that a watch event gets triggered upon is exposed to the owner of the watcher. It's important to note that only the path |