Vulnerability
curl/libcurl: Win CE Schannel cert wildcard matches too much
curl's TLS server certificate checks are flawed on Windows CE. This vulnerability occurs in the verify certificate function when comparing a wildcard certificate name (as returned by the Windows API function `CertGetNameString)` to the hostname used to make the connection to the server. The vulnerability can be triggered with an overly permissive wildcard SAN in the server certificate such as a DNS name of `*.com`. When the function compares the cert name to the connection hostname, the wildcard character is removed from the cert name and the connection hostname is checked to see if it ends with the modified cert name. This means a hostname of example.com would match a DNS SAN of `*.com`, among other variations. This approach violates recommendations in RFC 6125 and could lead to MITM attacks.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HLow exploitation likelihood — defer if no other signals fire.
No VEX statements published for CVE-2016-9952. Vendors publish VEX (Vulnerability Exploitability eXchange) to assert per-product whether a CVE is actually exploitable in their distribution.
Total impact on non-trivial mission systems