CVE-2019-7611
- Source
- https://cve.org/CVERecord?id=CVE-2019-7611
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2019-7611.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2019-7611
- Aliases
- Published
- 2019-03-25T19:29:02.257Z
- Modified
- 2026-07-08T19:51:10.469372Z
- Severity
-
- 8.1 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H CVSS Calculator
- Summary
- [none]
- Details
-
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.dlsfls.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
Affected packages
Git / github.com/elastic/elasticsearch
Affected ranges
- Type
- GIT
- Repo
- https://github.com/elastic/elasticsearch
- Events
-
Introduced0 Unknown introduced commit / All previous commits are affectedFixedIntroducedFixed
- Database specific
{ "cpe": "cpe:2.3:a:elastic:elasticsearch:*:*:*:*:*:*:*:*", "extracted_events": [ { "introduced": "0" }, { "fixed": "5.6.15" }, { "introduced": "6.0.0" }, { "fixed": "6.6.1" } ], "source": "CPE_RANGE" }
Affected versions
v0.*
v0.10.0
v0.11.0
v0.12.0
v0.13.0
v0.14.0
v0.15.0
v0.16.0
v0.17.0
v0.18.0
v0.19.0
v0.19.0.RC1
v0.19.0.RC2
v0.19.0.RC3
v0.20.0.RC1
v0.4.0
v0.5.0
v0.5.1
v0.6.0
v0.7.0
v0.7.1
v0.8.0
v0.9.0
v0.90.0
v0.90.0.Beta1
v0.90.0.RC1
v0.90.0.RC2
v1.*
v1.0.0.Beta1
v1.0.0.Beta2
v1.0.0.RC1
v5.*
v5.0.0-alpha5
v5.6.0
v5.6.1
v5.6.10
v5.6.11
v5.6.12
v5.6.13
v5.6.14
v5.6.2
v5.6.3
v5.6.4
v5.6.5
v5.6.6
v5.6.7
v5.6.8
v5.6.9
v6.*
v6.0.0-alpha1
v6.0.0-alpha2
v6.6.0