#14363: curl-7.74.0
-------------------------+-----------------------
 Reporter:  renodr       |       Owner:  renodr
     Type:  enhancement  |      Status:  assigned
 Priority:  high         |   Milestone:  10.1
Component:  BOOK         |     Version:  SVN
 Severity:  normal       |  Resolution:
 Keywords:               |
-------------------------+-----------------------
Changes (by renodr):

 * owner:  blfs-book => renodr
 * priority:  normal => high
 * status:  new => assigned


Comment:

 '''cURL Security Advisory for CVE-2020-8286'''

 {{{
 Inferior OCSP verification
 ==========================

 Project curl Security Advisory, December 9th 2020 -
 [Permalink](https://curl.se/docs/CVE-2020-8286.html)

 VULNERABILITY
 -------------

 libcurl offers "OCSP stapling" via the `CURLOPT_SSL_VERIFYSTATUS` option.
 When
 set, libcurl verifies the OCSP response that a server responds with as
 part of
 the TLS handshake. It then aborts the TLS negotiation if something is
 wrong
 with the response. The same feature can be enabled with `--cert-status`
 using
 the curl tool.

 As part of the OCSP response verification, a client should verify that the
 response is indeed set out for the correct certificate. This step was not
 performed by libcurl when built or told to use OpenSSL as TLS backend.

 This flaw would allow an attacker, who perhaps could have breached a TLS
 server, to provide a fraudulent OCSP response that would appear fine,
 instead
 of the real one. Like if the original certificate actually has been
 revoked.

 We are not aware of any exploit of this flaw.

 INFO
 ----

 This flaw has existed in curl since commit
 [d1cf5d570663d](https://github.com/curl/curl/commit/d1cf5d570663d) in curl
 7.41.0.

 The vulnerability is present only if OpenSSL is the designated TLS
 backend.
 OCSP stapling is not enabled by default by libcurl, it needs to be
 explicitly
 enabled by the application to get used.

 OCSP Stapling can be used with any of the TLS based protocols curl
 supports,
 including HTTPS, FTPS, SMTPS, POP3S, IMAPS, HTTPS-proxy and more.

 The Common Vulnerabilities and Exposures (CVE) project has assigned the
 name
 CVE-2020-8286 to this issue.

 CWE-299: Improper Check for Certificate Revocation

 Severity: Medium

 AFFECTED VERSIONS
 -----------------

 - Affected versions: libcurl 7.41.0 to and including 7.73.0
 - Not affected versions: libcurl < 7.41.0 and libcurl >= 7.74.0

 Also note that libcurl is used by many applications, and not always
 advertised as such.

 THE SOLUTION
 ------------

 The OCSP response checker function now also verifies that the certificate
 id
 is the correct one.

 A [fix for
 CVE-2020-8286](https://github.com/curl/curl/commit/d9d01672785b)

 RECOMMENDATIONS
 --------------

 We suggest you take one of the following actions immediately, in order of
 preference:

  A - Upgrade curl to version 7.74.0

  B - Don't rely on OCSP

 TIMELINE
 --------

 This issue was first reported to the curl project on December 2, 2020.

 This advisory was posted on December 9th 2020.
 }}}

--
Ticket URL: <http://wiki.linuxfromscratch.org/blfs/ticket/14363#comment:4>
BLFS Trac <http://wiki.linuxfromscratch.org/blfs>
Beyond Linux From Scratch
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to