Skip to content
Fencer Intel
medium 5.2

CVE-2023-49921 json

Elasticsearch Insertion of Sensitive Information into Log File

published 2y ago modified 2mo ago also BIT-elasticsearch-2023-49921 , EUVD-2024-2225 , GHSA-2hjr-vmf3-xwvp

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

Summary

An issue was discovered by Elastic whereby Watcher search input logged the search query results on DEBUG log level. This could lead to raw contents of documents stored in Elasticsearch to be printed in logs. Elastic has released 8.11.2 and 7.17.16 that resolves this issue by removing this excessive logging. This issue only affects users that use Watcher and have a Watch defined that uses the search input and additionally have set the search input’s logger to DEBUG or finer, for example using: org.elasticsearch.xpack.watcher.input.search, org.elasticsearch.xpack.watcher.input, org.elasticsearch.xpack.watcher, or wider, since the loggers are hierarchical.

Patch / fix

  • maven org.elasticsearch:elasticsearch 7.17.16, 8.11.2
  • bitnami elasticsearch 7.17.16, 8.11.2
  • Elastic Elasticsearch 7.17.16, 8.11.2

Is CVE-2023-49921 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-2023-49921 updated cvss 5.2

elasticsearch: Insertion of Sensitive Information into Log File

  • Red Hat Logging Subsystem for Red Hat OpenShift openshift-logging/fluentd-rhel8, openshift-logging/kibana6-rhel8 Red Hat OpenStack Platform 16.1 python3-panko, openstack-panko-api, openstack-panko-common Red Hat OpenStack Platform 16.2 python3-panko, openstack-panko-api, openstack-panko-common Red Hat Quay 3 quay/quay-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

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2y ago

Exploit prediction

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

CVSS scores

assigned by version score vector
CNA 3.1 5.2 CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
GitHub 3.1 5.2 CVSS:3.1/AV:A/AC:L/PR:L/UI:R/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
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.17.16
>=8.0.0, <8.11.2
7.17.16
8.11.2
bitnami elasticsearch
>=7.0.0, <7.17.16
>=8.0.0, <8.11.2
7.17.16
8.11.2

Affected products

  • Elastic Elasticsearch

Classification

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

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.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.