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

> Attackers with log access can view sensitive credentials and metadata in Kibana logs when specific JSON or pattern layouts are configured.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Oct 2023
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-7rvg-gjgp-95j7

## What is CVE-2023-31422?

CVE-2023-31422 is a critical vulnerability in Elastic Kibana, published on 26 Oct 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered by Elastic whereby sensitive information is recorded in Kibana logs in the event of an error. The issue impacts only Kibana version 8.10.0 when logging in the JSON layout or when the pattern layout is configured to log the %meta pattern. Elastic has released Kibana 8.10.1 which resolves this issue. The error object recorded in the log contains request information, which can include sensitive data, such as authentication credentials, cookies, authorization headers, query params, request paths, and other metadata. Some examples of sensitive data which can be included in the logs are account credentials for kibana_system, kibana-metricbeat, or Kibana end-users.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2023-31422?

It affects 1 product.


Products: Elastic Kibana.

## How do I fix CVE-2023-31422?

No fix has been published for CVE-2023-31422 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-31422 being exploited?

There is no known exploitation of CVE-2023-31422 in the wild and no public exploit code.

## Other vulnerabilities in Elastic Kibana

- [CVE-2019-7609](https://insights.sbomify.com/CVE-2019-7609/): Kibana Arbitrary Code Execution (critical 9.8, exploited in the wild)
- [CVE-2025-25015](https://insights.sbomify.com/CVE-2025-25015/): Kibana arbitrary code execution via prototype pollution (critical 9.9)
- [CVE-2024-37288](https://insights.sbomify.com/CVE-2024-37288/): Deserialization in Kibana (critical 9.9)
- [CVE-2023-31415](https://insights.sbomify.com/CVE-2023-31415/): Code injection in Kibana (critical 9.9)
- [CVE-2018-17245](https://insights.sbomify.com/CVE-2018-17245/): Information disclosure in Kibana (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-31422 and fix it if it is affected.

What it is: CVE-2023-31422 is a critical vulnerability in Elastic Kibana, published on 26 Oct 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-31422 in the wild and no public exploit code.

Affected product: Elastic Kibana. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-31422/ (Markdown: https://insights.sbomify.com/CVE-2023-31422/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-31422
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-31422
- OSV: https://osv.dev/vulnerability/CVE-2023-31422

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-31422/
Summaries are generated and may contain mistakes; the official description above is the record.