Skip to content

GHSA-2hjr-vmf3-xwvp BIT-elasticsearch-2023-49921 CVE-2023-49921

Elasticsearch Insertion of Sensitive Information into Log File

Medium Maven
Severity
0.0 / 10
Medium · CVSS 4.0
Exploit chance (EPSS)
0.45%
Chance of exploitation in the next 30 days. Higher than 38.69% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-532 Insertion of Sensitive Information into Log File
Fix
7.17.16
Upgrade org.elasticsearch:elasticsearch to this version or later

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.

Affected versions

Maven

PackageVulnerableFixed in
org.elasticsearch:elasticsearch
< 7.17.16
7.17.16
org.elasticsearch:elasticsearch
>= 8.0.0, < 8.11.2
8.11.2

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

org.elasticsearch:elasticsearch Maven → 7.17.16

maven
<dependency><groupId>org.elasticsearch</groupId><artifactId>elasticsearch</artifactId><version>7.17.16</version></dependency>
gradle
implementation("org.elasticsearch:elasticsearch:7.17.16")

Severity breakdown

CVSS 4.0 0.0

CVSS:4.0/AV:A/AC:L/AT:P/PR:L/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Attack vector
Adjacent
Attack complexity
Low
Attack requirements
Present
Privileges required
Low
User interaction
Passive
Confidentiality (vulnerable system)
High
Integrity (vulnerable system)
None
Availability (vulnerable system)
None
Confidentiality (subsequent systems)
None
Integrity (subsequent systems)
None
Availability (subsequent systems)
None

CVSS 3.1 5.2

CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N

Attack vector
Adjacent
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Weakness

CWE-532: Insertion of Sensitive Information into Log File

The product writes sensitive information to a log file.

How to prevent it
  • Architecture and Design, Implementation: Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
  • Distribution: Remove debug log files before deploying the application into production.
  • Operation: Protect log files against unauthorized read/write.
  • Implementation: Adjust configurations appropriately when software is transitioned from a debug state to production.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-mrfm-jxgf-2h6v
Elasticsearch Improper Access Control vulnerability
High Known exploited Also affects org.elasticsearch:elasticsearch
GHSA-w94p-6mhw-4qxw
Improper Access Control in Elasticsearch
High Known exploited Also affects org.elasticsearch:elasticsearch
GHSA-mm3m-5497-xggg
Elasticsearch Uncontrolled Resource Consumption Vulnerability
High Also affects org.elasticsearch:elasticsearch
GHSA-5xm9-x7x4-4j5x
Elasticsearch Vulnerable to Stack Overflow due to a Large Recursion
High Also affects org.elasticsearch:elasticsearch
GHSA-jgx4-7v3v-vwfm
Elasticsearch allocation of resources without limits or throttling leads to crash
High Also affects org.elasticsearch:elasticsearch
GHSA-5mpw-4546-2wcr
Elasticsearch Incorrect Authorization vulnerability
Medium Also affects org.elasticsearch:elasticsearch
GHSA-5v8f-xx9m-wj44
Elasticsearch stores private key on disk unencrypted
High Also affects org.elasticsearch:elasticsearch
GHSA-4q22-422g-m4pj
Elasticsearch StackOverflow vulnerability
Medium Also affects org.elasticsearch:elasticsearch
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor