CVE-2023-49921mediumCWE-532

CVE-2023-49921: medium-severity vulnerability in Elasticsearch

Published · Updated

Follow this CVE+ Monitor Elasticsearch+ Monitor org.elasticsearch:elasticsearch

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

13Vexday Risk Score

No sign of exploitation. No public exploitation artifact known so far.

ssvc Trackcvss 5.2epss 0.4%
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:3.1/AV:A/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
Affected products
Elastic · Elasticsearch
Related CVEs — Elasticsearch

In the same product, most dangerous first.

CVE-2021-22145—CVE-2021-22145EPSS 76.2%CVE-2023-31419MEDIUMElasticsearch StackOverflow vulnerabilityEPSS 61.1%CVE-2019-7619—CVE-2019-7619EPSS 2.4%CVE-2019-7611—CVE-2019-7611EPSS 2.1%CVE-2023-31418HIGHElasticsearch uncontrolled resource consumptionEPSS 2.1%CVE-2018-3831—CVE-2018-3831EPSS 2.0%