First published: Mon Nov 30 2020(Updated: )
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.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/elasticsearch-operator-container | <4.7 | 4.7 |
Elastic Kibana | <=4.7 | |
Redhat Openshift Container Platform | =4.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-27816 is a vulnerability in the elasticsearch-operator that allows the replacement of the original openshift-logging console link with a different one.
CVE-2020-27816 has a severity value of 6.1, which is considered medium.
CVE-2020-27816 allows an attacker to replace the original openshift-logging console link with a different one, posing a potential security risk.
To mitigate CVE-2020-27816, ensure that the elasticsearch-operator validates the namespace where the kibana logging resource is created.
You can find more information about CVE-2020-27816 on the following sources: [Github PR #581](https://github.com/openshift/elasticsearch-operator/pull/581), [Github PR #587](https://github.com/openshift/elasticsearch-operator/pull/587), [Red Hat Security Advisory RHSA-2021:0310](https://access.redhat.com/errata/RHSA-2021:0310).