An issue was identified by Elastic whereby sensitive information is recorded in Logstash logs under specific circumstances.
The prerequisites for the manifestation of this issue are:
* Logstash is configured to log in JSON format https://www.elastic.co/guide/en/logstash/current/running-logstash-command-line.html , which is not the default logging format.
* Sensitive data is stored in the Logstash keystore and referenced as a variable in Logstash configuration.
Metrics
Affected Vendors & Products
References
History
Thu, 13 Feb 2025 17:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | An issue was identified by Elastic whereby sensitive information is recorded in Logstash logs under specific circumstances. The prerequisites for the manifestation of this issue are: * Logstash is configured to log in JSON format https://www.elastic.co/guide/en/logstash/current/running-logstash-command-line.html , which is not the default logging format. * Sensitive data is stored in the Logstash keystore and referenced as a variable in Logstash configuration. | An issue was identified by Elastic whereby sensitive information is recorded in Logstash logs under specific circumstances. The prerequisites for the manifestation of this issue are: * Logstash is configured to log in JSON format https://www.elastic.co/guide/en/logstash/current/running-logstash-command-line.html , which is not the default logging format. * Sensitive data is stored in the Logstash keystore and referenced as a variable in Logstash configuration. |

Status: PUBLISHED
Assigner: elastic
Published: 2023-11-15T08:05:26.561Z
Updated: 2025-02-13T17:14:31.789Z
Reserved: 2023-10-24T17:28:32.186Z
Link: CVE-2023-46672

No data.

Status : Modified
Published: 2023-11-15T08:15:07.907
Modified: 2025-02-13T18:15:36.440
Link: CVE-2023-46672

No data.