CVE-2021-3636: Medium severity redhat Openshift vulnerability

Published Jul 2, 2021
·
Updated

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.

Other sources

The openshift-service-ca service contains unexpected CAs. In OpenShift 4.8 the service-ca.crt file only contains the self-signed certificate of the openshift-service-serving-signer CA certificate. In older versions of OpenShift there were more, additional CAs: - OU = openshift, CN = kube-apiserver-lb-signer - OU = openshift, CN = kube-apiserver-localhost-signer - OU = openshift, CN = kube-apiserver-service-network-signer - CN = openshift-kube-apiserver-operatorlocalhost-recovery-serving-signer - CN = ingress-operator - CN = .apps.cluster.example.com - CN = openshift-service-serving-signer

This means that an attacker who owns the ingress CA can impersonate as any in-cluster service-ca signed process. The issue impacts Confidentiality and Integrity of the OCP cluster.

OCP 4.8 is not impacted by this vulnerability.

Red Hat

Affected Software

3 affected componentsFixes available
redhat/openshift<0:4.8.0-202107161820.p0.git.051ac4f.assembly.stream.el7
0:4.8.0-202107161820.p0.git.051ac4f.assembly.stream.el7
redhat/openshift<4.8
4.8
redhat Openshift<4.8

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/openshift to a version that resolves this vulnerability.

    Fixed in 0:4.8.0-202107161820.p0.git.051ac4f.assembly.stream.el7
  2. Upgrade

    Upgrade redhat/openshift to a version that resolves this vulnerability.

    Fixed in 4.8

Event History

Jul 14, 2021
CVE Published
12:00 AM
Jul 30, 2021
CVE Published
via MITRE·07:27 PM
Data Sourced
via MITRE·07:27 PM
DescriptionWeakness
Data Sourced
via NVD·08:15 PM
RemedyDescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2021-3636?

CVE-2021-3636 has a severity rating that indicates it poses a security risk due to improper certificate generation.

2

How do I fix CVE-2021-3636?

To remediate CVE-2021-3636, upgrade to OpenShift version 4.8.0 or later.

3

What systems are affected by CVE-2021-3636?

CVE-2021-3636 affects OpenShift versions prior to 4.8.

4

What impact does CVE-2021-3636 have on security?

CVE-2021-3636 can potentially allow unauthorized access to in-cluster services due to the inclusion of additional certificates.

5

When was CVE-2021-3636 discovered?

CVE-2021-3636 was disclosed as a vulnerability affecting OpenShift prior to version 4.8.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203