Skip to content
Fencer Intel
high 8.1

CVE-2019-7611 json

Improper Access Control in Elasticsearch

published 7y ago modified 4mo ago also GHSA-fj32-6v7m-57pg , EUVD-2022-3790

cvss
8.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.1%
EPSS 2.1% chance of exploitation in 30 days, percentile 82%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.elasticsearch:elasticsearch 5.6.15, 6.6.1
  • elastic elasticsearch 5.6.15, 6.6.1

Is CVE-2019-7611 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-7611 updated cvss 6.8

elasticsearch: Improper permission issue when attaching a new name to an index

  • Red Hat JBoss Fuse 6 elasticsearch Red Hat OpenShift Container Platform 3.2 elasticsearch Red Hat OpenShift Container Platform 3.3 elasticsearch Red Hat OpenShift Container Platform 3.4 elasticsearch Red Hat OpenShift Container Platform 3.5 elasticsearch Red Hat OpenShift Container Platform 3.6 elasticsearch
    +1 more products
    Red Hat OpenShift Container Platform 3.7 elasticsearch
    affected: no fix planned “Out of support scope”
  • Red Hat OpenShift Container Platform 3.9 elasticsearch Red Hat OpenShift Container Platform 3.10 elasticsearch Red Hat OpenShift Container Platform 3.11 openshift3/ose-logging-elasticsearch5 Red Hat OpenShift Container Platform 4 openshift4/ose-logging-elasticsearch5
    affected: no fix planned “Will not fix”
  • Red Hat OpenShift Enterprise 3.1 elasticsearch
    affected: no fix planned “Out of support scope”
  • Red Hat Decision Manager 7
    fixed: vendor fix RHSA-2020:0899
  • Red Hat Process Automation 7
    fixed: vendor fix RHSA-2020:0895
  • Red Hat Fuse 7 elasticsearch Red Hat OpenStack Platform 8 (Liberty) Operational Tools elasticsearch Red Hat OpenStack Platform 9 (Mitaka) Operational Tools elasticsearch
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.15% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P
GitHub 3.1 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.elasticsearch:elasticsearch
<5.6.15
>=6.0.0, <6.6.1
5.6.15
6.6.1

Affected products

  • Elastic Elasticsearch

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.