Logstash Insertion of Sensitive Information into Log File (ESA-2023-26)
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, which is not the default logging format.
-
Sensitive data is stored in the Logstash keystore and referenced as a variable in Logstash configuration.
Affected Versions:
Logstash versions on or after 8.10.0 and before 8.11.1
Solutions and Mitigations:
Users should upgrade to version 8.11.1.
Users that have run Logstash 8.10.x and 8.11.0 instances and have explicitly configured logging in JSON format, should review their logs for any potential sensitive data and if deemed necessary, perform follow up actions such as purging sensitive data from logs and rotating any potentially exposed credentials. The following, not exhaustive, list of strings can be used to search for logged events that might contain secrets:
-
LogStash::Util::SafeURI -
LogStash::Util::Password -
Elasticsearch pool URLs updated -
javaClass":"java.net.URI" -
'{"object":"http'
Severity:
CVSSv3: 8.4 (High) CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
CVE ID: CVE-2023-46672