First published: Wed Dec 13 2023(Updated: )
An issue was discovered by Elastic whereby sensitive information may be recorded in Kibana logs in the event of an error or in the event where debug level logging is enabled in Kibana. Elastic has released Kibana 8.11.2 which resolves this issue. The messages recorded in the log may contain Account credentials for the kibana_system user, API Keys, and credentials of Kibana end-users, Elastic Security package policy objects which can contain private keys, bearer token, and sessions of 3rd-party integrations and finally Authorization headers, client secrets, local file paths, and stack traces. The issue may occur in any Kibana instance running an affected version that could potentially receive an unexpected error when communicating to Elasticsearch causing it to include sensitive data into Kibana error logs. It could also occur under specific circumstances when debug level logging is enabled in Kibana. Note: It was found that the fix for ESA-2023-25 in Kibana 8.11.1 for a similar issue was incomplete.
Credit: bressers@elastic.co
Affected Software | Affected Version | How to fix |
---|---|---|
Elastic | >=7.13.0<7.17.16 | |
Elastic | >=8.0.0<8.11.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-46675 has been classified with a severity rating that indicates a risk of sensitive information exposure due to logging practices in Kibana.
To mitigate CVE-2023-46675, users should upgrade to Kibana version 8.11.2 or later.
CVE-2023-46675 affects Kibana versions from 7.13.0 to 7.17.16 and versions from 8.0.0 to 8.11.1.
CVE-2023-46675 may lead to the exposure of sensitive information being recorded in Kibana logs during errors or when debug logging is enabled.
CVE-2023-46675 was discovered by the security team at Elastic.