CVE-2019-3818
Last modified
CVE-2019-3818 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. 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.. EPSS estimates a 0.66% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Kube-Rbac-Proxy Project | Kube-Rbac-Proxy | < 0.4.1 |
| Redhat | Openshift Container Platform | 3.11 |
References
- http://www.securityfocus.com/bid/106744Third Party Advisory, VDB Entry
- https://access.redhat.com/errata/RHBA-2019:0327Vendor Advisory
- https://access.redhat.com/security/cve/CVE-2019-3818Vendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-3818Issue Tracking, Patch, Vendor Advisory
- http://www.securityfocus.com/bid/106744Third Party Advisory, VDB Entry
- https://access.redhat.com/errata/RHBA-2019:0327Vendor Advisory
- https://access.redhat.com/security/cve/CVE-2019-3818Vendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-3818Issue Tracking, Patch, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2019-3818?
How severe is CVE-2019-3818?
How do I fix CVE-2019-3818?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2019
- CVE-2019-3812QEMU, through version 2.10 and through version 3.1.0, is vul…4.4
- CVE-2019-3813Spice, versions 0.5.2 through 0.14.1, are vulnerable to an o…7.5
- CVE-2019-3814It was discovered that Dovecot before versions 2.2.36.1 and …7.7
- CVE-2019-3815A memory leak was discovered in the backport of fixes for CV…3.3
- CVE-2019-3816Openwsman, versions up to and including 2.6.9, are vulnerabl…7.5
- CVE-2019-3817A use-after-free flaw has been discovered in libcomps before…7.5
- CVE-2019-3819A flaw was found in the Linux kernel in the function hid_deb…4.4
- CVE-2019-3820It was discovered that the gnome-shell lock screen since ver…4.3
- CVE-2019-3821A flaw was found in the way civetweb frontend was handling r…7.5
- CVE-2019-3822libcurl versions from 7.36.0 to before 7.64.0 are vulnerable…9.8
- CVE-2019-3823libcurl versions from 7.34.0 to before 7.64.0 are vulnerable…4.3
- CVE-2019-3824A flaw was found in the way an LDAP search expression could …
Are you affected by CVE-2019-3818?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
