CVE-2020-27816

Description

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.

Category

6.1
CVSS
Severity: Medium
CVSS 3.1 •
CVSS 2.0 •
EPSS 0.17%
Third-Party Advisory redhat.com
Affected: n/a openshift-logging/console
Published at:
Updated at:

References

Link Tags
https://bugzilla.redhat.com/show_bug.cgi?id=1902698 third party advisory issue tracking

Frequently Asked Questions

What is the severity of CVE-2020-27816?
CVE-2020-27816 has been scored as a medium severity vulnerability.
How to fix CVE-2020-27816?
To fix CVE-2020-27816, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2020-27816 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2020-27816 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2020-27816?
CVE-2020-27816 affects n/a openshift-logging/console.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.