CVE-2023-49921 Elasticsearch Insertion of Sensitive Information into Log File
Elasticsearch Watcher search inputs log raw document contents at DEBUG level, exposing sensitive data to users with log access.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2023-49921?
CVE-2023-49921 is a medium-severity vulnerability in Elastic Elasticsearch, published on 26 Jul 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Official 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.
Weakness: CWE-532
Which versions are affected by CVE-2023-49921?
5 open source packages ship an affected version, including org.elasticsearch:elasticsearch and elasticsearch. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
org.elasticsearch:elasticsearch Maven | All versions | 7.17.16 |
org.elasticsearch:elasticsearch Maven | All versions | 7.17.16 |
org.elasticsearch:elasticsearch Maven | From 8.0.0 | 8.11.2 |
org.elasticsearch:elasticsearch Maven | From 8.0.0 | 8.11.2 |
elasticsearch Bitnami | From 7.0.0 | 7.17.16, 8.11.2 |
Products include Elastic Elasticsearch.
How do I fix CVE-2023-49921?
Upgrade org.elasticsearch:elasticsearch to a fixed version for your release line: 7.17.16 or 8.11.2.
Is CVE-2023-49921 being exploited?
There is no known exploitation of CVE-2023-49921 in the wild and no public exploit code.
Other vulnerabilities in Elastic Elasticsearch
- CVE-2015-1427 Elasticsearch Groovy Scripting Engine Remote Code Execution
- CVE-2014-3120 Elasticsearch Remote Code Execution
- CVE-2015-5377 Code injection in n/a
- CVE-2026-72649 Deserialization of Untrusted Data in Elasticsearch Leading to Remote Code Execution
- CVE-2026-72642 Use of Out-of-range Pointer Offset in the Elasticsearch Machine Learning Native Inference Process
Sources
Also known as BIT-elasticsearch-2023-49921, GHSA-2hjr-vmf3-xwvp, MINI-fr6h-5ccx-q3cr, MINI-jqrh-pc2w-cqrh, UBUNTU-CVE-2023-49921.