CVE-2019-3818

7.5 HIGH 0.7% exploit odds Fix listed

What it is

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.

At a glance

Exploitability: Can be exploited over the network without logging in. High risk of data exposure.
Exploit odds: 0.7% chance of exploitation in the next 30 days (EPSS).
Fix: A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

2019-02-05 17:29 UTC PublishedDisclosed publicly on CVE.org and NVD
2026-06-17 02:35 UTC Last updatedMost recent change to the record

Why it ranks here

Exploited in the wild: no, CISA does not list it.
Exploit odds: 0.7% in the next 30 days (EPSS).
Severity: 7.5 HIGH (CVSS).
Fix: a patch or advisory is linked.

Details

Published: 2019-02-05 17:29 UTC
Last modified: 2026-06-17 02:35 UTC
Exploit probability: 0.7% · EPSS, next 30 days
Weakness: CWE-327 · Broken cryptographic algorithm
Record status: Modified

Affected

kube-rbac-proxy Project kube-rbac-proxy < 0.4.1
Redhat Openshift Container Platform 3.11

Attack profile CVSS 3.1 · 7.5

Attack vector: Network
Complexity: Low
Privileges needed: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2019-3818.md and follow it. Check whether this project is affected by CVE-2019-3818. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

· More options · Status badge

Download Square Reddit

Fix and advisories

References

NVD record · CVE.org record