Back to vendor advisories
Microsoft Security Response CenterCVE-2023-49921

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.

Mariner

5.2CVSS out of 10Medium severity
Scope

What the vendor says is affected

  • cbl2 rubygem-elasticsearch 8.3.0-1
  • azl3 rubygem-elasticsearch 8.9.0-1 on Azure Linux 3.0
  • cbl2 rubygem-elasticsearch 8.3.0-1 on CBL-Mariner 2.0
Timeline

When this advisory changed

  1. Published by Microsoft Security Response Center

    The publication date reported by the vendor.

  2. Added to SecurityAlert

    We collected the advisory from the official source.

  3. Confirmed at the source

    Our collector saw this advisory during a later source check.

Vulnerabilities

CVEs named in this advisory