CVE-2023-49921
elasticsearch: Insertion of Sensitive Information into Log File
Overview
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.
Source: OX vulnerability database
Severity
6.5 · MEDIUM
CVSS 3.1 base score, scored by NVD.
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Weakness: CWE-532
Affected packages · 2
| Ecosystem | Package | Vulnerable | Fixed in |
|---|---|---|---|
| Bitnami | elasticsearch | >=7.0.0, <7.17.16>=8.0.0, <8.11.2 | 7.17.168.11.2 |
| Maven | org.elasticsearch:elasticsearch | <7.17.16>=8.0.0, <8.11.2 | 7.17.168.11.2 |
Open a package to see all its vulnerabilities.
Operating systems · 1 fix
minimos 1 release · 1 package
| Release | Package | Fixed in |
|---|---|---|
| conductor +1 | 3.32.1-r0 |
References
- access.redhat.com https://access.redhat.com/security/cve/CVE-2023-49921
- discuss.elastic.co https://discuss.elastic.co/t/elasticsearch-8-11-2-7-17-16-security-update-esa-2023-29/349179
- github.com https://github.com/elastic/elasticsearch
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2023-49921
- www.cve.org https://www.cve.org/CVERecord?id=CVE-2023-49921
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.