CVE-2023-49921

Description

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.

Category

5.2
CVSS
Severity: Medium
CVSS 3.1 •
EPSS 0.49%
Vendor Advisory elastic.co
Affected: Elastic Elasticsearch
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2023-49921?
CVE-2023-49921 has been scored as a medium severity vulnerability.
How to fix CVE-2023-49921?
To fix CVE-2023-49921, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2023-49921 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2023-49921 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2023-49921?
CVE-2023-49921 affects Elastic Elasticsearch.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.