Skip to main content

Insertion of Sensitive Information into Log File


Severity Medium
Score 4.4/10


Elasticsearch generally filters out sensitive information and credentials before logging to the audit log. It was found that this filtering was not applied in versions 7.0.0 through 7.17.12, and 8.0.0 through 8.9.1, when requests to Elasticsearch use certain deprecated URIs for APIs. The impact of this flaw is that sensitive information such as passwords and tokens might be printed in cleartext in Elasticsearch audit logs. Note that audit logging is disabled by default and needs to be explicitly enabled and even when audit logging is enabled, request bodies that could contain sensitive information are not printed to the audit log unless explicitly configured.

  • LOW
  • NONE
  • NONE
  • HIGH
  • 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.

Advisory Timeline

  • Published