CVE-2019-7611
published 2019-03-25CVE-2019-7611: 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…
PriorityP345high8.1CVSS 3.1
AVNACHPRNUINSUCHIHAH
EPSS
2.15%
79.8th percentile
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.
Affected
3 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| elastic | elasticsearch | < 5.6.15 | 5.6.15 |
| elastic | elasticsearch | — | — |
| elastic | elasticsearch | >= 6.0.0 < 6.6.1 | 6.6.1 |
CVSS provenance
nvdv3.18.1HIGHCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
nvdv2.06.8MEDIUMAV:N/AC:M/Au:N/C:P/I:P/A:P
vendor_redhat8.1HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
Improper Access Control in Elasticsearch
ghsa·2022-05-13
CVE-2019-7611 [HIGH] CWE-284 Improper Access Control in Elasticsearch
Improper Access Control in Elasticsearch
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.
OSV
Improper Access Control in Elasticsearch
osv·2022-05-13
CVE-2019-7611 [HIGH] Improper Access Control in Elasticsearch
Improper Access Control in Elasticsearch
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.
Red Hat
elasticsearch: Improper permission issue when attaching a new name to an index
vendor_redhat·2019-02-19·CVSS 8.1
CVE-2019-7611 [HIGH] CWE-285 elasticsearch: Improper permission issue when attaching a new name to an index
elasticsearch: Improper permission issue when attaching a new name to an index
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.
Statement: Red Hat OpenStack Platform 8.0/9.0 Operational Tools Kibana/Elasticsearch versions do not include nor support X-Pack (8/9 versions must use the optional Shield, also not packaged
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2019-7611 elasticsearch: Improper permission issue when attaching a new name to an index [fedora-all]
bugzilla·2019-04-04·CVSS 8.1
CVE-2019-7611 [HIGH] CVE-2019-7611 elasticsearch: Improper permission issue when attaching a new name to an index [fedora-all]
CVE-2019-7611 elasticsearch: Improper permission issue when attaching a new name to an index [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects
Bugzilla
CVE-2019-7611 elasticsearch: Improper permission issue when attaching a new name to an index
bugzilla·2019-04-04·CVSS 8.1
CVE-2019-7611 [HIGH] CVE-2019-7611 elasticsearch: Improper permission issue when attaching a new name to an index
CVE-2019-7611 elasticsearch: Improper permission issue when attaching a new name to an index
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.
References:
https://discuss.elastic.co/t/elastic-stack-6-6-1-and-5-6-15-security-update/169077
Discussion:
Created elasticsearch tracking bugs for this issue:
Affects: fed
2019-03-25
Published