Skip to content
Fencer Intel
high 7.5

CVE-2017-8452 json

Kibana versions prior to 5.2.1 configured for SSL client access, file descriptors will fail to be cleaned up after certain requests and wil…

published 2017-06-16 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-17402

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.4%
EPSS 1.4% chance of exploitation in 30 days, percentile 72%
public exploits
0
none known

Summary

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.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-8452 updated cvss 5.3

kibana: Resource exhaustion via file descriptors clean up failure

  • Red Hat Enterprise Linux OpenStack Platform 7 (Kilo) Operational Tools kibana
    affected: no fix planned “Will not fix”
  • Red Hat OpenShift Enterprise 3 kibana
    affected: no fix available
  • Red Hat OpenStack Platform 8 (Liberty) Operational Tools kibana Red Hat OpenStack Platform 9 (Mitaka) Operational Tools kibana
    affected: no fix planned “Will not fix”
  • Red Hat OpenStack Platform 10 (Newton) Operational Tools kibana
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.38% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Affected products

  • Elastic Kibana

Classification

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

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.