Bug 1552117 (CVE-2018-3819) - CVE-2018-3819 kibana: open redirect on the login page
Summary: CVE-2018-3819 kibana: open redirect on the login page
Alias: CVE-2018-3819
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1566704
Blocks: 1552125
TreeView+ depends on / blocked
Reported: 2018-03-06 14:23 UTC by Laura Pardo
Modified: 2021-10-21 19:56 UTC (History)
22 users (show)

Fixed In Version: kibana 6.1.3, kibana 5.6.7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-10-21 19:56:43 UTC

Attachments (Terms of Use)

Description Laura Pardo 2018-03-06 14:23:13 UTC
A flaw was found in Kibana versions before 6.1.3 and 5.6.7. The fix in Kibana for ESA-2017-23 was incomplete. With X-Pack security enabled, there is an open redirect vulnerability on the login page that would enable an attacker to craft a link that redirects to an arbitrary website.


Comment 4 Jeff Cantrill 2018-04-24 17:12:42 UTC
Not a bug.  Openshift does not ship xpack as part of the kibana image.

Comment 5 Kurt Seifried 2018-04-25 16:43:39 UTC
(In reply to Jeff Cantrill from comment #4)
> Not a bug.  Openshift does not ship xpack as part of the kibana image.

Sorry not sure what the needinfo is for?

As far as security trackers go, the low/moderate are largely up to the product team to fix if they want to, or if they catch it on a rebase due to a later upgrade. For important and critical PS will poke you. For details on the changes to the RHSA process please see:


Comment 6 Andrej Nemec 2018-05-14 15:23:40 UTC

This issue affects the versions of kibana as shipped with Red Hat OpenShift Enterprise Linux. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

Note You need to log in before you can comment on or make changes to this bug.