Improper Validation of Certificate with Host Mismatch vulnerability in Apache Thrift.
This issue affects Apache Thrift: before 0.23.0.
Users are recommended to upgrade to version 0.23.0, which fixes the issue.
Weakness
The product communicates with a host that provides a certificate, but the product does not properly ensure that the certificate is actually associated with that host.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Thrift | Apache | * | 0.23.0 (excluding) |
| Cryostat 4 on RHEL 9 | RedHat | cryostat/cryostat-storage-rhel9:4.2.0-16 | * |
| Red Hat Build of Apache Camel 3.33 for Quarkus 3.33.2.SP1 | RedHat | libthrift | * |
| Multicluster Global Hub 1.3.4 | RedHat | multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1779212259 | * |
| Multicluster Global Hub 1.4.5 | RedHat | multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1779579439 | * |
| Multicluster Global Hub 1.5.4 | RedHat | multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1778867753 | * |
| Multicluster Global Hub 1.6.2 | RedHat | multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1780167118 | * |
| Multicluster Global Hub 1.7.1 | RedHat | multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1779925273 | * |
| Red Hat Advanced Cluster Management for Kubernetes 2.13 | RedHat | rhacm2/acm-grafana-rhel9:1782383730 | * |
| Red Hat Advanced Cluster Management for Kubernetes 2.15 | RedHat | rhacm2/acm-grafana-rhel9:1780677003 | * |
| Red Hat Advanced Cluster Management for Kubernetes 2.16 | RedHat | rhacm2/acm-grafana-rhel9:1780926805 | * |
| Red Hat OpenShift distributed tracing 3.10.0 | RedHat | rhosdt/tempo-rhel9:1781589494 | * |
Extended Description
Even if a certificate is well-formed, signed, and follows the chain of trust, it may simply be a valid certificate for a different site than the site that the product is interacting with. In order to ensure data integrity, the certificate must be valid, and it must pertain to the site that is being accessed. Even if the product attempts to check the hostname, it is still possible to incorrectly check the hostname. For example, attackers could create a certificate with a name that begins with a trusted name followed by a NUL byte, which could cause some string-based comparisons to only examine the portion that contains the trusted name.