CVE-2018-3825
First published: Wed Sep 19 2018(Updated: )
In Elastic Cloud Enterprise (ECE) versions prior to 1.1.4 a default master encryption key is used in the process of granting ZooKeeper access to Elasticsearch clusters. Unless explicitly overwritten, this master key is predictable across all ECE deployments. If an attacker can connect to ZooKeeper directly they would be able to access configuration information of other tenants if their cluster ID is known.
Credit: bressers@elastic.co
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Elastic Elastic Cloud Enterprise | <1.1.4 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is CVE-2018-3825?
CVE-2018-3825 is a vulnerability in Elastic Cloud Enterprise (ECE) versions prior to 1.1.4 where a default master encryption key is used in granting ZooKeeper access to Elasticsearch clusters.
How does CVE-2018-3825 affect Elastic Cloud Enterprise?
CVE-2018-3825 affects Elastic Cloud Enterprise (ECE) versions prior to 1.1.4, allowing an attacker to connect to ZooKeeper and potentially gain unauthorized access to Elasticsearch clusters.
What is the severity of CVE-2018-3825?
CVE-2018-3825 has a severity rating of medium with a CVSS score of 5.9.
How can I fix CVE-2018-3825?
To fix CVE-2018-3825, it is recommended to update Elastic Cloud Enterprise to version 1.1.4 or later.
Where can I find more information about CVE-2018-3825?
More information about CVE-2018-3825 can be found on the Elastic discussion forum and the Elastic community security page.
- collector/nvd-index
- agent/severity
- agent/references
- agent/weakness
- agent/author
- agent/type
- agent/tags
- agent/description
- agent/event
- agent/softwarecombine
- agent/last-modified-date
- agent/first-publish-date
- collector/mitre-cve
- source/MITRE
- vendor/elastic
- canonical/elastic elastic cloud enterprise