High severity · published Sep 19, 2018
CVE-2018-3828
Elastic Cloud Enterprise (ECE) versions prior to 1.1.4 contain an information exposure vulnerability
7.5
CVSS
0.6%
EPSS
No
On KEV
Description
Elastic Cloud Enterprise (ECE) versions prior to 1.1.4 contain an information exposure vulnerability. It was discovered that certain exception conditions would result in encryption keys, passwords, and other security sensitive headers being leaked to the allocator logs. An attacker with access to the logging cluster may obtain leaked credentials and perform authenticated actions using these credentials.
CVSS vector
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Confidentiality
High
Integrity
High
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.6% · higher than 48% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
EC
Elastic Cloud Enterprise · Elastic
before 1.1.4 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2018-3828
CVE.org
https://www.cve.org/CVERecord?id=CVE-2018-3828
Vendor Advisory
https://discuss.elastic.co/t/elastic-cloud-enterprise-1-1-4-security-update/135778
Vendor Advisory
https://www.elastic.co/community/security
More from Elastic Cloud Enterprise
9.8
CVE-2024-37282
It was identified that under certain specific preconditions, an API key that was originally created with a specific privileges could be subsequently used to create new API keys…
8.8
CVE-2025-37736
Elastic Cloud Enterprise Improper Authorization
8.2
CVE-2026-115709
Improper Link Resolution Before File Access ('Link Following') in Elastic Cloud Enterprise (ECE) Leading to Information Disclosure and Data Loss
7.5
CVE-2026-115713
Improper Link Resolution Before File Access ('Link Following') in Elastic Cloud Enterprise (ECE) Leading to Information Disclosure and Data Modification
7.5
CVE-2023-31418
An issue has been identified with how Elasticsearch handled incoming requests on the HTTP layer
