Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2019-3818: The kube-rbac-proxy container before version 0.4.1 as used in Red Hat OpenShift Container Platform does not ho

49
This month
HIGH 7.5REMOTEWATCHLISTUPGRADEDOWNGRADE

CVE-2019-3818 is a high-severity flaw (CVSS 7.5) affecting kube-rbac-proxy, openshift container platform. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • High severity
  • Remotely exploitable, no login, no user action
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score7.5 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.7% (top 48%)
CISA exploited listNo
WeaknessCWE-327
Published2019-02-05
Last modified2026-06-17
Publisher (CNA): Red Hat, Inc. · Vendor: kube-rbac-proxy project · redhat

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

kube-rbac-proxy project kube-rbac-proxy UPGRADE
Affected: < 0.4.1
Fixed in: 0.4.1
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy kube-rbac-proxy || rpm -q kube-rbac-proxy || kube-rbac-proxy --version
2. UPGRADE to 0.4.1 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade kube-rbac-proxy
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade kube-rbac-proxy
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
redhat openshift container platform DOWNGRADE
Affected: 3.11
Fixed in: no fixed release known
Safe to downgrade to: a release before 3.11
1. Check installed version
apt-cache policy openshift-container-platform || rpm -q openshift-container-platform || openshift-container-platform --version
2. No fixed release: DOWNGRADE to a release before 3.11 (Debian / Ubuntu)
apt-cache madison openshift-container-platform sudo apt install openshift-container-platform=<VERSION_BEFORE_3.11> sudo apt-mark hold openshift-container-platform
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list openshift-container-platform sudo dnf downgrade openshift-container-platform-<VERSION_BEFORE_3.11> sudo dnf versionlock add openshift-container-platform
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-3818?

kube-rbac-proxy: upgrade to 0.4.1; openshift container platform: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2019-3818 being exploited?

CVE-2019-3818 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-3818 affect?

CVE-2019-3818 affects kube-rbac-proxy, openshift container platform. Severity is high (CVSS 7.5). 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 connect

How urgent is CVE-2019-3818?

Priority 49/100. High severity; Remotely exploitable, no login, no user action; On your watchlist

Software pages

Red Hat OpenShift vulnerabilities

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.