From $URL: 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. This flaw also exists in the command line tool (--cert-status). We are not aware of any exploit of this flaw.
@ Maintainer(s): Can we already start stabilization of =net-misc/curl-7.53.0?
(In reply to Thomas Deutschmann from comment #1) > @ Maintainer(s): Can we already start stabilization of =net-misc/curl-7.53.0? Yes. KEYWORDS="alpha amd64 arm hppa ia64 ppc ppc64 sparc x86"
ppc64 stable
arm ppc stable.
Stable for HPPA.
amd64 stable
x86 stable
sparc stable
Stable on alpha.
ia64 please complete stabilization. GLSA Vote: Yes Starting GLSA writing process.
ia64 stable. Maintainer(s), please cleanup.
This issue was resolved and addressed in GLSA 201703-04 at https://security.gentoo.org/glsa/201703-04 by GLSA coordinator Yury German (BlueKnight).
Re Opening for cleanup. Maintainer(s), please drop the vulnerable version(s).
Maintainer(s), please drop the vulnerable version(s).
Cleanup PR: https://github.com/gentoo/gentoo/pull/4846
Repository is now clean, all done.
