RHSA-2020:2479: Moderate: OpenShift Container Platform 3.11 atomic-openshift security update
First published: Thu Jun 18 2020(Updated: )
OpenShift Enterprise by Red Hat is the company's cloud computing Platform-as-a-Service (PaaS) solution designed for on-premise or private cloud deployments. <br>Security Fix(es):<br><li> libseccomp-golang: mishandling of multiple argument rules leading to a bypass of intended access restrictions (CVE-2017-18367)</li> <li> kubernetes: Denial of service in API server via crafted YAML payloads by authorized users (CVE-2019-11254)</li> <li> kubernetes: Server side request forgery (SSRF) in kube-controller-manager allows users to leak secret information (CVE-2020-8555)</li> For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
| Affected Software | Affected Version | How to fix |
|---|---|---|
| redhat/atomic-openshift | <3.11.232-1.git.0.a5bc32f.el7 | 3.11.232-1.git.0.a5bc32f.el7 |
| redhat/atomic-openshift | <3.11.232-1.git.0.a5bc32f.el7 | 3.11.232-1.git.0.a5bc32f.el7 |
| redhat/atomic-openshift-clients | <3.11.232-1.git.0.a5bc32f.el7 | 3.11.232-1.git.0.a5bc32f.el7 |
| redhat/atomic-openshift-clients-redistributable | <3.11.232-1.git.0.a5bc32f.el7 | 3.11.232-1.git.0.a5bc32f.el7 |
| redhat/atomic-openshift-docker-excluder | <3.11.232-1.git.0.a5bc32f.el7 | 3.11.232-1.git.0.a5bc32f.el7 |
| redhat/atomic-openshift-excluder | <3.11.232-1.git.0.a5bc32f.el7 | 3.11.232-1.git.0.a5bc32f.el7 |
| redhat/atomic-openshift-hyperkube | <3.11.232-1.git.0.a5bc32f.el7 | 3.11.232-1.git.0.a5bc32f.el7 |
| redhat/atomic-openshift-hypershift | <3.11.232-1.git.0.a5bc32f.el7 | 3.11.232-1.git.0.a5bc32f.el7 |
| redhat/atomic-openshift-master | <3.11.232-1.git.0.a5bc32f.el7 | 3.11.232-1.git.0.a5bc32f.el7 |
| redhat/atomic-openshift-node | <3.11.232-1.git.0.a5bc32f.el7 | 3.11.232-1.git.0.a5bc32f.el7 |
| redhat/atomic-openshift-pod | <3.11.232-1.git.0.a5bc32f.el7 | 3.11.232-1.git.0.a5bc32f.el7 |
| redhat/atomic-openshift-sdn-ovs | <3.11.232-1.git.0.a5bc32f.el7 | 3.11.232-1.git.0.a5bc32f.el7 |
| redhat/atomic-openshift-template-service-broker | <3.11.232-1.git.0.a5bc32f.el7 | 3.11.232-1.git.0.a5bc32f.el7 |
| redhat/atomic-openshift-tests | <3.11.232-1.git.0.a5bc32f.el7 | 3.11.232-1.git.0.a5bc32f.el7 |
| redhat/atomic-openshift | <3.11.232-1.git.0.a5bc32f.el7 | 3.11.232-1.git.0.a5bc32f.el7 |
| redhat/atomic-openshift-clients | <3.11.232-1.git.0.a5bc32f.el7 | 3.11.232-1.git.0.a5bc32f.el7 |
| redhat/atomic-openshift-hyperkube | <3.11.232-1.git.0.a5bc32f.el7 | 3.11.232-1.git.0.a5bc32f.el7 |
| redhat/atomic-openshift-hypershift | <3.11.232-1.git.0.a5bc32f.el7 | 3.11.232-1.git.0.a5bc32f.el7 |
| redhat/atomic-openshift-master | <3.11.232-1.git.0.a5bc32f.el7 | 3.11.232-1.git.0.a5bc32f.el7 |
| redhat/atomic-openshift-node | <3.11.232-1.git.0.a5bc32f.el7 | 3.11.232-1.git.0.a5bc32f.el7 |
| redhat/atomic-openshift-pod | <3.11.232-1.git.0.a5bc32f.el7 | 3.11.232-1.git.0.a5bc32f.el7 |
| redhat/atomic-openshift-sdn-ovs | <3.11.232-1.git.0.a5bc32f.el7 | 3.11.232-1.git.0.a5bc32f.el7 |
| redhat/atomic-openshift-template-service-broker | <3.11.232-1.git.0.a5bc32f.el7 | 3.11.232-1.git.0.a5bc32f.el7 |
| redhat/atomic-openshift-tests | <3.11.232-1.git.0.a5bc32f.el7 | 3.11.232-1.git.0.a5bc32f.el7 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of RHSA-2020:2479?
The severity of RHSA-2020:2479 is important, indicating a significant security vulnerability in OpenShift Enterprise.
How do I fix RHSA-2020:2479?
To fix RHSA-2020:2479, you should update your OpenShift Enterprise packages to version 3.11.232-1.git.0.a5bc32f.el7.
Which packages are affected by RHSA-2020:2479?
RHSA-2020:2479 affects multiple packages including atomic-openshift, atomic-openshift-clients, and atomic-openshift-master.
What is the nature of the vulnerability in RHSA-2020:2479?
The vulnerability in RHSA-2020:2479 involves the mishandling of multiple argument rules leading to a bypass of intended access.
When should I apply the patch for RHSA-2020:2479?
You should apply the patch for RHSA-2020:2479 as soon as possible to mitigate the security risk associated with the vulnerability.
- agent/severity
- agent/type
- agent/softwarecombine
- agent/last-modified-date
- agent/first-publish-date
- agent/remedy
- agent/weakness
- agent/title
- agent/description
- collector/redhat-errata
- source/Red Hat
- anchor-id/RHSA-2020:2479
- agent/software-canonical-lookup
- agent/references
- agent/tags
- agent/event
- agent/source
- package-manager/redhat