Skip to content
Fencer Vulns
low 3.7

CVE-2019-3818 json

The kube-rbac-proxy container before version 0.4.1 as used in Red Hat OpenShift Container Platform does not honor TLS configurations, allow…

published 2019-02-05 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-13441

cvss
3.7
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 51%
public exploits
0
none known

Summary

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.

Patch / fix

  • kube-rbac-proxy_project kube-rbac-proxy 0.4.1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-3818 updated cvss 3.7

kube-rbac-proxy: Improper application of config allows for insecure ciphers and TLS 1.0

  • Red Hat OpenShift Container Platform 3.11 openshift3/ose v3.11.82-3, openshift3/node v3.11.82-3, openshift3/grafana v3.11.82-3, openshift3/ose-cli v3.11.82-3, openshift3/ose-pod v3.11.82-3, openshift3/apb-base v3.11.82-6, +73 more
    fixed: vendor fix RHBA-2019:0327
  • Red Hat OpenShift Container Platform 4 openshift4/ose-kube-rbac-proxy
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.66% chance of exploitation in the next 30 days, higher than 51% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.0 3.7 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N

Affected products

  • [UNKNOWN] kube-rbac-proxy

Classification

Weakness
  • CWE-327 Use of a Broken or Risky Cryptographic Algorithm

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.