CVE-2020-27816: Medium severity elastic vulnerability

Published Nov 30, 2020
·
Updated

In the OpenShift Container Platform 4.x the kibana logging console might be manipulated or even completely damaged by any user who create kibana resource in a non openshift-logging namespace. Due to that the console links is recreated by the elasticsearch-operator based on the new CR. If the new kibana resource is removed then the openshift-logging console link does not back to the original one but completely is lost.

This flaw could lead to an arbitrary URL redirection or the openshift-logging console link full damage.

Other sources

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.

MITRE

Affected Software

3 affected componentsFixes available
redhat/elasticsearch-operator-container<4.7
4.7
Elastic Kibana<=4.7
redhat OpenShift Container Platform=4.0

Event History

Dec 2, 2020
CVE Published
via MITRE·12:54 AM
Data Sourced
via MITRE·12:54 AM
DescriptionWeakness

Frequently Asked Questions

1

What is CVE-2020-27816?

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.

2

What is the severity of CVE-2020-27816?

CVE-2020-27816 has a severity value of 6.1, which is considered medium.

3

How does CVE-2020-27816 impact the elasticsearch-operator?

CVE-2020-27816 allows an attacker to replace the original openshift-logging console link with a different one, posing a potential security risk.

4

How can I mitigate CVE-2020-27816?

To mitigate CVE-2020-27816, ensure that the elasticsearch-operator validates the namespace where the kibana logging resource is created.

5

Where can I find more information about CVE-2020-27816?

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).

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203