Skip to content

Improper Access Control in Elasticsearch

High severity GitHub Reviewed Published May 13, 2022 to the GitHub Advisory Database • Updated Jan 27, 2023

Package

maven org.elasticsearch:elasticsearch (Maven)

Affected versions

< 5.6.15
>= 6.0.0, < 6.6.1

Patched versions

5.6.15
6.6.1

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.

References

Published by the National Vulnerability Database Mar 25, 2019
Published to the GitHub Advisory Database May 13, 2022
Reviewed Jun 27, 2022
Last updated Jan 27, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.244%
(65th percentile)

Weaknesses

CVE ID

CVE-2019-7611

GHSA ID

GHSA-fj32-6v7m-57pg

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.