Elastic Kibana

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 Entity Store Leading to Unauthorized API Key Creation

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

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

Incorrect Authorization in Kibana Fleet Leading to Information Disclosure

Missing Authorization in Kibana Leading to Information Disclosure

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

Incorrect Authorization in Kibana Leading to Unauthorized Disabling of Privilege Monitoring

Incorrect Authorization in Kibana Leading to Machine Learning Audit Log Integrity Compromise

Missing Authorization in Kibana Leading to Unauthorized Modification of Machine Learning Trained Model Space Assignments

Kibana server-side request forgery

Kibana Improper Authorization

Kibana Origin Validation Error

Kibana Improper Authorization

Incorrect Authorization in Kibana Leading to Unauthorized Disclosure, Modification, and Deletion of Data

Authorization Bypass Through User-Controlled Key in Kibana Leading to Unauthorized Data Modification in Kibana

It was discovered that Kibana’s JIRA connector & IBM Resilient connector could be used to return HTTP response data on internal hosts, which may be intentionally hidden from public view. Using this vulnerability, a malicious user with the ability to create connectors, could utilize these connectors to view limited HTTP response data on hosts accessible to the cluster.

In Kibana versions before 7.12.0 and 6.8.15 a flaw in the session timeout was discovered where the xpack.security.session.idleTimeout setting is not being respected. This was caused by background polling activities unintentionally extending authenticated users sessions, preventing a user session from timing out.