Skip to content
Fencer Vulns
medium 4.9

CVE-2020-7021 json

Insertion of Sensitive Information into Log File in Elasticsearch

published 2021-02-10 5 y ago modified 2026-09-08 2 mo ago also BIT-elasticsearch-2020-7021 , EUVD-2022-3611 , GHSA-cqgv-256r-m9r8

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

Summary

Elasticsearch versions before 7.10.0 and 6.8.14 have an information disclosure issue when audit logging and the emit_request_body option is enabled. The Elasticsearch audit log could contain sensitive information such as password hashes or authentication tokens. This could allow an Elasticsearch administrator to view these details.

Patch / fix

  • maven org.elasticsearch:elasticsearch 6.8.14, 7.10.0
  • bitnami elasticsearch 6.8.14, 7.10.0
  • elastic elasticsearch 6.8.14, 7.10.0

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-7021 updated cvss 1.9

elasticsearch: Information disclosure via audit logging with emit_request_body option enabled

  • Red Hat Decision Manager 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 available “Fix deferred”
  • Red Hat Fuse 7 elasticsearch Red Hat Integration Camel K 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.49% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
GitHub 3.1 4.9 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
NVD 3.1 4.9 CVSS:3.1/AV:N/AC:L/PR:H/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 4.9 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Affected packages

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

Affected products

  • Elastic Elasticsearch

Classification

Weakness
  • CWE-532 Insertion of Sensitive Information into Log File

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.