CVE-2020-27816

MEDIUMCVSS 6.1/10EPSS 0.64%

Last modified

CVE-2020-27816 is a medium-severity vulnerability rated 6.1/10 on the CVSS scale. 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. EPSS estimates a 0.64% chance of exploitation in the next 30 days.

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.

Metrics

CVSS 3.1
6.1/10

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

EPSS Probability
0.64%

46.2th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
ElasticKibana<= 4.7
RedhatOpenshift Container Platform4.0

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2020-27816?
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.
How severe is CVE-2020-27816?
CVE-2020-27816 has a CVSS score of 6.1/10 (MEDIUM severity). The EPSS model estimates a 0.64% probability of exploitation in the next 30 days.
How do I fix CVE-2020-27816?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2020-27816?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST