cve.bz

CVE-2021-3636 redhat openshift: Improper Authentication

4.6 mediumExploit referenceEPSS 0.3%Fix available

Medium (4.6) in redhat openshift. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
It was found in OpenShift, before version 4.8, that the generated certificate for the in-cluster Service CA, incorrectly included additional certificates. The Service CA is automatically mounted into all pods, allowing them to safely connect to trusted in-cluster services that present certificates signed by the trusted Service CA. The incorrect inclusion of additional CAs in this certificate would allow an attacker that compromises any of the additional CAs to masquerade as a trusted in-cluster service.

Severity

CVSS 3.1

4.6 medium
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 21st percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-287 Improper Authentication
CWE-295 Improper Certificate Validation
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain 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.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
redhat:openshiftbefore 4.8

Linux distributions

DistributionReleasePackageFixed inAdvisory
Red Hatopenshift:4.8::el7cri-o, cri-o-debuginfo0:1.21.2-5.rhaos4.8.gitb27d974.el7RHSA-2021:2437
Red Hatopenshift:4.8::el7cri-tools, cri-tools-debuginfo0:1.21.0-2.el7RHSA-2021:2437
Red Hatopenshift:4.8::el7haproxy, haproxy-debuginfo0:2.2.13-1.el7RHSA-2021:2437
Red Hatopenshift:4.8::el7openshift, openshift-hyperkube0:4.8.0-202107161820.p0.git.051ac4f.assembly.stream.el7RHSA-2021:2437
Red Hatopenshift:4.8::el7openshift-ansible, openshift-ansible-test0:4.8.0-202106281541.p0.git.626f7a3.assembly.stream.el7RHSA-2021:2437
Red Hatopenshift:4.8::el7openshift-clients, openshift-clients-redistributable0:4.8.0-202106281541.p0.git.1077b05.assembly.stream.el7RHSA-2021:2437
Red Hatopenshift:4.8::el7runc, runc-debuginfo0:1.0.0-98.rhaos4.8.gitcd80260.el7RHSA-2021:2437
Red Hatopenshift:4.8::el8afterburn, rust-afterburn, afterburn-debuginfo and 1 more0:5.0.0-1.rhaos4.8.el8RHSA-2021:2437
Red Hatopenshift:4.8::el8atomic-openshift-service-idler0:4.8.0-202106281541.p0.git.39cfc66.assembly.stream.el8RHSA-2021:2437
Red Hatopenshift:4.8::el8butane, butane-debuginfo0:0.12.1-1.rhaos4.8.el8RHSA-2021:2437
Red Hatopenshift:4.8::el8console-login-helper-messages, console-login-helper-messages-profile, console-login-helper-messages-issuegen0:0.20.3-1.rhaos4.8.el8RHSA-2021:2437
Red Hatopenshift:4.8::el8coreos-installer, coreos-installer-bootinfra, coreos-installer-debuginfo and 2 more0:0.9.0-6.rhaos4.8.el8RHSA-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

Red Hat rates this Moderate.

Red Hat's statement

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.

ProductPackageStateAdvisory
Red Hat OpenShift Container Platform 4.8openshift-0:4.8.0-202107161820.p0.git.051ac4f.assembly.stream.el7Fixed 2021-07-27RHSA-2021:2437
Red Hat OpenShift Container Platform 3.11atomic-openshiftOut 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.

Attack patterns (CAPEC)

  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High
  • CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
  • CAPEC-57 Utilizing REST's Trust in the System Resource to Obtain Sensitive Data Likelihood: Medium · Severity: Very High
  • CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
  • CAPEC-114 Authentication Abuse Severity: Medium
  • CAPEC-115 Authentication Bypass Severity: Medium
  • CAPEC-151 Identity Spoofing Likelihood: Medium · Severity: Medium
  • CAPEC-194 Fake the Source of Data Severity: Medium
  • CAPEC-593 Session Hijacking Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-287.

References

Check your stackJSON