# Elastic Cloud Enterprise 1.0.2 security update

**URL:** <https://discuss.elastic.co/t/elastic-cloud-enterprise-1-0-2-security-update/100247>\
**Category:** Security Announcements\
**Created:** [September 12, 2017, 6:20pm UTC](https://discuss.elastic.co/t/elastic-cloud-enterprise-1-0-2-security-update/100247 "2017-09-12T18:20:46Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![joshbressers](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joshbressers/32/42332_2.png) [@joshbressers](https://discuss.elastic.co/u/joshbressers)\
**Post date:** [September 12, 2017, 6:20pm UTC](https://discuss.elastic.co/t/elastic-cloud-enterprise-1-0-2-security-update/100247/1 "2017-09-12T18:20:46Z")

</div>

**Elastic Cloud Enterprise unsecured communication (ESA-2017-13)**

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.

**Affected Versions:** ECE 1.0.0 and 1.0.1

**Solutions and Mitigations:**  
All Elastic Cloud Enterprise users should upgrade to version 1.0.2. There is no known workaround for this issue.

**CVE ID:** CVE-2017-8444

---

_[View the full topic](https://discuss.elastic.co/t/elastic-cloud-enterprise-1-0-2-security-update/100247)._