Vulnerability 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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Elastic | Elasticsearch | >= 7.0.0, < 7.17.16 |
Related Weaknesses (CWE)
References
- https://discuss.elastic.co/t/elasticsearch-8-11-2-7-17-16-security-update-esa-20Vendor Advisory
- https://discuss.elastic.co/t/elasticsearch-8-11-2-7-17-16-security-update-esa-20Vendor Advisory
FAQ
What is CVE-2023-49921?
CVE-2023-49921 is a vulnerability with a CVSS score of 5.2 (MEDIUM). 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 i...
How severe is CVE-2023-49921?
CVE-2023-49921 has been rated MEDIUM with a CVSS base score of 5.2/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2023-49921?
Check the references section above for vendor advisories and patch information. Affected products include: Elastic Elasticsearch.