CVE-2019-3818: High severity kube-rbac-proxy vulnerability
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.
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2019-3818?
CVE-2019-3818 is classified as a moderate severity vulnerability due to its potential impact on TLS security.
How do I fix CVE-2019-3818?
To fix CVE-2019-3818, upgrade the kube-rbac-proxy to version 0.4.1 or later to ensure TLS configurations are correctly honored.
What versions are affected by CVE-2019-3818?
CVE-2019-3818 affects kube-rbac-proxy versions prior to 0.4.1 and Red Hat OpenShift Container Platform version 3.11.
What impact does CVE-2019-3818 have on TLS connections?
CVE-2019-3818 allows the use of insecure ciphers and TLS 1.0, which can lead to potential compromise of encrypted traffic.
Is CVE-2019-3818 a local or remote attack vector?
CVE-2019-3818 can be exploited through a remote attack vector if an attacker targets the weak TLS configuration.