Bug 1668961 (CVE-2019-3818) - CVE-2019-3818 kube-rbac-proxy: Improper application of config allows for insecure ciphers and TLS 1.0
Summary: CVE-2019-3818 kube-rbac-proxy: Improper application of config allows for inse...
Status: NEW
Alias: CVE-2019-3818
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard: impact=low,public=20190125,reported=2...
Keywords: Security
Depends On: 1669379 1669378
Blocks: 1668962
TreeView+ depends on / blocked
 
Reported: 2019-01-24 01:13 UTC by Sam Fowler
Modified: 2019-06-08 23:49 UTC (History)
10 users (show)

(edit)
The kube-rbac-proxy container, as used in Red Hat OpenShift Container Platform, does not honor TLS configurations allowing for the 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 of the data stream.
Clone Of:
(edit)
Last Closed:


Attachments (Terms of Use)

Description Sam Fowler 2019-01-24 01:13:01 UTC
The kube-rbac-proxy container as used in Red Hat OpenShift Container Platform does not honour TLS configurations, allowing for use of insecure ciphers and TLS 1.0. An attacker could potentially target a weak TLS configuration via a man-in-the-middle attack to discover sensitive information.

The fix for this issue properly applies the configured TLS settings and makes TLS 1.2 the default.

Comment 1 Sam Fowler 2019-01-24 01:19:42 UTC
Patch:

https://github.com/brancz/kube-rbac-proxy/pull/27/files

Comment 2 Sam Fowler 2019-01-25 04:14:34 UTC
Acknowledgments:

Name: Frederic Branczyk (Red Hat), Matthias Loibl (Red Hat), Max Inden (Red Hat)

Comment 4 Sam Fowler 2019-04-24 01:15:53 UTC
This issue has been addressed in the following products:

  Red Hat OpenShift Container Platform 3.11

Via RHBA-2019:0327 https://access.redhat.com/errata/RHBA-2019:0327


Note You need to log in before you can comment on or make changes to this bug.