Back to bug 2066386
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Patrick Del Bello | 2022-03-21 16:12:04 UTC | Blocks | 2066389 | |
| Anten Skrabec | 2022-04-05 23:06:08 UTC | Depends On | 2072288, 2072291, 2072290, 2072289, 2072287, 2072286 | |
| Anten Skrabec | 2022-04-05 23:09:24 UTC | Depends On | 2072296 | |
| Anten Skrabec | 2022-04-07 19:17:13 UTC | Doc Text | A flaw was found in the upgrade assistant for elasticsearch 7.17.0. When upgrading from version 6.x to 7.x, the built-in protections on the security infex would be disabled, possibly allowing authenticated users to access the index. | |
| Anten Skrabec | 2022-04-07 19:21:11 UTC | Doc Text | A flaw was found in the upgrade assistant for elasticsearch 7.17.0. When upgrading from version 6.x to 7.x, the built-in protections on the security infex would be disabled, possibly allowing authenticated users to access the index. | A flaw was discovered in Kibana which allows users with Read access to the Uptime feature to modify alerting rules, allowing them to create new or overwrite existing ones. However any rules created this way would not be enabled by default, allowing a user to disable an existing, enabled alert rule. |
| RaTasha Tillery-Smith | 2022-04-08 12:46:04 UTC | Doc Text | A flaw was discovered in Kibana which allows users with Read access to the Uptime feature to modify alerting rules, allowing them to create new or overwrite existing ones. However any rules created this way would not be enabled by default, allowing a user to disable an existing, enabled alert rule. | A flaw was found in Kibana. This issue allows users with read access to the Uptime feature to modify alerting rules, allowing them to create new or overwrite existing ones. However, any rules created this way are not enabled by default and allow the user to disable an existing, enabled alert rule. |
| Red Hat Bugzilla | 2022-04-19 04:38:56 UTC | CC | ggaughan | |
| Red Hat Bugzilla | 2023-05-15 18:09:22 UTC | CC | drieden | |
| Red Hat Bugzilla | 2023-07-07 08:34:13 UTC | Assignee | security-response-team | nobody |
Back to bug 2066386