# CVE-2022-23711: Information disclosure in kibana

> Unauthenticated attackers can view sensitive Elastic Stack monitoring data in Kibana page source if specific optional monitoring settings are enabled.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Apr 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-83v8-h997-4xf4

## What is CVE-2022-23711?

CVE-2022-23711 is a medium-severity vulnerability in Elastic Kibana, published on 21 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in Kibana could expose sensitive information related to Elastic Stack monitoring in the Kibana page source. Elastic Stack monitoring features provide a way to keep a pulse on the health and performance of your Elasticsearch cluster. Authentication with a vulnerable Kibana instance is not required to view the exposed information. The Elastic Stack monitoring exposure only impacts users that have set any of the optional monitoring.ui.elasticsearch.* settings in order to configure Kibana as a remote UI for Elastic Stack Monitoring. The same vulnerability in Kibana could expose other non-sensitive application-internal information in the page source.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2022-23711?

It affects 1 product.


Products: Elastic Kibana.

## How do I fix CVE-2022-23711?

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

## Is CVE-2022-23711 being exploited?

There is no known exploitation of CVE-2022-23711 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-2022-23711 and fix it if it is affected.

What it is: CVE-2022-23711 is a medium-severity vulnerability in Elastic Kibana, published on 21 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-23711 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-2022-23711/ (Markdown: https://insights.sbomify.com/CVE-2022-23711/index.md)
```

## Sources

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

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