Elastic Kibana any version

The elasticsearch-operator does not validate the namespace where kibana logging resource is created and due to that it is possible to replace the original openshift-logging console link (kibana console) to different one, created based on the new CR for the new kibana resource. This could lead to an arbitrary URL redirection or the openshift-logging console link damage. This flaw affects elasticsearch-operator-container versions before 4.7.

An open redirect flaw was found in Kibana versions before 7.13.0 and 6.8.16. If a logged in user visits a maliciously crafted URL, it could result in Kibana redirecting the user to an arbitrary website.

An open redirect issue was discovered in Kibana that could lead to a user being redirected to an arbitrary website if they use a maliciously crafted Kibana URL.

Kibana open redirect issue

Kibana Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Missing Authorization in Kibana Leading to Unauthorized Elasticsearch Index Data Exposure

Kibana versions before 6.8.9 and 7.7.0 contains a stored XSS flaw in the TSVB visualization. An attacker who is able to edit or create a TSVB visualization could allow the attacker to obtain sensitive information from, or perform destructive actions, on behalf of Kibana users who edit the TSVB visualization.

Kibana versions before 6.8.6 and 7.5.1 contain a cross site scripting (XSS) flaw in the coordinate and region map visualizations. An attacker with the ability to create coordinate map visualizations could create a malicious visualization. If another Kibana user views that visualization or a dashboard containing the visualization it could execute JavaScript in the victim�s browser.

An XSS vulnerability was found in Kibana index patterns. Using this vulnerability, an authenticated user with permissions to create index patterns can inject malicious javascript into the index pattern which could execute against other users

It was discovered that Kibana was not sanitizing document fields containing HTML snippets. Using this vulnerability, an attacker with the ability to write documents to an elasticsearch index could inject HTML. When the Discover app highlighted a search term containing the HTML, it would be rendered for the user.

Kibana Open Redirect

Kibana Unrestricted Upload of File with Dangerous Type Can Lead to XSS

Incorrect Authorization in Kibana Leading to Unauthorized Deletion of Synthetics Private Locations

Incorrect Authorization in Kibana Leading to Unauthorized Modification of Data

Incorrect Authorization in Kibana Leading to Unauthorized Cross-Space Exposure of Machine Learning Job Data

Improper Access Control in Kibana Leading to Unauthorized Data Modification and Information Disclosure

Improper Neutralization of Input During Web Page Generation in Kibana Leading to Stored HTML Injection

Kibana Cross-site Scripting via the Integration Package Upload Functionality

A vulnerability in Kibana could expose sensitive information related to Elastic Stack monitoring in the Kibana page source. Elastic Stack monitoring features provide a way to keep a pulse on the health and performance of your Elasticsearch cluster. Authentication with a vulnerable Kibana instance is not required to view the exposed information. The Elastic Stack monitoring exposure only impacts users that have set any of the optional monitoring.ui.elasticsearch.* settings in order to configure Kibana as a remote UI for Elastic Stack Monitoring. The same vulnerability in Kibana could expose other non-sensitive application-internal information in the page source.

Operation on a Resource after Expiration or Termination in Kibana Leading to Unauthorized File Access

Incomplete List of Disallowed Inputs in Kibana Leading to Server-Side Request Forgery

Kibana versions before 6.8.2 and 7.2.1 contain a server side request forgery (SSRF) flaw in the graphite integration for Timelion visualizer. An attacker with administrative Kibana access could set the timelion:graphite.url configuration option to an arbitrary URL. This could possibly lead to an attacker accessing external URL resources as the Kibana process on the host system.

A high-privileged user, allowed to create custom osquery packs 17 could affect the availability of Kibana by uploading a maliciously crafted osquery pack.

Insertion of Sensitive Information into Log File in Kibana Leading to Information Disclosure

It was discovered that on Windows operating systems specifically, Kibana was not validating a user supplied path, which would load .pbf files. Because of this, a malicious user could arbitrarily traverse the Kibana host to load internal files ending in the .pbf extension. Thanks to Dominic Couture for finding this vulnerability.

It was discovered that OpenShift Container Platform's (OCP) distribution of Kibana could open in an iframe, which made it possible to intercept and manipulate requests. This flaw allows an attacker to trick a user into performing arbitrary actions in OCP's distribution of Kibana, such as clickjacking.

Kibana path traversal issue

A flaw was discovered in Kibana in which users with Read access to the Uptime feature could modify alerting rules. A user with this privilege would be able to create new alerting rules or overwrite existing ones. However, any new or modified rules would not be enabled, and a user with this privilege could not modify alerting connectors. This effectively means that Read users could disable existing alerting rules.

Kibana Broken Access Control issue

Authorization Bypass Through User-Controlled Key in Kibana Leading to Information Disclosure

Missing Authorization in Kibana Leading to Unauthorized Information Disclosure

Kibana Unrestricted Upload of File

Observable Response Discrepancy in Kibana Leading to Cross-Space Information Disclosure

Improperly Controlled Modification of Dynamically-Determined Object Attributes in Kibana Leading to Unauthorized Data Modification

Uncaught Exception in Kibana Cases Leading to Denial of Service

Missing Authorization in Kibana Leading to Unauthorized Disclosure of Fleet Deployment Metadata

Missing Authorization in Kibana Entity Store Leading to Unauthorized API Key Creation

Incorrect Authorization in Kibana Fleet Leading to Information Disclosure

Authorization Bypass Through User-Controlled Key in Kibana Leading to Information Disclosure

Unintended Proxy or Intermediary ('Confused Deputy') in Kibana Leading to Unauthorized Information Exposure