CVSS 3.1
4.6 mediumCVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:NMedium (4.6) in redhat openshift. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:NExplain CVE-2021-3636 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2021-3636?via=ask-ai-copy and https://cve.bz/cve/CVE-2021-3636?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2021-3636 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| redhat:openshift | before 4.8 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Red Hat | openshift:4.8::el7 | cri-o, cri-o-debuginfo | 0:1.21.2-5.rhaos4.8.gitb27d974.el7 | RHSA-2021:2437 |
| Red Hat | openshift:4.8::el7 | cri-tools, cri-tools-debuginfo | 0:1.21.0-2.el7 | RHSA-2021:2437 |
| Red Hat | openshift:4.8::el7 | haproxy, haproxy-debuginfo | 0:2.2.13-1.el7 | RHSA-2021:2437 |
| Red Hat | openshift:4.8::el7 | openshift, openshift-hyperkube | 0:4.8.0-202107161820.p0.git.051ac4f.assembly.stream.el7 | RHSA-2021:2437 |
| Red Hat | openshift:4.8::el7 | openshift-ansible, openshift-ansible-test | 0:4.8.0-202106281541.p0.git.626f7a3.assembly.stream.el7 | RHSA-2021:2437 |
| Red Hat | openshift:4.8::el7 | openshift-clients, openshift-clients-redistributable | 0:4.8.0-202106281541.p0.git.1077b05.assembly.stream.el7 | RHSA-2021:2437 |
| Red Hat | openshift:4.8::el7 | runc, runc-debuginfo | 0:1.0.0-98.rhaos4.8.gitcd80260.el7 | RHSA-2021:2437 |
| Red Hat | openshift:4.8::el8 | afterburn, rust-afterburn, afterburn-debuginfo and 1 more | 0:5.0.0-1.rhaos4.8.el8 | RHSA-2021:2437 |
| Red Hat | openshift:4.8::el8 | atomic-openshift-service-idler | 0:4.8.0-202106281541.p0.git.39cfc66.assembly.stream.el8 | RHSA-2021:2437 |
| Red Hat | openshift:4.8::el8 | butane, butane-debuginfo | 0:0.12.1-1.rhaos4.8.el8 | RHSA-2021:2437 |
| Red Hat | openshift:4.8::el8 | console-login-helper-messages, console-login-helper-messages-profile, console-login-helper-messages-issuegen | 0:0.20.3-1.rhaos4.8.el8 | RHSA-2021:2437 |
| Red Hat | openshift:4.8::el8 | coreos-installer, coreos-installer-bootinfra, coreos-installer-debuginfo and 2 more | 0:0.9.0-6.rhaos4.8.el8 | RHSA-2021:2437 |
| 49 more for Red Hat in the JSON and on Red Hat's page. | ||||
From the distributions' data via OSV.dev: Red Hat Security Data © Red Hat, Inc., CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Red Hat.
Red Hat rates this Moderate.
Though this CVE is fixed by default in freshly installed OpenShift 4.8 clusters, existing clusters that upgrade to 4.8 will need to opt-in to the new secure behaviour. Once opted-in, it is not possible to revert to the previous insecure behaviour.
Clusters can opt-in to the new secure behaviour by upgrading to version 4.8 or later and then setting "spec.useMoreSecureServiceCA" to true in the KubeControllerManager API object, e.g.:
```$ oc patch KubeControllerManager cluster -p '{"spec": {"useMoreSecureServiceCA": true}}' --type=merge```
The kube-controller-manager pod will then restart before the changes to take effect. New pods will then be provisioned with the secure Service CA.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat OpenShift Container Platform 4.8 | openshift-0:4.8.0-202107161820.p0.git.051ac4f.assembly.stream.el7 | Fixed 2021-07-27 | RHSA-2021:2437 |
| Red Hat OpenShift Container Platform 3.11 | atomic-openshift | Out of support scope |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2021-3636.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-287.