# CVE-2017-8452: Denial of service in Kibana

> Attackers can cause Kibana to crash by exhausting file descriptors in SSL-enabled configurations, requiring an upgrade to fix.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-p36j-6ff2-h5mm

## What is CVE-2017-8452?

CVE-2017-8452 is a high-severity denial of service vulnerability in Elastic Kibana, published on 16 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Kibana versions prior to 5.2.1 configured for SSL client access, file descriptors will fail to be cleaned up after certain requests and will accumulate over time until the process crashes.

Weakness: CWE-769 (DEPRECATED: Uncontrolled File Descriptor Consumption), CWE-775 (Missing Release of File Descriptor or Handle after Effective Lifetime)

## Which versions are affected by CVE-2017-8452?

It affects 1 product.


Products: Elastic Kibana.

## How do I fix CVE-2017-8452?

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

## Is CVE-2017-8452 being exploited?

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

What it is: CVE-2017-8452 is a high-severity denial of service vulnerability in Elastic Kibana, published on 16 Jun 2017. 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-2017-8452 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-2017-8452/ (Markdown: https://insights.sbomify.com/CVE-2017-8452/index.md)
```

## Sources

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

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