A vulnerability, which was classified as critical, has been found in kube-rbac-proxy up to 0.4.0 (Firewall Software). This issue affects an unknown functionality of the component TLS Configuration Handler. The manipulation with an unknown input leads to a risky encryption vulnerability. Using CWE to declare the problem leads to CWE-327. The product uses a broken or risky cryptographic algorithm or protocol. Impacted is confidentiality, integrity, and availability. The summary by CVE 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.

The bug was discovered 02/04/2019. The weakness was published 02/05/2019 (Website). The advisory is shared at access.redhat.com. The identification of this vulnerability is CVE-2019-3818 since 01/03/2019. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1600 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k.

Upgrading to version 0.4.1 eliminates this vulnerability.

Productinfo

Type

• Firewall Software

Name

• kube-rbac-proxy

Version

• 0.1
• 0.2
• 0.3
• 0.4

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Discussion