Red Hat Security Advisory: OpenShift Container Platform 3.11 security update
An update for atomic-openshift and jenkins-2-plugins is now available for Red Hat OpenShift Container Platform 3.11. Red Hat Product Security has rated this update as having a security impact of Moderate. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.
describes (3)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2019-10337US | high7.5 | — | ||
An XML external entities (XXE) vulnerability in Jenkins Token Macro Plugin 2.7 and earlier allowed attackers able to control a the content of the input file for the "XML" macro to… | ||||
| CVE-2019-3876US | medium6.3 | — | ||
A flaw was found in the /oauth/token/request custom endpoint of the OpenShift OAuth server allowing for XSS generation of CLI tokens due to missing X-Frame-Options and CSRF protect… | ||||
| CVE-2019-1002100US | medium6.5 | — | ||
In all Kubernetes versions prior to v1.11.8, v1.12.6, and v1.13.4, users that are authorized to make patch requests to the Kubernetes API Server can send a specially crafted patch… | ||||
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHSA-2019:1851self
- https://access.redhat.com/security/updates/classification/#moderateexternal
- 1683190external
- 1691107external
- 1719782external
- Canonical URLself
remediations (130)
- Fixedatomic-openshift-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-0:3.11.129-1.git.0.bd4f2d5.el7.src as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-0:3.11.129-1.git.0.bd4f2d5.el7.src as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-0:3.11.129-1.git.0.bd4f2d5.el7.src as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-clients-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-clients-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-clients-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-clients-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-clients-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-clients-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-clients-redistributable-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-clients-redistributable-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-clients-redistributable-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-docker-excluder-0:3.11.129-1.git.0.bd4f2d5.el7.noarch as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-docker-excluder-0:3.11.129-1.git.0.bd4f2d5.el7.noarch as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-docker-excluder-0:3.11.129-1.git.0.bd4f2d5.el7.noarch as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-excluder-0:3.11.129-1.git.0.bd4f2d5.el7.noarch as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-excluder-0:3.11.129-1.git.0.bd4f2d5.el7.noarch as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-excluder-0:3.11.129-1.git.0.bd4f2d5.el7.noarch as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-hyperkube-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-hyperkube-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-hyperkube-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-hyperkube-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-hyperkube-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-hyperkube-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-hypershift-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-hypershift-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-hypershift-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-hypershift-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-hypershift-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-hypershift-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-master-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-master-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-master-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-master-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-master-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-master-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-node-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-node-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-node-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-node-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-node-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-node-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-pod-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-pod-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-pod-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-pod-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-pod-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-pod-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-sdn-ovs-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-sdn-ovs-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-sdn-ovs-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-sdn-ovs-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-sdn-ovs-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-sdn-ovs-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-template-service-broker-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-template-service-broker-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-template-service-broker-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-template-service-broker-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-template-service-broker-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-template-service-broker-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-tests-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-tests-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-tests-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-tests-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-tests-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedatomic-openshift-tests-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedjenkins-2-plugins-0:3.11.1560870549-1.el7.noarch as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedjenkins-2-plugins-0:3.11.1560870549-1.el7.noarch as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedjenkins-2-plugins-0:3.11.1560870549-1.el7.noarch as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedjenkins-2-plugins-0:3.11.1560870549-1.el7.src as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedjenkins-2-plugins-0:3.11.1560870549-1.el7.src as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Fixedjenkins-2-plugins-0:3.11.1560870549-1.el7.src as a component of Red Hat OpenShift Container Platform 3.11
For OpenShift Container Platform 3.11 see the following documentation for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
https://access.redhat.com/errata/RHSA-2019:1851 - Workaroundatomic-openshift-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
Remove ‘patch’ permissions from untrusted users.
- Workaroundatomic-openshift-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
Since at least v3.4, the OpenShift documentation [1] has specified the format for corsAllowedOrigins to accurately match intended hostnames. Since at least v3.7, installs will default to use the correct regular expression formatted variables. Earlier versions may be configured with plain strings, a configuration which will persist across cluster upgrades, opening them to cross origin vulnerabilities such as this. At a minimum, you should ensure that the corsAllowedOrigin definition within master-config.yaml contains elements in the form ~~~ corsAllowedOrigins: - (?i)//my\.subdomain\.domain\.com(:|\z) ~~~ and not the form ~~~ corsAllowedOrigins: - domain.com ~~~ as the first will permit cross origin requests only if the host matches exactly, whereas the second will permit from any host that merely contains the string (such as ABCDdomain.com or even domain.comABCD.com). Footnotes: [1] https://docs.openshift.com/container-platform/3.4/architecture/infrastructure_components/web_console.html#corsAllowedOrigins
- Workaroundatomic-openshift-0:3.11.129-1.git.0.bd4f2d5.el7.src as a component of Red Hat OpenShift Container Platform 3.11
Remove ‘patch’ permissions from untrusted users.
- Workaroundatomic-openshift-0:3.11.129-1.git.0.bd4f2d5.el7.src as a component of Red Hat OpenShift Container Platform 3.11
Since at least v3.4, the OpenShift documentation [1] has specified the format for corsAllowedOrigins to accurately match intended hostnames. Since at least v3.7, installs will default to use the correct regular expression formatted variables. Earlier versions may be configured with plain strings, a configuration which will persist across cluster upgrades, opening them to cross origin vulnerabilities such as this. At a minimum, you should ensure that the corsAllowedOrigin definition within master-config.yaml contains elements in the form ~~~ corsAllowedOrigins: - (?i)//my\.subdomain\.domain\.com(:|\z) ~~~ and not the form ~~~ corsAllowedOrigins: - domain.com ~~~ as the first will permit cross origin requests only if the host matches exactly, whereas the second will permit from any host that merely contains the string (such as ABCDdomain.com or even domain.comABCD.com). Footnotes: [1] https://docs.openshift.com/container-platform/3.4/architecture/infrastructure_components/web_console.html#corsAllowedOrigins
- Workaroundatomic-openshift-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
Remove ‘patch’ permissions from untrusted users.
- Workaroundatomic-openshift-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
Since at least v3.4, the OpenShift documentation [1] has specified the format for corsAllowedOrigins to accurately match intended hostnames. Since at least v3.7, installs will default to use the correct regular expression formatted variables. Earlier versions may be configured with plain strings, a configuration which will persist across cluster upgrades, opening them to cross origin vulnerabilities such as this. At a minimum, you should ensure that the corsAllowedOrigin definition within master-config.yaml contains elements in the form ~~~ corsAllowedOrigins: - (?i)//my\.subdomain\.domain\.com(:|\z) ~~~ and not the form ~~~ corsAllowedOrigins: - domain.com ~~~ as the first will permit cross origin requests only if the host matches exactly, whereas the second will permit from any host that merely contains the string (such as ABCDdomain.com or even domain.comABCD.com). Footnotes: [1] https://docs.openshift.com/container-platform/3.4/architecture/infrastructure_components/web_console.html#corsAllowedOrigins
- Workaroundatomic-openshift-clients-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
Remove ‘patch’ permissions from untrusted users.
- Workaroundatomic-openshift-clients-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
Since at least v3.4, the OpenShift documentation [1] has specified the format for corsAllowedOrigins to accurately match intended hostnames. Since at least v3.7, installs will default to use the correct regular expression formatted variables. Earlier versions may be configured with plain strings, a configuration which will persist across cluster upgrades, opening them to cross origin vulnerabilities such as this. At a minimum, you should ensure that the corsAllowedOrigin definition within master-config.yaml contains elements in the form ~~~ corsAllowedOrigins: - (?i)//my\.subdomain\.domain\.com(:|\z) ~~~ and not the form ~~~ corsAllowedOrigins: - domain.com ~~~ as the first will permit cross origin requests only if the host matches exactly, whereas the second will permit from any host that merely contains the string (such as ABCDdomain.com or even domain.comABCD.com). Footnotes: [1] https://docs.openshift.com/container-platform/3.4/architecture/infrastructure_components/web_console.html#corsAllowedOrigins
- Workaroundatomic-openshift-clients-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
Remove ‘patch’ permissions from untrusted users.
- Workaroundatomic-openshift-clients-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
Since at least v3.4, the OpenShift documentation [1] has specified the format for corsAllowedOrigins to accurately match intended hostnames. Since at least v3.7, installs will default to use the correct regular expression formatted variables. Earlier versions may be configured with plain strings, a configuration which will persist across cluster upgrades, opening them to cross origin vulnerabilities such as this. At a minimum, you should ensure that the corsAllowedOrigin definition within master-config.yaml contains elements in the form ~~~ corsAllowedOrigins: - (?i)//my\.subdomain\.domain\.com(:|\z) ~~~ and not the form ~~~ corsAllowedOrigins: - domain.com ~~~ as the first will permit cross origin requests only if the host matches exactly, whereas the second will permit from any host that merely contains the string (such as ABCDdomain.com or even domain.comABCD.com). Footnotes: [1] https://docs.openshift.com/container-platform/3.4/architecture/infrastructure_components/web_console.html#corsAllowedOrigins
- Workaroundatomic-openshift-clients-redistributable-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
Remove ‘patch’ permissions from untrusted users.
- Workaroundatomic-openshift-clients-redistributable-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
Since at least v3.4, the OpenShift documentation [1] has specified the format for corsAllowedOrigins to accurately match intended hostnames. Since at least v3.7, installs will default to use the correct regular expression formatted variables. Earlier versions may be configured with plain strings, a configuration which will persist across cluster upgrades, opening them to cross origin vulnerabilities such as this. At a minimum, you should ensure that the corsAllowedOrigin definition within master-config.yaml contains elements in the form ~~~ corsAllowedOrigins: - (?i)//my\.subdomain\.domain\.com(:|\z) ~~~ and not the form ~~~ corsAllowedOrigins: - domain.com ~~~ as the first will permit cross origin requests only if the host matches exactly, whereas the second will permit from any host that merely contains the string (such as ABCDdomain.com or even domain.comABCD.com). Footnotes: [1] https://docs.openshift.com/container-platform/3.4/architecture/infrastructure_components/web_console.html#corsAllowedOrigins
- Workaroundatomic-openshift-docker-excluder-0:3.11.129-1.git.0.bd4f2d5.el7.noarch as a component of Red Hat OpenShift Container Platform 3.11
Remove ‘patch’ permissions from untrusted users.
- Workaroundatomic-openshift-docker-excluder-0:3.11.129-1.git.0.bd4f2d5.el7.noarch as a component of Red Hat OpenShift Container Platform 3.11
Since at least v3.4, the OpenShift documentation [1] has specified the format for corsAllowedOrigins to accurately match intended hostnames. Since at least v3.7, installs will default to use the correct regular expression formatted variables. Earlier versions may be configured with plain strings, a configuration which will persist across cluster upgrades, opening them to cross origin vulnerabilities such as this. At a minimum, you should ensure that the corsAllowedOrigin definition within master-config.yaml contains elements in the form ~~~ corsAllowedOrigins: - (?i)//my\.subdomain\.domain\.com(:|\z) ~~~ and not the form ~~~ corsAllowedOrigins: - domain.com ~~~ as the first will permit cross origin requests only if the host matches exactly, whereas the second will permit from any host that merely contains the string (such as ABCDdomain.com or even domain.comABCD.com). Footnotes: [1] https://docs.openshift.com/container-platform/3.4/architecture/infrastructure_components/web_console.html#corsAllowedOrigins
- Workaroundatomic-openshift-excluder-0:3.11.129-1.git.0.bd4f2d5.el7.noarch as a component of Red Hat OpenShift Container Platform 3.11
Remove ‘patch’ permissions from untrusted users.
- Workaroundatomic-openshift-excluder-0:3.11.129-1.git.0.bd4f2d5.el7.noarch as a component of Red Hat OpenShift Container Platform 3.11
Since at least v3.4, the OpenShift documentation [1] has specified the format for corsAllowedOrigins to accurately match intended hostnames. Since at least v3.7, installs will default to use the correct regular expression formatted variables. Earlier versions may be configured with plain strings, a configuration which will persist across cluster upgrades, opening them to cross origin vulnerabilities such as this. At a minimum, you should ensure that the corsAllowedOrigin definition within master-config.yaml contains elements in the form ~~~ corsAllowedOrigins: - (?i)//my\.subdomain\.domain\.com(:|\z) ~~~ and not the form ~~~ corsAllowedOrigins: - domain.com ~~~ as the first will permit cross origin requests only if the host matches exactly, whereas the second will permit from any host that merely contains the string (such as ABCDdomain.com or even domain.comABCD.com). Footnotes: [1] https://docs.openshift.com/container-platform/3.4/architecture/infrastructure_components/web_console.html#corsAllowedOrigins
- Workaroundatomic-openshift-hyperkube-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
Remove ‘patch’ permissions from untrusted users.
- Workaroundatomic-openshift-hyperkube-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
Since at least v3.4, the OpenShift documentation [1] has specified the format for corsAllowedOrigins to accurately match intended hostnames. Since at least v3.7, installs will default to use the correct regular expression formatted variables. Earlier versions may be configured with plain strings, a configuration which will persist across cluster upgrades, opening them to cross origin vulnerabilities such as this. At a minimum, you should ensure that the corsAllowedOrigin definition within master-config.yaml contains elements in the form ~~~ corsAllowedOrigins: - (?i)//my\.subdomain\.domain\.com(:|\z) ~~~ and not the form ~~~ corsAllowedOrigins: - domain.com ~~~ as the first will permit cross origin requests only if the host matches exactly, whereas the second will permit from any host that merely contains the string (such as ABCDdomain.com or even domain.comABCD.com). Footnotes: [1] https://docs.openshift.com/container-platform/3.4/architecture/infrastructure_components/web_console.html#corsAllowedOrigins
- Workaroundatomic-openshift-hyperkube-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
Remove ‘patch’ permissions from untrusted users.
- Workaroundatomic-openshift-hyperkube-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
Since at least v3.4, the OpenShift documentation [1] has specified the format for corsAllowedOrigins to accurately match intended hostnames. Since at least v3.7, installs will default to use the correct regular expression formatted variables. Earlier versions may be configured with plain strings, a configuration which will persist across cluster upgrades, opening them to cross origin vulnerabilities such as this. At a minimum, you should ensure that the corsAllowedOrigin definition within master-config.yaml contains elements in the form ~~~ corsAllowedOrigins: - (?i)//my\.subdomain\.domain\.com(:|\z) ~~~ and not the form ~~~ corsAllowedOrigins: - domain.com ~~~ as the first will permit cross origin requests only if the host matches exactly, whereas the second will permit from any host that merely contains the string (such as ABCDdomain.com or even domain.comABCD.com). Footnotes: [1] https://docs.openshift.com/container-platform/3.4/architecture/infrastructure_components/web_console.html#corsAllowedOrigins
- Workaroundatomic-openshift-hypershift-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
Remove ‘patch’ permissions from untrusted users.
- Workaroundatomic-openshift-hypershift-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
Since at least v3.4, the OpenShift documentation [1] has specified the format for corsAllowedOrigins to accurately match intended hostnames. Since at least v3.7, installs will default to use the correct regular expression formatted variables. Earlier versions may be configured with plain strings, a configuration which will persist across cluster upgrades, opening them to cross origin vulnerabilities such as this. At a minimum, you should ensure that the corsAllowedOrigin definition within master-config.yaml contains elements in the form ~~~ corsAllowedOrigins: - (?i)//my\.subdomain\.domain\.com(:|\z) ~~~ and not the form ~~~ corsAllowedOrigins: - domain.com ~~~ as the first will permit cross origin requests only if the host matches exactly, whereas the second will permit from any host that merely contains the string (such as ABCDdomain.com or even domain.comABCD.com). Footnotes: [1] https://docs.openshift.com/container-platform/3.4/architecture/infrastructure_components/web_console.html#corsAllowedOrigins
- Workaroundatomic-openshift-hypershift-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
Remove ‘patch’ permissions from untrusted users.
- Workaroundatomic-openshift-hypershift-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
Since at least v3.4, the OpenShift documentation [1] has specified the format for corsAllowedOrigins to accurately match intended hostnames. Since at least v3.7, installs will default to use the correct regular expression formatted variables. Earlier versions may be configured with plain strings, a configuration which will persist across cluster upgrades, opening them to cross origin vulnerabilities such as this. At a minimum, you should ensure that the corsAllowedOrigin definition within master-config.yaml contains elements in the form ~~~ corsAllowedOrigins: - (?i)//my\.subdomain\.domain\.com(:|\z) ~~~ and not the form ~~~ corsAllowedOrigins: - domain.com ~~~ as the first will permit cross origin requests only if the host matches exactly, whereas the second will permit from any host that merely contains the string (such as ABCDdomain.com or even domain.comABCD.com). Footnotes: [1] https://docs.openshift.com/container-platform/3.4/architecture/infrastructure_components/web_console.html#corsAllowedOrigins
- Workaroundatomic-openshift-master-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
Remove ‘patch’ permissions from untrusted users.
- Workaroundatomic-openshift-master-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
Since at least v3.4, the OpenShift documentation [1] has specified the format for corsAllowedOrigins to accurately match intended hostnames. Since at least v3.7, installs will default to use the correct regular expression formatted variables. Earlier versions may be configured with plain strings, a configuration which will persist across cluster upgrades, opening them to cross origin vulnerabilities such as this. At a minimum, you should ensure that the corsAllowedOrigin definition within master-config.yaml contains elements in the form ~~~ corsAllowedOrigins: - (?i)//my\.subdomain\.domain\.com(:|\z) ~~~ and not the form ~~~ corsAllowedOrigins: - domain.com ~~~ as the first will permit cross origin requests only if the host matches exactly, whereas the second will permit from any host that merely contains the string (such as ABCDdomain.com or even domain.comABCD.com). Footnotes: [1] https://docs.openshift.com/container-platform/3.4/architecture/infrastructure_components/web_console.html#corsAllowedOrigins
- Workaroundatomic-openshift-master-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
Remove ‘patch’ permissions from untrusted users.
- Workaroundatomic-openshift-master-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
Since at least v3.4, the OpenShift documentation [1] has specified the format for corsAllowedOrigins to accurately match intended hostnames. Since at least v3.7, installs will default to use the correct regular expression formatted variables. Earlier versions may be configured with plain strings, a configuration which will persist across cluster upgrades, opening them to cross origin vulnerabilities such as this. At a minimum, you should ensure that the corsAllowedOrigin definition within master-config.yaml contains elements in the form ~~~ corsAllowedOrigins: - (?i)//my\.subdomain\.domain\.com(:|\z) ~~~ and not the form ~~~ corsAllowedOrigins: - domain.com ~~~ as the first will permit cross origin requests only if the host matches exactly, whereas the second will permit from any host that merely contains the string (such as ABCDdomain.com or even domain.comABCD.com). Footnotes: [1] https://docs.openshift.com/container-platform/3.4/architecture/infrastructure_components/web_console.html#corsAllowedOrigins
- Workaroundatomic-openshift-node-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
Remove ‘patch’ permissions from untrusted users.
- Workaroundatomic-openshift-node-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
Since at least v3.4, the OpenShift documentation [1] has specified the format for corsAllowedOrigins to accurately match intended hostnames. Since at least v3.7, installs will default to use the correct regular expression formatted variables. Earlier versions may be configured with plain strings, a configuration which will persist across cluster upgrades, opening them to cross origin vulnerabilities such as this. At a minimum, you should ensure that the corsAllowedOrigin definition within master-config.yaml contains elements in the form ~~~ corsAllowedOrigins: - (?i)//my\.subdomain\.domain\.com(:|\z) ~~~ and not the form ~~~ corsAllowedOrigins: - domain.com ~~~ as the first will permit cross origin requests only if the host matches exactly, whereas the second will permit from any host that merely contains the string (such as ABCDdomain.com or even domain.comABCD.com). Footnotes: [1] https://docs.openshift.com/container-platform/3.4/architecture/infrastructure_components/web_console.html#corsAllowedOrigins
- Workaroundatomic-openshift-node-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
Remove ‘patch’ permissions from untrusted users.
- Workaroundatomic-openshift-node-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
Since at least v3.4, the OpenShift documentation [1] has specified the format for corsAllowedOrigins to accurately match intended hostnames. Since at least v3.7, installs will default to use the correct regular expression formatted variables. Earlier versions may be configured with plain strings, a configuration which will persist across cluster upgrades, opening them to cross origin vulnerabilities such as this. At a minimum, you should ensure that the corsAllowedOrigin definition within master-config.yaml contains elements in the form ~~~ corsAllowedOrigins: - (?i)//my\.subdomain\.domain\.com(:|\z) ~~~ and not the form ~~~ corsAllowedOrigins: - domain.com ~~~ as the first will permit cross origin requests only if the host matches exactly, whereas the second will permit from any host that merely contains the string (such as ABCDdomain.com or even domain.comABCD.com). Footnotes: [1] https://docs.openshift.com/container-platform/3.4/architecture/infrastructure_components/web_console.html#corsAllowedOrigins
- Workaroundatomic-openshift-pod-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
Remove ‘patch’ permissions from untrusted users.
- Workaroundatomic-openshift-pod-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
Since at least v3.4, the OpenShift documentation [1] has specified the format for corsAllowedOrigins to accurately match intended hostnames. Since at least v3.7, installs will default to use the correct regular expression formatted variables. Earlier versions may be configured with plain strings, a configuration which will persist across cluster upgrades, opening them to cross origin vulnerabilities such as this. At a minimum, you should ensure that the corsAllowedOrigin definition within master-config.yaml contains elements in the form ~~~ corsAllowedOrigins: - (?i)//my\.subdomain\.domain\.com(:|\z) ~~~ and not the form ~~~ corsAllowedOrigins: - domain.com ~~~ as the first will permit cross origin requests only if the host matches exactly, whereas the second will permit from any host that merely contains the string (such as ABCDdomain.com or even domain.comABCD.com). Footnotes: [1] https://docs.openshift.com/container-platform/3.4/architecture/infrastructure_components/web_console.html#corsAllowedOrigins
- Workaroundatomic-openshift-pod-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
Remove ‘patch’ permissions from untrusted users.
- Workaroundatomic-openshift-pod-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
Since at least v3.4, the OpenShift documentation [1] has specified the format for corsAllowedOrigins to accurately match intended hostnames. Since at least v3.7, installs will default to use the correct regular expression formatted variables. Earlier versions may be configured with plain strings, a configuration which will persist across cluster upgrades, opening them to cross origin vulnerabilities such as this. At a minimum, you should ensure that the corsAllowedOrigin definition within master-config.yaml contains elements in the form ~~~ corsAllowedOrigins: - (?i)//my\.subdomain\.domain\.com(:|\z) ~~~ and not the form ~~~ corsAllowedOrigins: - domain.com ~~~ as the first will permit cross origin requests only if the host matches exactly, whereas the second will permit from any host that merely contains the string (such as ABCDdomain.com or even domain.comABCD.com). Footnotes: [1] https://docs.openshift.com/container-platform/3.4/architecture/infrastructure_components/web_console.html#corsAllowedOrigins
- Workaroundatomic-openshift-sdn-ovs-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
Remove ‘patch’ permissions from untrusted users.
- Workaroundatomic-openshift-sdn-ovs-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
Since at least v3.4, the OpenShift documentation [1] has specified the format for corsAllowedOrigins to accurately match intended hostnames. Since at least v3.7, installs will default to use the correct regular expression formatted variables. Earlier versions may be configured with plain strings, a configuration which will persist across cluster upgrades, opening them to cross origin vulnerabilities such as this. At a minimum, you should ensure that the corsAllowedOrigin definition within master-config.yaml contains elements in the form ~~~ corsAllowedOrigins: - (?i)//my\.subdomain\.domain\.com(:|\z) ~~~ and not the form ~~~ corsAllowedOrigins: - domain.com ~~~ as the first will permit cross origin requests only if the host matches exactly, whereas the second will permit from any host that merely contains the string (such as ABCDdomain.com or even domain.comABCD.com). Footnotes: [1] https://docs.openshift.com/container-platform/3.4/architecture/infrastructure_components/web_console.html#corsAllowedOrigins
- Workaroundatomic-openshift-sdn-ovs-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
Remove ‘patch’ permissions from untrusted users.
- Workaroundatomic-openshift-sdn-ovs-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
Since at least v3.4, the OpenShift documentation [1] has specified the format for corsAllowedOrigins to accurately match intended hostnames. Since at least v3.7, installs will default to use the correct regular expression formatted variables. Earlier versions may be configured with plain strings, a configuration which will persist across cluster upgrades, opening them to cross origin vulnerabilities such as this. At a minimum, you should ensure that the corsAllowedOrigin definition within master-config.yaml contains elements in the form ~~~ corsAllowedOrigins: - (?i)//my\.subdomain\.domain\.com(:|\z) ~~~ and not the form ~~~ corsAllowedOrigins: - domain.com ~~~ as the first will permit cross origin requests only if the host matches exactly, whereas the second will permit from any host that merely contains the string (such as ABCDdomain.com or even domain.comABCD.com). Footnotes: [1] https://docs.openshift.com/container-platform/3.4/architecture/infrastructure_components/web_console.html#corsAllowedOrigins
- Workaroundatomic-openshift-template-service-broker-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
Remove ‘patch’ permissions from untrusted users.
- Workaroundatomic-openshift-template-service-broker-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
Since at least v3.4, the OpenShift documentation [1] has specified the format for corsAllowedOrigins to accurately match intended hostnames. Since at least v3.7, installs will default to use the correct regular expression formatted variables. Earlier versions may be configured with plain strings, a configuration which will persist across cluster upgrades, opening them to cross origin vulnerabilities such as this. At a minimum, you should ensure that the corsAllowedOrigin definition within master-config.yaml contains elements in the form ~~~ corsAllowedOrigins: - (?i)//my\.subdomain\.domain\.com(:|\z) ~~~ and not the form ~~~ corsAllowedOrigins: - domain.com ~~~ as the first will permit cross origin requests only if the host matches exactly, whereas the second will permit from any host that merely contains the string (such as ABCDdomain.com or even domain.comABCD.com). Footnotes: [1] https://docs.openshift.com/container-platform/3.4/architecture/infrastructure_components/web_console.html#corsAllowedOrigins
- Workaroundatomic-openshift-template-service-broker-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
Remove ‘patch’ permissions from untrusted users.
- Workaroundatomic-openshift-template-service-broker-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
Since at least v3.4, the OpenShift documentation [1] has specified the format for corsAllowedOrigins to accurately match intended hostnames. Since at least v3.7, installs will default to use the correct regular expression formatted variables. Earlier versions may be configured with plain strings, a configuration which will persist across cluster upgrades, opening them to cross origin vulnerabilities such as this. At a minimum, you should ensure that the corsAllowedOrigin definition within master-config.yaml contains elements in the form ~~~ corsAllowedOrigins: - (?i)//my\.subdomain\.domain\.com(:|\z) ~~~ and not the form ~~~ corsAllowedOrigins: - domain.com ~~~ as the first will permit cross origin requests only if the host matches exactly, whereas the second will permit from any host that merely contains the string (such as ABCDdomain.com or even domain.comABCD.com). Footnotes: [1] https://docs.openshift.com/container-platform/3.4/architecture/infrastructure_components/web_console.html#corsAllowedOrigins
- Workaroundatomic-openshift-tests-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
Remove ‘patch’ permissions from untrusted users.
- Workaroundatomic-openshift-tests-0:3.11.129-1.git.0.bd4f2d5.el7.ppc64le as a component of Red Hat OpenShift Container Platform 3.11
Since at least v3.4, the OpenShift documentation [1] has specified the format for corsAllowedOrigins to accurately match intended hostnames. Since at least v3.7, installs will default to use the correct regular expression formatted variables. Earlier versions may be configured with plain strings, a configuration which will persist across cluster upgrades, opening them to cross origin vulnerabilities such as this. At a minimum, you should ensure that the corsAllowedOrigin definition within master-config.yaml contains elements in the form ~~~ corsAllowedOrigins: - (?i)//my\.subdomain\.domain\.com(:|\z) ~~~ and not the form ~~~ corsAllowedOrigins: - domain.com ~~~ as the first will permit cross origin requests only if the host matches exactly, whereas the second will permit from any host that merely contains the string (such as ABCDdomain.com or even domain.comABCD.com). Footnotes: [1] https://docs.openshift.com/container-platform/3.4/architecture/infrastructure_components/web_console.html#corsAllowedOrigins
- Workaroundatomic-openshift-tests-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
Remove ‘patch’ permissions from untrusted users.
- Workaroundatomic-openshift-tests-0:3.11.129-1.git.0.bd4f2d5.el7.x86_64 as a component of Red Hat OpenShift Container Platform 3.11
Since at least v3.4, the OpenShift documentation [1] has specified the format for corsAllowedOrigins to accurately match intended hostnames. Since at least v3.7, installs will default to use the correct regular expression formatted variables. Earlier versions may be configured with plain strings, a configuration which will persist across cluster upgrades, opening them to cross origin vulnerabilities such as this. At a minimum, you should ensure that the corsAllowedOrigin definition within master-config.yaml contains elements in the form ~~~ corsAllowedOrigins: - (?i)//my\.subdomain\.domain\.com(:|\z) ~~~ and not the form ~~~ corsAllowedOrigins: - domain.com ~~~ as the first will permit cross origin requests only if the host matches exactly, whereas the second will permit from any host that merely contains the string (such as ABCDdomain.com or even domain.comABCD.com). Footnotes: [1] https://docs.openshift.com/container-platform/3.4/architecture/infrastructure_components/web_console.html#corsAllowedOrigins
- Workaroundjenkins-2-plugins-0:3.11.1560870549-1.el7.noarch as a component of Red Hat OpenShift Container Platform 3.11
Remove ‘patch’ permissions from untrusted users.
- Workaroundjenkins-2-plugins-0:3.11.1560870549-1.el7.noarch as a component of Red Hat OpenShift Container Platform 3.11
Since at least v3.4, the OpenShift documentation [1] has specified the format for corsAllowedOrigins to accurately match intended hostnames. Since at least v3.7, installs will default to use the correct regular expression formatted variables. Earlier versions may be configured with plain strings, a configuration which will persist across cluster upgrades, opening them to cross origin vulnerabilities such as this. At a minimum, you should ensure that the corsAllowedOrigin definition within master-config.yaml contains elements in the form ~~~ corsAllowedOrigins: - (?i)//my\.subdomain\.domain\.com(:|\z) ~~~ and not the form ~~~ corsAllowedOrigins: - domain.com ~~~ as the first will permit cross origin requests only if the host matches exactly, whereas the second will permit from any host that merely contains the string (such as ABCDdomain.com or even domain.comABCD.com). Footnotes: [1] https://docs.openshift.com/container-platform/3.4/architecture/infrastructure_components/web_console.html#corsAllowedOrigins
- Workaroundjenkins-2-plugins-0:3.11.1560870549-1.el7.src as a component of Red Hat OpenShift Container Platform 3.11
Remove ‘patch’ permissions from untrusted users.
- Workaroundjenkins-2-plugins-0:3.11.1560870549-1.el7.src as a component of Red Hat OpenShift Container Platform 3.11
Since at least v3.4, the OpenShift documentation [1] has specified the format for corsAllowedOrigins to accurately match intended hostnames. Since at least v3.7, installs will default to use the correct regular expression formatted variables. Earlier versions may be configured with plain strings, a configuration which will persist across cluster upgrades, opening them to cross origin vulnerabilities such as this. At a minimum, you should ensure that the corsAllowedOrigin definition within master-config.yaml contains elements in the form ~~~ corsAllowedOrigins: - (?i)//my\.subdomain\.domain\.com(:|\z) ~~~ and not the form ~~~ corsAllowedOrigins: - domain.com ~~~ as the first will permit cross origin requests only if the host matches exactly, whereas the second will permit from any host that merely contains the string (such as ABCDdomain.com or even domain.comABCD.com). Footnotes: [1] https://docs.openshift.com/container-platform/3.4/architecture/infrastructure_components/web_console.html#corsAllowedOrigins
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan