Skip to content
Fencer Vulns
medium 5.3

CVE-2021-22135 json

API information disclosure flaw in Elasticsearch

published 2021-05-13 5 y ago modified 2026-09-08 2 mo ago also BIT-elasticsearch-2021-22135 , EUVD-2021-1442 , GHSA-62ww-4p3p-7fhj

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

Summary

Elasticsearch versions before 7.11.2 and 6.8.15 contain a document disclosure flaw was found in the Elasticsearch suggester and profile API when Document and Field Level Security are enabled. The suggester and profile API are normally disabled for an index when document level security is enabled on the index. Certain queries are able to enable the profiler and suggester which could lead to disclosing the existence of documents and fields the attacker should not be able to view.

Patch / fix

  • maven org.elasticsearch:elasticsearch 6.8.15, 7.11.2
  • bitnami elasticsearch 6.8.15, 7.11.2
  • elastic elasticsearch 6.8.15, 7.11.2

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-2021-22135 updated cvss 3.1

elasticsearch: Document disclosure flaw in the Elasticsearch suggester

  • Red Hat Decision Manager 7 elasticsearch Red Hat Fuse 7 elasticsearch Red Hat Integration Camel K 1 elasticsearch
    affected: no fix available “Fix deferred”
  • Red Hat JBoss Fuse 6 elasticsearch
    affected: no fix planned “Out of support scope”
  • Red Hat Process Automation 7 elasticsearch
    affected: no fix available
  • Red Hat RHINT Camel-Q 2.7
    fixed: vendor fix RHSA-2022:5606
  • Red Hat Logging Subsystem for Red Hat OpenShift openshift-logging/elasticsearch6-rhel8 Red Hat Integration Camel Quarkus 1 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
    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.34% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

Affected packages

ecosystem package affected fixed in
maven org.elasticsearch:elasticsearch
>=7.0.0, <7.11.2
<6.8.15
7.11.2
6.8.15
bitnami elasticsearch
<6.8.15
>=7.11.0, <7.11.2
6.8.15
7.11.2

Affected products

  • Elastic Elasticsearch

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Vulns 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.