CVE-2017-2629 log

Severity Low
Remote Yes
Type Insufficient validation
A coding error has been found in curl >= 7.52.0 and < 7.53.0, causing the TLS Certificate Status Request extension check to always return true.
curl and libcurl support "OCSP stapling", also known as the TLS Certificate Status Request extension (using the CURLOPT_SSL_VERIFYSTATUS option). When telling curl to use this feature, it uses that TLS extension to ask for a fresh proof of the server's certificate's validity. If the server doesn't support the extension, or fails to provide said proof, curl is expected to return an error.
Due to a coding mistake, the code that checks for a test success or failure, ends up always thinking there's valid proof, even when there is none or if the server doesn't support the TLS extension in question. Contrary to how it used to function and contrary to how this feature is documented to work.
This could lead to users not detecting when a server's certificate goes invalid or otherwise be mislead that the server is in a better shape than it is in reality.
Group Package Affected Fixed Severity Status Ticket
AVG-184 lib32-libcurl-gnutls 7.52.1-2 7.53.0-1 Medium Fixed
AVG-183 lib32-libcurl-compat 7.52.1-2 7.53.0-1 Medium Fixed
AVG-182 lib32-curl 7.52.1-1 7.53.0-1 Low Fixed
AVG-181 libcurl-gnutls 7.52.1-1 7.53.0-1 Medium Fixed
AVG-180 libcurl-compat 7.52.1-1 7.53.0-1 Medium Fixed
AVG-179 curl 7.52.1-2 7.53.0-1 Low Fixed
Date Advisory Group Package Severity Type
03 Mar 2017 ASA-201703-1 AVG-179 curl Low insufficient validation