It has been discovered that the client-side TLS implementation in Fossil was often failing to verify that the hostname of the server matched the hostname contained in the TLS certificate. Hence, an "https" connection would always work as long as the server returned any valid certificate, even if that certificate did not match the hostname. Reference: https://fossil-scm.org/forum/forumpost/8d367e16f53d93c789d70bd3bf2c9587227bbd5c6a7b8e512cccd79007536036
Created fossil tracking bugs for this issue: Affects: fedora-all [bug 1980049]
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.