curl supports matching of wildcard patterns when listed as "Subject Alternative Name" in TLS server certificates. curl can be built to use its own name matching function for TLS rather than one provided by a TLS library. This private wildcard matching function would match IDN (International Domain Name) hosts incorrectly and could as a result accept patterns that otherwise should mismatch. IDN hostnames are converted to puny code before used for certificate checks. Puny coded names always start with `xn--` and should not be allowed to pattern match, but the wildcard check in curl could still check for `x*`, which would match even though the IDN name most likely contained nothing even resembling an `x`.
Created curl tracking bugs for this issue: Affects: fedora-all [bug 2207899] Created mingw-curl tracking bugs for this issue: Affects: fedora-all [bug 2207900]
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2023:4354 https://access.redhat.com/errata/RHSA-2023:4354
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2023:4523 https://access.redhat.com/errata/RHSA-2023:4523
This issue has been addressed in the following products: Red Hat JBoss Core Services Via RHSA-2023:4628 https://access.redhat.com/errata/RHSA-2023:4628
This issue has been addressed in the following products: JBoss Core Services on RHEL 7 JBoss Core Services for RHEL 8 Via RHSA-2023:4629 https://access.redhat.com/errata/RHSA-2023:4629
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.0 Extended Update Support Via RHSA-2023:5598 https://access.redhat.com/errata/RHSA-2023:5598
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.6 Extended Update Support Via RHSA-2023:6292 https://access.redhat.com/errata/RHSA-2023:6292