CVE-2018-3831

Description

Elasticsearch Alerting and Monitoring in versions before 6.4.1 or 5.6.12 have an information disclosure issue when secrets are configured via the API. The Elasticsearch _cluster/settings API, when queried, could leak sensitive configuration information such as passwords, tokens, or usernames. This could allow an authenticated Elasticsearch user to improperly view these details.

Category

8.8
CVSS
Severity: High
CVSS 3.1 •
CVSS 2.0 •
EPSS 0.57%
Vendor Advisory elastic.co Vendor Advisory elastic.co
Affected: Elastic Elasticsearch
Published at:
Updated at:

References

Link Tags
https://discuss.elastic.co/t/elastic-stack-6-4-1-and-5-6-12-security-update/149035 mitigation vendor advisory
https://www.elastic.co/community/security vendor advisory

Frequently Asked Questions

What is the severity of CVE-2018-3831?
CVE-2018-3831 has been scored as a high severity vulnerability.
How to fix CVE-2018-3831?
To fix CVE-2018-3831, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2018-3831 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2018-3831 is being actively exploited. According to its EPSS score, there is a ~1% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2018-3831?
CVE-2018-3831 affects Elastic Elasticsearch.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.