PT-2019-16737 · Kubernetes · Kube-Rbac-Proxy

Published 2019-02-05 · Updated 2021-05-21 · CVE-2019-3818

Positive Technologies (AI Summary)

CVSS v3.1

7.5

High

Base vector

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

Name of the Vulnerable Software and Affected Versions kube-rbac-proxy versions prior to 0.4.1

Description The issue allows for the use of insecure ciphers and TLS 1.0, as the kube-rbac-proxy container does not honor TLS configurations. This could enable an attacker to target traffic sent over a TLS connection with a weak configuration and potentially break the encryption.

Recommendations For versions prior to 0.4.1, update to version 0.4.1 or later to resolve the issue. As a temporary workaround, consider disabling the use of insecure ciphers and TLS 1.0 in the TLS configuration until a patch is available. Restrict access to the kube-rbac-proxy container to minimize the risk of exploitation.

Fix

Use of a Broken Cryptographic Algorithm

Weakness Enumeration

CWE-327

Related Identifiers

CVE-2019-3818

Affected Products

Kube-Rbac-Proxy

References · 7

• https://osv.dev/vulnerability/CVE-2019-3818 · Vendor Advisory
• https://access.redhat.com/errata/RHBA-2019:0327 · Vendor Advisory
• https://access.redhat.com/security/cve/CVE-2019-3818 · Vendor Advisory
• https://nvd.nist.gov/vuln/detail/CVE-2019-3818 · Security Note
• https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-3818 · Vendor Advisory
• http://securityfocus.com/bid/106744 · Note
• https://t.me/cvenotify/14803 · Telegram Post