Skip to content
Fencer Vulns
medium 4.8

CVE-2020-7016 json

Kibana versions before 6.8.11 and 7.8.1 contain a denial of service (DoS) flaw in Timelion.

published 2020-07-27 6 y ago modified 2026-09-08 2 mo ago also BIT-elk-2020-7016 , BIT-kibana-2020-7016 , EUVD-2020-28153

cvss
4.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.1%
EPSS 1.1% chance of exploitation in 30 days, percentile 65%
public exploits
0
none known

Summary

Kibana versions before 6.8.11 and 7.8.1 contain a denial of service (DoS) flaw in Timelion. An attacker can construct a URL that when viewed by a Kibana user can lead to the Kibana process consuming large amounts of CPU and becoming unresponsive.

Patch / fix

  • bitnami elk 6.8.11, 7.8.1
  • bitnami kibana 6.8.11, 7.8.1
  • elasticsearch kibana 6.8.11, 7.8.1

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-2020-7016 updated cvss 4.8

kibana: DoS in Timelion

  • Red Hat OpenShift Container Platform 3.11 kibana
    affected: no fix available “Fix deferred”
  • Red Hat OpenShift Container Platform 4 kibana, openshift4/ose-logging-kibana6
    affected: no fix available, no fix planned “Will not fix”

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.08% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 4.8 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:H
NVD 2.0 2.1 AV:N/AC:H/Au:S/C:N/I:N/A:P
OSV 3.1 4.8 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
bitnami elk
<6.8.11
>=7.0.0, <7.8.1
6.8.11
7.8.1
bitnami kibana
<6.8.11
>=7.0.0, <7.8.1
6.8.11
7.8.1

Affected products

  • Elastic Kibana

Classification

Weakness
  • CWE-185 Incorrect Regular Expression
  • CWE-400 Uncontrolled Resource Consumption

References

Sources

Fencer Vulns 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.