Hide Forgot
crypto/tls clients can panic when provided a certificate of the wrong type for the negotiated parameters. net/http clients performing HTTPS requests are also affected. The panic can be triggered by an attacker in a privileged network position without access to the server certificate's private key, as long as a trusted ECDSA or Ed25519 certificate for the server exists (or can be issued), or the client is configured with Config.InsecureSkipVerify. Clients that disable all TLS_RSA cipher suites (that is, TLS 1.0–1.2 cipher suites without ECDHE), as well as TLS 1.3-only clients, are unaffected. References: https://golang.org/doc/devel/release https://github.com/golang/go/issues/47145 https://github.com/golang/go/issues/47144
Created golang tracking bugs for this issue: Affects: fedora-all [bug 1983597]
Created golang tracking bugs for this issue: Affects: epel-7 [bug 1986200]
Created buildah tracking bugs for this issue: Affects: fedora-all [bug 1987738] Created containernetworking-plugins tracking bugs for this issue: Affects: fedora-all [bug 1987737] Created podman tracking bugs for this issue: Affects: fedora-all [bug 1987739]
Created runc tracking bugs for this issue: Affects: fedora-all [bug 1987832]
Flaw summary: Code in golang's crypto/tls/key_agreement.go in the generateClientKeyExchange() routine, which is used in the TLS handshake, made an assumption that the provided certificate's public key was of the correct type for TLS_RSA cipher suites: encrypted, err := rsa.EncryptPKCS1v15(config.rand(), cert.PublicKey.(*rsa.PublicKey), preMasterSecret) The patch fixes the issue by first checking for errors when processing the provided public key from the X509 certificate, then if and only if no errors exist, it will begin the encryption process: rsaKey, ok := cert.PublicKey.(*rsa.PublicKey) if !ok { return nil, nil, errors.New("tls: server certificate contains incorrect key type for selected ciphersuite") } encrypted, err := rsa.EncryptPKCS1v15(config.rand(), rsaKey, preMasterSecret)
This issue has been addressed in the following products: Red Hat Developer Tools Via RHSA-2021:3015 https://access.redhat.com/errata/RHSA-2021:3015
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2021-34558
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.8 Via RHSA-2021:2984 https://access.redhat.com/errata/RHSA-2021:2984
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.8 Via RHSA-2021:2983 https://access.redhat.com/errata/RHSA-2021:2983
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2021:3076 https://access.redhat.com/errata/RHSA-2021:3076
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.6 Via RHSA-2021:3009 https://access.redhat.com/errata/RHSA-2021:3009
This issue has been addressed in the following products: RHACS-3.64-RHEL-8 Via RHSA-2021:3146 https://access.redhat.com/errata/RHSA-2021:3146
This issue has been addressed in the following products: Red Hat OpenShift Jaeger 1.20 Via RHSA-2021:3229 https://access.redhat.com/errata/RHSA-2021:3229
OpenShift engineering has decided to NOT ship 4.8.6 on 8/23 due to the following issue. https://bugzilla.redhat.com/show_bug.cgi?id=1995785 All the fixes part will be now included in 4.8.7 on 8/30.
This issue has been addressed in the following products: RHEL-8-CNV-4.8 Via RHSA-2021:3259 https://access.redhat.com/errata/RHSA-2021:3259
This issue has been addressed in the following products: Red Hat Migration Toolkit for Containers 1.5 Via RHSA-2021:3361 https://access.redhat.com/errata/RHSA-2021:3361
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.8 Via RHSA-2021:3248 https://access.redhat.com/errata/RHSA-2021:3248
This issue has been addressed in the following products: Openshift Serverless 1 on RHEL 8 Via RHSA-2021:3555 https://access.redhat.com/errata/RHSA-2021:3555
This issue has been addressed in the following products: Openshift Serveless 1.17 Via RHSA-2021:3556 https://access.redhat.com/errata/RHSA-2021:3556
This issue has been addressed in the following products: RHEL-8-CNV-4.8 Via RHSA-2021:3598 https://access.redhat.com/errata/RHSA-2021:3598
This issue has been addressed in the following products: RHEL-8-CNV-2.6 Via RHSA-2021:3733 https://access.redhat.com/errata/RHSA-2021:3733
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.9 Via RHSA-2021:3759 https://access.redhat.com/errata/RHSA-2021:3759
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.8 Via RHSA-2021:3820 https://access.redhat.com/errata/RHSA-2021:3820
This issue has been addressed in the following products: RHEL-8-CNV-4.9 Via RHSA-2021:4104 https://access.redhat.com/errata/RHSA-2021:4104
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2021:4226 https://access.redhat.com/errata/RHSA-2021:4226
This issue has been addressed in the following products: Service Telemetry Framework 1.3 for RHEL 8 Via RHSA-2021:4582 https://access.redhat.com/errata/RHSA-2021:4582
This issue has been addressed in the following products: RHEL-8-CNV-2.6 RHEL-7-CNV-2.6 Via RHSA-2021:4722 https://access.redhat.com/errata/RHSA-2021:4722
This issue has been addressed in the following products: RHEL-8-CNV-2.6 Via RHSA-2021:4725 https://access.redhat.com/errata/RHSA-2021:4725
This issue has been addressed in the following products: RHEL-8-CNV-4.8 Via RHSA-2021:4914 https://access.redhat.com/errata/RHSA-2021:4914
This issue has been addressed in the following products: Red Hat OpenShift Data Foundation 4.9.0 on RHEL-8 Via RHSA-2021:5085 https://access.redhat.com/errata/RHSA-2021:5085
This issue has been addressed in the following products: Red Hat OpenShift Data Foundation 4.9.0 on RHEL-8 Via RHSA-2021:5086 https://access.redhat.com/errata/RHSA-2021:5086
This issue has been addressed in the following products: RHEL-8-CNV-4.9 Via RHSA-2022:0191 https://access.redhat.com/errata/RHSA-2022:0191
This issue has been addressed in the following products: Red Hat OpenStack Platform 16.2 Via RHSA-2022:0237 https://access.redhat.com/errata/RHSA-2022:0237
This issue has been addressed in the following products: Red Hat OpenStack Platform 16.1 Via RHSA-2022:0260 https://access.redhat.com/errata/RHSA-2022:0260
This issue has been addressed in the following products: RHEL-8-CNV-4.10 Via RHSA-2022:0947 https://access.redhat.com/errata/RHSA-2022:0947
This issue has been addressed in the following products: Red Hat OpenStack Platform 16.2 Via RHSA-2022:0998 https://access.redhat.com/errata/RHSA-2022:0998
This issue has been addressed in the following products: Red Hat OpenStack Platform 16.1 Via RHSA-2022:0988 https://access.redhat.com/errata/RHSA-2022:0988
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.10 Via RHSA-2022:0577 https://access.redhat.com/errata/RHSA-2022:0577
This issue has been addressed in the following products: RHEL-8-CNV-4.8 RHEL-7-CNV-4.8 Via RHSA-2022:1329 https://access.redhat.com/errata/RHSA-2022:1329
This issue has been addressed in the following products: RHODF-4.10-RHEL-8 Via RHSA-2022:1372 https://access.redhat.com/errata/RHSA-2022:1372
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2022:7954 https://access.redhat.com/errata/RHSA-2022:7954