openshift-ansible: dockergc service account incorrectly associated with namespace during upgrade
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| [Red Hat] | openshift-ansible | affected |
|
Configuration 1 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat OpenShift Container Platform 3.11 | |||
| openshift-ansible-0:3.11.146-1.git.0.fcedb45.el7 | cpe:/a:redhat:openshift:3.11::el7 | RHSA-2019:2818 | 2019-09-23T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2019-5948 | A flaw was found during the upgrade of an existing OpenShift Container Platform 3.x cluster. Using CRI-O, the dockergc service account is assigned to the current namespace of the user performing the upgrade. This flaw can allow an unprivileged user to escalate their privileges to those allowed by the privileged Security Context Constraints. |
No CVSS v4.0
This CVE is not in the KEV list.
Exploit prediction score: 1.1% (1.074% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.