elasticsearch: Improper permission issue when attaching a new name to an index
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Elastic | Elasticsearch | affected |
|
Configuration 1 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Decision Manager 7 | |||
| elasticsearch | cpe:/a:redhat:jboss_enterprise_brms_platform:7.7 | RHSA-2020:0899 | 2020-03-18T00:00:00Z |
| Red Hat Process Automation 7 | |||
| elasticsearch | cpe:/a:redhat:jboss_enterprise_bpms_platform:7.7 | RHSA-2020:0895 | 2020-03-18T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2022-3790 | 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. |
Github GHSA |
GHSA-fj32-6v7m-57pg | Improper Access Control in Elasticsearch |
No CVSS v4.0
This CVE is not in the KEV list.
Exploit prediction score: 2.1% (2.149% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.