What is the severity of CVE-2019-3818?

CVE-2019-3818 is classified as a moderate severity vulnerability due to its potential impact on TLS security.

How do I fix CVE-2019-3818?

To fix CVE-2019-3818, upgrade the kube-rbac-proxy to version 0.4.1 or later to ensure TLS configurations are correctly honored.

What versions are affected by CVE-2019-3818?

CVE-2019-3818 affects kube-rbac-proxy versions prior to 0.4.1 and Red Hat OpenShift Container Platform version 3.11.

What impact does CVE-2019-3818 have on TLS connections?

CVE-2019-3818 allows the use of insecure ciphers and TLS 1.0, which can lead to potential compromise of encrypted traffic.

Is CVE-2019-3818 a local or remote attack vector?

CVE-2019-3818 can be exploited through a remote attack vector if an attacker targets the weak TLS configuration.

Vulnerability/
CVE-2019-3818

high

7.5

CWE

327

5/2/2019

21/11/2024

CVE-2019-3818

First published: Tue Feb 05 2019(Updated: )

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.

Credit: secalert@redhat.com secalert@redhat.com

Affected Software	Affected Version	How to fix
Kube-rbac-proxy	<0.4.1
redhat openshift container platform	=3.11

Remedy

https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-3818

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-3818?
CVE-2019-3818 is classified as a moderate severity vulnerability due to its potential impact on TLS security.
How do I fix CVE-2019-3818?
To fix CVE-2019-3818, upgrade the kube-rbac-proxy to version 0.4.1 or later to ensure TLS configurations are correctly honored.
What versions are affected by CVE-2019-3818?
CVE-2019-3818 affects kube-rbac-proxy versions prior to 0.4.1 and Red Hat OpenShift Container Platform version 3.11.
What impact does CVE-2019-3818 have on TLS connections?
CVE-2019-3818 allows the use of insecure ciphers and TLS 1.0, which can lead to potential compromise of encrypted traffic.
Is CVE-2019-3818 a local or remote attack vector?
CVE-2019-3818 can be exploited through a remote attack vector if an attacker targets the weak TLS configuration.

agent/references
agent/type
collector/mitre-cve
source/MITRE
agent/severity
agent/weakness
agent/description
agent/first-publish-date
agent/remedy
agent/author
agent/last-modified-date
agent/event
agent/softwarecombine
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
collector/nvd-api
source/NVD
agent/software-canonical-lookup
vendor/kube-rbac-proxy project
canonical/kube-rbac-proxy
vendor/redhat
canonical/redhat openshift container platform
version/redhat openshift container platform/3.11

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.