1 results (0.002 seconds)

CVSS: 6.8EPSS: 0%CPEs: 2EXPL: 0

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 8.11.3 and 7.17.16 that prevents this issue by limiting these types of logs to DEBUG level logging, which is disabled by default. Elastic descubrió un problema por el cual Beats y Elastic Agent registraban un evento sin procesar en sus propios registros en el nivel WARN o ERROR si fallaba la ingesta de ese evento en Elasticsearch con cualquier código de estado HTTP 4xx excepto 409 o 429. Dependiendo de la naturaleza del en caso de que Beats o Elastic Agent intentaran ingerir, esto podría dar lugar a la inserción de información confidencial o privada en los registros de Beats o Elastic Agent. • https://discuss.elastic.co/t/beats-and-elastic-agent-8-11-3-7-17-16-security-update-esa-2023-30/349180 • CWE-532: Insertion of Sensitive Information into Log File •