Skip to main content

Insertion of Sensitive Information into Log File

CVE-2023-49922

Medium
6.5/10

Summary

An issue was discovered by Elastic whereby Beats and Elastic Agent would log a raw event in its own logs at the WARN or ERROR level if ingesting that event to Elasticsearch failed with any 4xx HTTP status code except 409 or 429. Depending on the nature of the event that Beats or Elastic Agent attempted to ingest, this could lead to the insertion of sensitive or private information in the Beats or Elastic Agent logs. Elastic has released a fix that prevents this issue by limiting these types of logs to DEBUG level logging, which is disabled by default. This affects github.com/elastic/beats versions 7.0.x prior to 7.17.16 and 8.0.x prior to 8.11.3.

  • 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