CURL-CVE-2016-9952

vendorUSosv

Win CE Schannel cert wildcard matches too much

view advisory published 2016-12-21Licence: per source

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.

01

describes (1)

Related CVEs.

IDseverity exploitable
CVE-2016-9952UShigh8.1—
The verify_certificate function in lib/vtls/schannel.c in libcurl 7.30.0 through 7.51.0, when built for Windows CE using the schannel TLS backend, makes it easier for remote attack…
scry

Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.

Free scan