Arch Linux Security Advisory ASA-201703-1
========================================
Severity: Low
Date    : 2017-03-03
CVE-ID  : CVE-2017-2629
Package : curl
Type    : insufficient validation
Remote  : Yes
Link    : https://security.archlinux.org/AVG-179

Summary
======
The package curl before version 7.53.0-1 is vulnerable to insufficient
validation.

Resolution
=========
Upgrade to 7.53.0-1.

# pacman -Syu "curl>=7.53.0-1"

The problem has been fixed upstream in version 7.53.0.

Workaround
=========
None.

Description
==========
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.

Impact
=====
This vulnerability 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.

References
=========
https://curl.se/docs/CVE-2017-2629.html
https://security.archlinux.org/CVE-2017-2629

ArchLinux: 201703-1: curl: insufficient validation

March 3, 2017

Summary

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.

Resolution

Upgrade to 7.53.0-1. # pacman -Syu "curl>=7.53.0-1"
The problem has been fixed upstream in version 7.53.0.

References

https://curl.se/docs/CVE-2017-2629.html https://security.archlinux.org/CVE-2017-2629

Severity
Package : curl
Type : insufficient validation
Remote : Yes
Link : https://security.archlinux.org/AVG-179

Workaround

None.

Related News