CVE-2019-7611

Description

A permission issue was found in Elasticsearch versions before 5.6.15 and 6.6.1 when Field Level Security and Document Level Security are disabled and the _aliases, _shrink, or _split endpoints are used . If the elasticsearch.yml file has xpack.security.dls_fls.enabled set to false, certain permission checks are skipped when users perform one of the actions mentioned above, to make existing data available under a new index/alias name. This could result in an attacker gaining additional permissions against a restricted index.

Category

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

References

Frequently Asked Questions

What is the severity of CVE-2019-7611?
CVE-2019-7611 has been scored as a high severity vulnerability.
How to fix CVE-2019-7611?
To fix CVE-2019-7611, 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-2019-7611 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2019-7611 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-2019-7611?
CVE-2019-7611 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.