Skip to content
Fencer Vulns
medium 6.1

CVE-2017-11482 json

The Kibana fix for CVE-2017-8451 was found to be incomplete.

published 2017-12-08 8 y ago modified 2026-06-17 4 mo ago also EUVD-2017-3100

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

Summary

The Kibana fix for CVE-2017-8451 was found to be incomplete. With X-Pack installed, Kibana versions before 6.0.1 and 5.6.5 have an open redirect vulnerability on the login page that would enable an attacker to craft a link that redirects to an arbitrary website.

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-11482 updated cvss 6.1

kibana: open redirect on the login page (ESA-2017-23)

  • Red Hat OpenShift Enterprise 3 kibana
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux OpenStack Platform 7 (Kilo) Operational Tools kibana Red Hat JBoss Fuse 6 hawtio-kibana hawtio-kibana Red Hat OpenStack Platform 8 (Liberty) Operational Tools kibana Red Hat OpenStack Platform 9 (Mitaka) Operational Tools kibana Red Hat OpenStack Platform 10 (Newton) puppet-kibana3 Red Hat OpenStack Platform 11 (Ocata) puppet-kibana3
    +1 more products
    Red Hat OpenStack Platform 12 (Pike) puppet-kibana3
    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

0.74% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.0 6.1 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
NVD 2.0 5.8 AV:N/AC:M/Au:N/C:P/I:P/A:N

Affected products

  • Elastic Kibana

Classification

Weakness
  • CWE-601 URL Redirection to Untrusted Site

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.