{"uuid": "94e1d1c6-a5b2-490a-9f26-aec34b67eb4a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-49921", "type": "seen", "source": "https://t.me/cvedetector/1669", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-49921 - ElasticWatcher DEBUG Logging Information Disclosure Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2023-49921 \nPublished : July 26, 2024, 5:15 a.m. | 38\u00a0minutes ago \nDescription : 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\u2019s 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. \nSeverity: 5.2 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"26 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-26T07:58:22.000000Z"}