CVE-2023-49921: Medium severity elastic vulnerability
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2023-49921?
CVE-2023-49921 is considered a moderate severity vulnerability due to the potential exposure of sensitive document contents in the logs.
How do I fix CVE-2023-49921?
To fix CVE-2023-49921, update your Elasticsearch installation to version 8.11.2 or 7.17.16.
What impact does CVE-2023-49921 have on my system?
CVE-2023-49921 could lead to sensitive data exposure through the logging of search query results in DEBUG logs.
Which versions of Elasticsearch are affected by CVE-2023-49921?
Elasticsearch versions between 7.0.0 and 7.17.16, and between 8.0.0 and 8.11.2 are affected by CVE-2023-49921.
Is the logging issue in CVE-2023-49921 an isolated vulnerability?
CVE-2023-49921 specifically relates to the logging of search query results and does not indicate other vulnerabilities.