Skip to main content

Insertion of Sensitive Information into Log File

CVE-2023-49921

Medium
6.5/10

Summary

An issue was discovered by Elastic whereby Watcher search input logged the search query results on the DEBUG log level. This could lead to the raw contents of documents stored in Elasticsearch being printed in logs. Elastic 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. This issue affects org.elasticsearch:elasticsearch versions 7.0.0-alpha1 through 7.17.15, and 8.0.0-alpha1 through 8.11.1.

  • LOW
  • NETWORK
  • NONE
  • UNCHANGED
  • NONE
  • LOW
  • HIGH
  • NONE

CWE-532 - Insertion of Sensitive Information into Log File

It's quite common for applications to save logs. For example, whenever a user requests a resource from a particular website, the web server writes information about the request to a log file. These files are helpful for identifying abnormal system activity, bugs, and evaluating the security controls of the application. Security of log files is critical for the overall security of the application and its confidential resources. An application that lacks appropriate logging levels can expose sensitive user data and system information stored on the log files to malicious users. This info can be exploited to compromise your system.

References

Advisory Timeline

  • Published