CVE-2019-3818

Description

The kube-rbac-proxy container before version 0.4.1 as used in Red Hat OpenShift Container Platform does not honor TLS configurations, allowing for use of insecure ciphers and TLS 1.0. An attacker could target traffic sent over a TLS connection with a weak configuration and potentially break the encryption.

References

Link	Tags
https://access.redhat.com/security/cve/CVE-2019-3818	vendor advisory
http://www.securityfocus.com/bid/106744	third party advisory vdb entry
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-3818	patch vendor advisory issue tracking
https://access.redhat.com/errata/RHBA-2019:0327	vendor advisory

Frequently Asked Questions

What is the severity of CVE-2019-3818?: CVE-2019-3818 has been scored as a high severity vulnerability.
How to fix CVE-2019-3818?: To fix CVE-2019-3818, 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-2019-3818 being actively exploited in the wild?: As for now, there are no information to confirm that CVE-2019-3818 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-2019-3818?: CVE-2019-3818 affects [UNKNOWN] kube-rbac-proxy.

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.

Description

Category

CWE-327 – Use of a Broken or Risky Cryptographic Algorithm

References

Frequently Asked Questions