# CVE-2022-38778: Denial of service in kibana

> An authenticated user can crash the Kibana server process via a flaw in a third-party dependency, causing denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Feb 2023
- **Updated:** 25 Mar 2025
- **Also known as:** GHSA-ph5g-2r58-hm46

## What is CVE-2022-38778?

CVE-2022-38778 is a medium-severity denial of service vulnerability in Elastic Kibana, published on 8 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw (CVE-2022-38900) was discovered in one of Kibana’s third party dependencies, that could allow an authenticated user to perform a request that crashes the Kibana server process.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 2 products.


Products: Decode-Uri-Component Project Decode-Uri-Component, Elastic Kibana.

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

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

## Is CVE-2022-38778 being exploited?

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

## Other vulnerabilities in Elastic Kibana

- [CVE-2022-38900](https://insights.sbomify.com/CVE-2022-38900/): decode-uri-component vulnerable to Denial of Service (DoS) (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-38778 and fix it if it is affected.

What it is: CVE-2022-38778 is a medium-severity denial of service vulnerability in Elastic Kibana, published on 8 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-38778 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-38778/ (Markdown: https://insights.sbomify.com/CVE-2022-38778/index.md)
```

## Sources

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

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