Bug 1425746 (CVE-2017-2629) - CVE-2017-2629 curl: SSL_VERIFYSTATUS ignored
Summary: CVE-2017-2629 curl: SSL_VERIFYSTATUS ignored
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2017-2629
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard: impact=moderate,public=20170222,repor...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-22 09:56 UTC by Adam Mariš
Modified: 2019-06-08 21:49 UTC (History)
22 users (show)

Fixed In Version: curl 7.53.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-22 09:58:11 UTC


Attachments (Terms of Use)

Description Adam Mariš 2017-02-22 09:56:17 UTC
A coding mistake was found in TLS Certificate Status Request extension feature that asks for a fresh proof of the server's certificate's validity in the code that checks for a test success or failure. It 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. This flaw also exists in the command line tool (--cert-status).

Affected versions: 7.52.0 to and including 7.52.1
Not affected versions: < 7.52.0 and >= 7.53.0

Upstream patch:

https://curl.haxx.se/CVE-2017-2629.patch

External References:

https://curl.haxx.se/docs/adv_20170222.html

Comment 1 Adam Mariš 2017-02-22 09:58:11 UTC
Acknowledgments:

Name: the Curl project
Upstream: Marcus Hoffmann

Comment 2 Kamil Dudka 2017-02-22 15:33:01 UTC
Luckily, this bug has never reached any stable release of Fedora.  Rawhide is fixed since curl-7.53.0-1.fc26 via:

http://pkgs.fedoraproject.org/cgit/rpms/curl.git/commit/?id=8afeb939


Note You need to log in before you can comment on or make changes to this bug.