Skip to content
Fencer Vulns
medium 4.1

CVE-2023-31417 json

Elasticsearch Insertion of sensitive information in audit logs

published 2023-10-26 3 y ago modified 2026-09-08 2 mo ago also BIT-elasticsearch-2023-31417 , EUVD-2023-2709 , GHSA-99pc-69q9-jxf2

cvss
4.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 15%
public exploits
0
none known

Summary

Elasticsearch generally filters out sensitive information and credentials before logging to the audit log. It was found that this filtering was not applied when requests to Elasticsearch use certain deprecated URIs for APIs. The impact of this flaw is that sensitive information such as passwords and tokens might be printed in cleartext in Elasticsearch audit logs. Note that audit logging is disabled by default and needs to be explicitly enabled and even when audit logging is enabled, request bodies that could contain sensitive information are not printed to the audit log unless explicitly configured.

Patch / fix

  • maven org.elasticsearch:elasticsearch 7.17.13, 8.9.2
  • bitnami elasticsearch 7.17.13, 8.9.2
  • Elastic Elasticsearch 7.17.12, 8.9.1

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-2023-31417 updated cvss 4.1

elasticsearch: Sensitive information in audit logs

  • Red Hat OpenShift Container Platform 3.11 openshift3/ose-logging-elasticsearch5
    affected: workaround, no fix planned “Out of support scope”
  • Red Hat OpenShift Container Platform 4 elasticsearch
    affected: workaround, no fix planned “Will not fix”
  • Red Hat Logging Subsystem for Red Hat OpenShift openshift-logging/elasticsearch6-rhel8
    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

0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 4.1 CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N
GitHub 3.1 4.1 CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N
NVD 3.1 4.4 CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
OSV 3.1 4.4 CVSS:3.1/AV:L/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
>=7.0.0, <7.17.13
>=8.0.0, <8.9.2
7.17.13
8.9.2
bitnami elasticsearch
>=7.0.0, <7.17.13
>=8.0.0, <8.9.2
7.17.13
8.9.2

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.