kubernetes kube-rbac-proxy CVE-2019-3818 vulnerability in Kubernetes and Other Products
Published on February 5, 2019

product logo product logo product logo
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.

Vendor Advisory NVD

Weakness Type

Use of a Broken or Risky Cryptographic Algorithm

The use of a broken or risky cryptographic algorithm is an unnecessary risk that may result in the exposure of sensitive information. The use of a non-standard algorithm is dangerous because a determined attacker may be able to break the algorithm and compromise whatever data has been protected. Well-known techniques may exist to break the algorithm.


Products Associated with CVE-2019-3818

You can be notified by email with stack.watch whenever vulnerabilities like CVE-2019-3818 are published in these products:

Kubernetes Kube Rbac Proxy
 
Red Hat Openshift Container Platform
 
Kube Rbac Proxyproject Kube Rbac Proxy
 

Affected Versions

[UNKNOWN] kube-rbac-proxy Version 0.4.1 is affected by CVE-2019-3818

Exploit Probability

EPSS
0.08%
Percentile
22.46%

EPSS (Exploit Prediction Scoring System) scores estimate the probability that a vulnerability will be exploited in the wild within the next 30 days. The percentile shows you how this score compares to all other vulnerabilities.