All Versions
126
Latest Version
Avg Release Cycle
101 days
Latest Release
800 days ago

Changelog History
Page 5

  • v1.0.2.c Changes

    July 09, 2015
    • Alternate chains certificate forgery

    During certificate verification, OpenSSL will attempt to find an alternative certificate chain if the first attempt to build such a chain fails. An error in the implementation of this logic can mean that an attacker could cause certain checks on untrusted certificates to be bypassed, such as the CA flag, enabling them to use a valid leaf certificate to act as a CA and "issue" an invalid certificate.

    This issue was reported to OpenSSL by Adam Langley/David Benjamin (Google/BoringSSL).

    Matt Caswell

  • v1.0.2.b Changes

    June 12, 2015
    • Fix HMAC ABI incompatibility. The previous version introduced an ABI incompatibility in the handling of HMAC. The previous ABI has now been restored.

    Matt Caswell

  • v1.0.2.a Changes

    June 11, 2015
    • Malformed ECParameters causes infinite loop

    When processing an ECParameters structure OpenSSL enters an infinite loop if the curve specified is over a specially malformed binary polynomial field.

    This can be used to perform denial of service against any system which processes public keys, certificate requests or certificates. This includes TLS clients and TLS servers with client authentication enabled.

    This issue was reported to OpenSSL by Joseph Barr-Pixton. [CVE-2015-1788][]

    Andy Polyakov

    • Exploitable out-of-bounds read in X509_cmp_time

    X509_cmp_time does not properly check the length of the ASN1_TIME string and can read a few bytes out of bounds. In addition, X509_cmp_time accepts an arbitrary number of fractional seconds in the time string.

    An attacker can use this to craft malformed certificates and CRLs of various sizes and potentially cause a segmentation fault, resulting in a DoS on applications that verify certificates or CRLs. TLS clients that verify CRLs are affected. TLS clients and servers with client authentication enabled may be affected if they use custom verification callbacks.

    This issue was reported to OpenSSL by Robert Swiecki (Google), and independently by Hanno Böck. [CVE-2015-1789][]

    Emilia Käsper

    • PKCS7 crash with missing EnvelopedContent

    The PKCS#7 parsing code does not handle missing inner EncryptedContent correctly. An attacker can craft malformed ASN.1-encoded PKCS#7 blobs with missing content and trigger a NULL pointer dereference on parsing.

    Applications that decrypt PKCS#7 data or otherwise parse PKCS#7 structures from untrusted sources are affected. OpenSSL clients and servers are not affected.

    This issue was reported to OpenSSL by Michal Zalewski (Google). [CVE-2015-1790][]

    Emilia Käsper

    • CMS verify infinite loop with unknown hash function

    When verifying a signedData message the CMS code can enter an infinite loop if presented with an unknown hash function OID. This can be used to perform denial of service against any system which verifies signedData messages using the CMS code. This issue was reported to OpenSSL by Johannes Bauer. [CVE-2015-1792][]

    Stephen Henson

    • Race condition handling NewSessionTicket

    If a NewSessionTicket is received by a multi-threaded client when attempting to reuse a previous ticket then a race condition can occur potentially leading to a double free of the ticket data. [CVE-2015-1791][]

    Matt Caswell

    • Only support 256-bit or stronger elliptic curves with the 'ecdh_auto' setting (server) or by default (client). Of supported curves, prefer P-256 (both).

    Emilia Kasper

  • v1.0.1.t Changes

    September 22, 2016
    • OCSP Status Request extension unbounded memory growth

    A malicious client can send an excessively large OCSP Status Request extension. If that client continually requests renegotiation, sending a large OCSP Status Request extension each time, then there will be unbounded memory growth on the server. This will eventually lead to a Denial Of Service attack through memory exhaustion. Servers with a default configuration are vulnerable even if they do not support OCSP. Builds using the "no-ocsp" build time option are not affected.

    This issue was reported to OpenSSL by Shi Lei (Gear Team, Qihoo 360 Inc.) [CVE-2016-6304][]

    Matt Caswell

    • In order to mitigate the SWEET32 attack, the DES ciphers were moved from HIGH to MEDIUM.

    This issue was reported to OpenSSL Karthikeyan Bhargavan and Gaetan Leurent (INRIA) [CVE-2016-2183][]

    Rich Salz

    • OOB write in MDC2_Update()

    An overflow can occur in MDC2_Update() either if called directly or through the EVP_DigestUpdate() function using MDC2. If an attacker is able to supply very large amounts of input data after a previous call to EVP_EncryptUpdate() with a partial block then a length check can overflow resulting in a heap corruption.

    The amount of data needed is comparable to SIZE_MAX which is impractical on most platforms.

    This issue was reported to OpenSSL by Shi Lei (Gear Team, Qihoo 360 Inc.) [CVE-2016-6303][]

    Stephen Henson

    • Malformed SHA512 ticket DoS

    If a server uses SHA512 for TLS session ticket HMAC it is vulnerable to a DoS attack where a malformed ticket will result in an OOB read which will ultimately crash.

    The use of SHA512 in TLS session tickets is comparatively rare as it requires a custom server callback and ticket lookup mechanism.

    This issue was reported to OpenSSL by Shi Lei (Gear Team, Qihoo 360 Inc.) [CVE-2016-6302][]

    Stephen Henson

    • OOB write in BN_bn2dec()

    The function BN_bn2dec() does not check the return value of BN_div_word(). This can cause an OOB write if an application uses this function with an overly large BIGNUM. This could be a problem if an overly large certificate or CRL is printed out from an untrusted source. TLS is not affected because record limits will reject an oversized certificate before it is parsed.

    This issue was reported to OpenSSL by Shi Lei (Gear Team, Qihoo 360 Inc.) [CVE-2016-2182][]

    Stephen Henson

    • OOB read in TS_OBJ_print_bio()

    The function TS_OBJ_print_bio() misuses OBJ_obj2txt(): the return value is the total length the OID text representation would use and not the amount of data written. This will result in OOB reads when large OIDs are presented.

    This issue was reported to OpenSSL by Shi Lei (Gear Team, Qihoo 360 Inc.) [CVE-2016-2180][]

    Stephen Henson

    • Pointer arithmetic undefined behaviour

    Avoid some undefined pointer arithmetic

    A common idiom in the codebase is to check limits in the following manner: "p + len > limit"

    Where "p" points to some malloc'd data of SIZE bytes and limit == p + SIZE

    "len" here could be from some externally supplied data (e.g. from a TLS message).

    The rules of C pointer arithmetic are such that "p + len" is only well defined where len <= SIZE. Therefore the above idiom is actually undefined behaviour.

    For example this could cause problems if some malloc implementation provides an address for "p" such that "p + len" actually overflows for values of len that are too big and therefore p + len < limit.

    This issue was reported to OpenSSL by Guido Vranken [CVE-2016-2177][]

    Matt Caswell

    • Constant time flag not preserved in DSA signing

    Operations in the DSA signing algorithm should run in constant time in order to avoid side channel attacks. A flaw in the OpenSSL DSA implementation means that a non-constant time codepath is followed for certain operations. This has been demonstrated through a cache-timing attack to be sufficient for an attacker to recover the private DSA key.

    This issue was reported by César Pereida (Aalto University), Billy Brumley (Tampere University of Technology), and Yuval Yarom (The University of Adelaide and NICTA). [CVE-2016-2178][]

    César Pereida

    • DTLS buffered message DoS

    In a DTLS connection where handshake messages are delivered out-of-order those messages that OpenSSL is not yet ready to process will be buffered for later use. Under certain circumstances, a flaw in the logic means that those messages do not get removed from the buffer even though the handshake has been completed. An attacker could force up to approx. 15 messages to remain in the buffer when they are no longer required. These messages will be cleared when the DTLS connection is closed. The default maximum size for a message is 100k. Therefore the attacker could force an additional 1500k to be consumed per connection. By opening many simulataneous connections an attacker could cause a DoS attack through memory exhaustion.

    This issue was reported to OpenSSL by Quan Luo. [CVE-2016-2179][]

    Matt Caswell

    • DTLS replay protection DoS

    A flaw in the DTLS replay attack protection mechanism means that records that arrive for future epochs update the replay protection "window" before the MAC for the record has been validated. This could be exploited by an attacker by sending a record for the next epoch (which does not have to decrypt or have a valid MAC), with a very large sequence number. This means that all subsequent legitimate packets are dropped causing a denial of service for a specific DTLS connection.

    This issue was reported to OpenSSL by the OCAP audit team. [CVE-2016-2181][]

    Matt Caswell

    • Certificate message OOB reads

    In OpenSSL 1.0.2 and earlier some missing message length checks can result in OOB reads of up to 2 bytes beyond an allocated buffer. There is a theoretical DoS risk but this has not been observed in practice on common platforms.

    The messages affected are client certificate, client certificate request and server certificate. As a result the attack can only be performed against a client or a server which enables client authentication.

    This issue was reported to OpenSSL by Shi Lei (Gear Team, Qihoo 360 Inc.) [CVE-2016-6306][]

    Stephen Henson

  • v1.0.1.s Changes

    May 03, 2016
    • Prevent padding oracle in AES-NI CBC MAC check

    A MITM attacker can use a padding oracle attack to decrypt traffic when the connection uses an AES CBC cipher and the server support AES-NI.

    This issue was introduced as part of the fix for Lucky 13 padding attack [CVE-2013-0169][]. The padding check was rewritten to be in constant time by making sure that always the same bytes are read and compared against either the MAC or padding bytes. But it no longer checked that there was enough data to have both the MAC and padding bytes.

    This issue was reported by Juraj Somorovsky using TLS-Attacker. [CVE-2016-2107][]

    Kurt Roeckx

    • Fix EVP_EncodeUpdate overflow

    An overflow can occur in the EVP_EncodeUpdate() function which is used for Base64 encoding of binary data. If an attacker is able to supply very large amounts of input data then a length check can overflow resulting in a heap corruption.

    Internally to OpenSSL the EVP_EncodeUpdate() function is primarly used by the PEM_write_bio* family of functions. These are mainly used within the OpenSSL command line applications, so any application which processes data from an untrusted source and outputs it as a PEM file should be considered vulnerable to this issue. User applications that call these APIs directly with large amounts of untrusted data may also be vulnerable.

    This issue was reported by Guido Vranken. [CVE-2016-2105][]

    Matt Caswell

    • Fix EVP_EncryptUpdate overflow

    An overflow can occur in the EVP_EncryptUpdate() function. If an attacker is able to supply very large amounts of input data after a previous call to EVP_EncryptUpdate() with a partial block then a length check can overflow resulting in a heap corruption. Following an analysis of all OpenSSL internal usage of the EVP_EncryptUpdate() function all usage is one of two forms. The first form is where the EVP_EncryptUpdate() call is known to be the first called function after an EVP_EncryptInit(), and therefore that specific call must be safe. The second form is where the length passed to EVP_EncryptUpdate() can be seen from the code to be some small value and therefore there is no possibility of an overflow. Since all instances are one of these two forms, it is believed that there can be no overflows in internal code due to this problem. It should be noted that EVP_DecryptUpdate() can call EVP_EncryptUpdate() in certain code paths. Also EVP_CipherUpdate() is a synonym for EVP_EncryptUpdate(). All instances of these calls have also been analysed too and it is believed there are no instances in internal usage where an overflow could occur.

    This issue was reported by Guido Vranken. [CVE-2016-2106][]

    Matt Caswell

    • Prevent ASN.1 BIO excessive memory allocation

    When ASN.1 data is read from a BIO using functions such as d2i_CMS_bio() a short invalid encoding can casuse allocation of large amounts of memory potentially consuming excessive resources or exhausting memory.

    Any application parsing untrusted data through d2i BIO functions is affected. The memory based functions such as d2i_X509() are not affected. Since the memory based functions are used by the TLS library, TLS applications are not affected.

    This issue was reported by Brian Carpenter. [CVE-2016-2109][]

    Stephen Henson

    • EBCDIC overread

    ASN1 Strings that are over 1024 bytes can cause an overread in applications using the X509_NAME_oneline() function on EBCDIC systems. This could result in arbitrary stack data being returned in the buffer.

    This issue was reported by Guido Vranken. [CVE-2016-2176][]

    Matt Caswell

    • Modify behavior of ALPN to invoke callback after SNI/servername callback, such that updates to the SSL_CTX affect ALPN.

    Todd Short

    • Remove LOW from the DEFAULT cipher list. This removes singles DES from the default.

    Kurt Roeckx

    • Only remove the SSLv2 methods with the no-ssl2-method option. When the methods are enabled and ssl2 is disabled the methods return NULL.

    Kurt Roeckx

  • v1.0.1.r Changes

    March 01, 2016
    • 🏗 Disable weak ciphers in SSLv3 and up in default builds of OpenSSL. Builds that are not configured with "enable-weak-ssl-ciphers" will not provide any "EXPORT" or "LOW" strength ciphers.

    Viktor Dukhovni

    • 🏗 Disable SSLv2 default build, default negotiation and weak ciphers. SSLv2 is by default disabled at build-time. Builds that are not configured with "enable-ssl2" will not support SSLv2. Even if "enable-ssl2" is used, users who want to negotiate SSLv2 via the version-flexible SSLv23_method() will need to explicitly call either of:

      SSL_CTX_clear_options(ctx, SSL_OP_NO_SSLv2); or SSL_clear_options(ssl, SSL_OP_NO_SSLv2);

    as appropriate. Even if either of those is used, or the application explicitly uses the version-specific SSLv2_method() or its client and server variants, SSLv2 ciphers vulnerable to exhaustive search key recovery have been removed. Specifically, the SSLv2 40-bit EXPORT ciphers, and SSLv2 56-bit DES are no longer available. ([CVE-2016-0800])

    Viktor Dukhovni

    • Fix a double-free in DSA code

    A double free bug was discovered when OpenSSL parses malformed DSA private keys and could lead to a DoS attack or memory corruption for applications that receive DSA private keys from untrusted sources. This scenario is considered rare.

    This issue was reported to OpenSSL by Adam Langley(Google/BoringSSL) using libFuzzer. ([CVE-2016-0705])

    Stephen Henson

    • Disable SRP fake user seed to address a server memory leak.

    Add a new method SRP_VBASE_get1_by_user that handles the seed properly.

    SRP_VBASE_get_by_user had inconsistent memory management behaviour. In order to fix an unavoidable memory leak, SRP_VBASE_get_by_user was changed to ignore the "fake user" SRP seed, even if the seed is configured.

    Users should use SRP_VBASE_get1_by_user instead. Note that in SRP_VBASE_get1_by_user, caller must free the returned value. Note also that even though configuring the SRP seed attempts to hide invalid usernames by continuing the handshake with fake credentials, this behaviour is not constant time and no strong guarantees are made that the handshake is indistinguishable from that of a valid user. ([CVE-2016-0798])

    Emilia Käsper

    • Fix BN_hex2bn/BN_dec2bn NULL pointer deref/heap corruption

    In the BN_hex2bn function the number of hex digits is calculated using an int value i. Later bn_expand is called with a value of i * 4. For large values of i this can result in bn_expand not allocating any memory because i * 4 is negative. This can leave the internal BIGNUM data field as NULL leading to a subsequent NULL ptr deref. For very large values of i, the calculation i * 4 could be a positive value smaller than i. In this case memory is allocated to the internal BIGNUM data field, but it is insufficiently sized leading to heap corruption. A similar issue exists in BN_dec2bn. This could have security consequences if BN_hex2bn/BN_dec2bn is ever called by user applications with very large untrusted hex/dec data. This is anticipated to be a rare occurrence.

    All OpenSSL internal usage of these functions use data that is not expected to be untrusted, e.g. config file data or application command line arguments. If user developed applications generate config file data based on untrusted data then it is possible that this could also lead to security consequences. This is also anticipated to be rare.

    This issue was reported to OpenSSL by Guido Vranken. ([CVE-2016-0797])

    Matt Caswell

    • Fix memory issues in BIO_*printf functions

    The internal fmtstr function used in processing a "%s" format string in the BIO_*printf functions could overflow while calculating the length of a string and cause an OOB read when printing very long strings.

    Additionally the internal doapr_outch function can attempt to write to an OOB memory location (at an offset from the NULL pointer) in the event of a memory allocation failure. In 1.0.2 and below this could be caused where the size of a buffer to be allocated is greater than INT_MAX. E.g. this could be in processing a very long "%s" format string. Memory leaks can also occur.

    The first issue may mask the second issue dependent on compiler behaviour. These problems could enable attacks where large amounts of untrusted data is passed to the BIO_*printf functions. If applications use these functions in this way then they could be vulnerable. OpenSSL itself uses these functions when printing out human-readable dumps of ASN.1 data. Therefore applications that print this data could be vulnerable if the data is from untrusted sources. OpenSSL command line applications could also be vulnerable where they print out ASN.1 data, or if untrusted data is passed as command line arguments.

    Libssl is not considered directly vulnerable. Additionally certificates etc received via remote connections via libssl are also unlikely to be able to trigger these issues because of message size limits enforced within libssl.

    This issue was reported to OpenSSL Guido Vranken. ([CVE-2016-0799])

    Matt Caswell

    • Side channel attack on modular exponentiation

    A side-channel attack was found which makes use of cache-bank conflicts on the Intel Sandy-Bridge microarchitecture which could lead to the recovery of RSA keys. The ability to exploit this issue is limited as it relies on an attacker who has control of code in a thread running on the same hyper-threaded core as the victim thread which is performing decryptions.

    This issue was reported to OpenSSL by Yuval Yarom, The University of Adelaide and NICTA, Daniel Genkin, Technion and Tel Aviv University, and Nadia Heninger, University of Pennsylvania with more information at http://cachebleed.info. ([CVE-2016-0702])

    Andy Polyakov

    • Change the req command to generate a 2048-bit RSA/DSA key by default, if no keysize is specified with default_bits. This fixes an omission in an earlier change that changed all RSA/DSA key generation commands to use 2048 bits by default.

    Emilia Käsper

  • v1.0.1.q Changes

    January 28, 2016
    • Protection for DH small subgroup attacks

    As a precautionary measure the SSL_OP_SINGLE_DH_USE option has been switched on by default and cannot be disabled. This could have some performance impact.

    Matt Caswell

    • SSLv2 doesn't block disabled ciphers

    A malicious client can negotiate SSLv2 ciphers that have been disabled on the server and complete SSLv2 handshakes even if all SSLv2 ciphers have been disabled, provided that the SSLv2 protocol was not also disabled via SSL_OP_NO_SSLv2.

    This issue was reported to OpenSSL on 26th December 2015 by Nimrod Aviram and Sebastian Schinzel. [CVE-2015-3197][]

    Viktor Dukhovni

    • Reject DH handshakes with parameters shorter than 1024 bits.

    Kurt Roeckx

  • v1.0.1.p Changes

    December 03, 2015
    • Certificate verify crash with missing PSS parameter

    The signature verification routines will crash with a NULL pointer dereference if presented with an ASN.1 signature using the RSA PSS algorithm and absent mask generation function parameter. Since these routines are used to verify certificate signature algorithms this can be used to crash any certificate verification operation and exploited in a DoS attack. Any application which performs certificate verification is vulnerable including OpenSSL clients and servers which enable client authentication.

    This issue was reported to OpenSSL by Loïc Jonas Etienne (Qnective AG). [CVE-2015-3194][]

    Stephen Henson

    • X509_ATTRIBUTE memory leak

    When presented with a malformed X509_ATTRIBUTE structure OpenSSL will leak memory. This structure is used by the PKCS#7 and CMS routines so any application which reads PKCS#7 or CMS data from untrusted sources is affected. SSL/TLS is not affected.

    This issue was reported to OpenSSL by Adam Langley (Google/BoringSSL) using libFuzzer. [CVE-2015-3195][]

    Stephen Henson

    • Rewrite EVP_DecodeUpdate (base64 decoding) to fix several bugs. This changes the decoding behaviour for some invalid messages, though the change is mostly in the more lenient direction, and legacy behaviour is preserved as much as possible.

    Emilia Käsper

    • In DSA_generate_parameters_ex, if the provided seed is too short, use a random seed, as already documented.

    Rich Salz and Ismo Puustinen [email protected]

  • v1.0.1.o Changes

    July 09, 2015
    • Alternate chains certificate forgery

    During certificate verfification, OpenSSL will attempt to find an alternative certificate chain if the first attempt to build such a chain fails. An error in the implementation of this logic can mean that an attacker could cause certain checks on untrusted certificates to be bypassed, such as the CA flag, enabling them to use a valid leaf certificate to act as a CA and "issue" an invalid certificate.

    This issue was reported to OpenSSL by Adam Langley/David Benjamin (Google/BoringSSL). [CVE-2015-1793][]

    Matt Caswell

    • Race condition handling PSK identify hint

    If PSK identity hints are received by a multi-threaded client then the values are wrongly updated in the parent SSL_CTX structure. This can result in a race condition potentially leading to a double free of the identify hint data. [CVE-2015-3196][]

    Stephen Henson

  • v1.0.1.n Changes

    June 12, 2015
    • Fix HMAC ABI incompatibility. The previous version introduced an ABI incompatibility in the handling of HMAC. The previous ABI has now been restored.