[3.4] openssl: Multiple vulnerabilities (CVE-2017-3737, CVE-2017-3738)
CVE-2017-3737: Read/write after SSL object in error state
OpenSSL 1.0.2 (starting from version 1.0.2b) introduced an “error
state”
mechanism. The intent was that if a fatal error occurred during a
handshake then
OpenSSL would move into the error state and would immediately fail if
you
attempted to continue the handshake. This works as designed for the
explicit
handshake functions (SSL_do_handshake(), SSL_accept() and
SSL_connect()),
however due to a bug it does not work correctly if SSL_read() or
SSL_write() is
called directly. In that scenario, if the handshake fails then a fatal
error
will be returned in the initial function call. If
SSL_read()/SSL_write() is
subsequently called by the application for the same SSL object then it
will
succeed and the data is passed without being decrypted/encrypted
directly from
the SSL/TLS record layer.
Fixed In:
openssl 1.0.2n
References:
https://www.openssl.org/news/secadv/20171207.txt
CVE-2017-3738: rsaz_1024_mul_avx2 overflow bug on x86_64
There is an overflow bug in the AVX2 Montgomery multiplication
procedure
used in exponentiation with 1024-bit moduli. No EC algorithms are
affected.
Analysis suggests that attacks against RSA and DSA as a result of this
defect
would be very difficult to perform and are not believed likely.
Attacks
against DH1024 are considered just feasible, because most of the work
necessary to deduce information about a private key may be performed
offline.
The amount of resources required for such an attack would be
significant.
Fixed In:
openssl 1.0.2n
References:
https://www.openssl.org/news/secadv/20171207.txt
(from redmine: issue id 8277, created on 2017-12-13, closed on 2017-12-18)
- Relations:
- parent #8260 (closed)
- Changesets:
- Revision b0c3a0f6 on 2017-12-15T08:29:14Z:
main/openssl: security upgrade to 1.0.2n
fixes #8277
CVE-2017-3737
CVE-2017-3738
(cherry picked from commit b74e9ca7e1962c168d79fc1d11039d7febd5b0e6)- Revision 69941fbb on 2018-11-22T15:32:44Z:
main/openssl: security upgrade to 1.0.2n
fixes #8277
CVE-2017-3737
CVE-2017-3738
(cherry picked from commit b74e9ca7e1962c168d79fc1d11039d7febd5b0e6)