Skip to content
Fencer Vulns
medium 4.8

CVE-2021-22132 json

Insufficiently Protected Credentials in Elasticsearch

published 2021-01-14 5 y ago modified 2026-09-08 2 mo ago also BIT-elasticsearch-2021-22132 , EUVD-2021-0610 , GHSA-5fvx-2jj3-6mff

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

Summary

Elasticsearch versions 7.7.0 to 7.10.1 contain an information disclosure flaw in the async search API. Users who execute an async search will improperly store the HTTP headers. An Elasticsearch user with the ability to read the .tasks index could obtain sensitive request headers of other users in the cluster. This issue is fixed in Elasticsearch 7.10.2

Patch / fix

  • maven org.elasticsearch:elasticsearch 7.10.2
  • bitnami elasticsearch 7.10.2
  • elastic elasticsearch 7.10.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-22132 updated cvss 4.8

elasticsearch: executing async search improperly stores HTTP headers leading to information disclosure

  • Red Hat Decision Manager 7 elasticsearch
    affected: no fix planned “Will not fix”
  • Red Hat Fuse 7 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 planned “Will not fix”
  • Red Hat RHAF Camel-K 1.8
    fixed: vendor fix RHSA-2022:6407
  • Red Hat RHINT Camel-Q 2.7
    fixed: vendor fix RHSA-2022:5606
  • 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.22% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

Affected packages

ecosystem package affected fixed in
maven org.elasticsearch:elasticsearch
>=7.7.0, <7.10.2
7.10.2
bitnami elasticsearch
>=7.7.0, <7.10.2
7.10.2

Affected products

  • Elastic Elasticsearch

Classification

Weakness
  • CWE-522 Insufficiently Protected Credentials

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.