Skip to content
Fencer Intel
medium 6.5

CVE-2020-7019 json

Improper privilege management in elasticsearch

published 6y ago modified 2mo ago also BIT-elasticsearch-2020-7019 , EUVD-2022-3523 , GHSA-c77j-p484-h84m

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

Summary

In Elasticsearch before 7.9.0 and 6.8.12 a field disclosure flaw was found when running a scrolling search with Field Level Security. If a user runs the same query another more privileged user recently ran, the scrolling search can leak fields that should be hidden. This could result in an attacker gaining additional permissions against a restricted index.

Patch / fix

  • maven org.elasticsearch:elasticsearch 6.8.12, 7.9.0
  • bitnami elasticsearch 6.8.12, 7.9.0
  • elastic elasticsearch 6.8.12, 7.9.0

Is CVE-2020-7019 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-2020-7019 updated cvss 5.3

elasticsearch: scrolling search can leak fields that should be hidden allowing access restriction bypass

  • Red Hat Decision Manager 7 elasticsearch Red Hat Fuse 7 elasticsearch Red Hat JBoss Fuse 6 elasticsearch Red Hat OpenShift Container Platform 3.11 openshift3/ose-logging-elasticsearch5 Red Hat OpenShift Container Platform 4 openshift4/ose-logging-elasticsearch5, openshift4/ose-logging-elasticsearch6 Red Hat Process Automation 7 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

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

CVSS scores

assigned by version score vector
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N
OSV 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.elasticsearch:elasticsearch
>=7.0.0, <7.9.0
<6.8.12
7.9.0
6.8.12
bitnami elasticsearch
<6.8.12
>=7.0.0, <7.9.0
6.8.12
7.9.0

Affected products

  • Elastic Elasticsearch

Classification

Weakness
  • CWE-270 Privilege Context Switching Error
  • CWE-269 Improper Privilege Management

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.