October 9, 2021

Release Notes for Symas OpenLDAP Gold, Version 2.4.59.4

This release of Symas OpenLDAP contains the following component versions:

OpenLDAP 2.4.59
Cyrus SASL 2.1.26
OpenSSL 1.1.1l
GPerftools 2.7.0 (Select platforms)
Heimdal Kerberos 7.7.0 (Select platforms)
Kstart 4.2 (Select platforms)
libsodium 1.0.18

Summary of Changes:
OpenLDAP:
Post 2.4.59 Updates:
Fixed slapd slaptest migration to correctly set olcTSLVerifyClient (ITS#9711)
Fixed slapd-mdb multival delete handling (ITS#9712)
Fixed slapo-ppolicy and slapo-ppolicy10 logging when pwdChangedTime attribute is not present (ITS#9625)
Fixed slapo-ppolicy10 to restore OpenLDAP 2.4 compatibility (ITS#9671)

Cyrus SASL:
No changes

OpenSSL:
No changes

Heimdal Kerberos:
No changes

GPerfTools:
No changes

Libtool:
No changes

Libsodium:
No changes

Status of this release:

This is a production release and is made available for general use. We have tested it in our labs and in the field and we believe it is suitable for use in production  environments. However, as is always the case with any software, please test it in your own environment to make sure it meets your requirements, maintain backups of critical data, and make appropriate provisions for unexpected outages.

Bug reports, comments, and suggestions can be submitted to support@symas.com. We look forward to hearing from you!

August 26, 2021

Release Notes for Symas OpenLDAP Gold, Version 2.4.59.3

This release of Symas OpenLDAP contains the following component versions:

OpenLDAP 2.4.59
Cyrus SASL 2.1.26
OpenSSL 1.1.1l
GPerftools 2.7.0 (Select platforms)
Heimdal Kerberos 7.7.0 (Select platforms)
Kstart 4.2 (Select platforms)
libsodium 1.0.18

Summary of Changes:
OpenLDAP:
Post 2.4.59 Updates:
Fixed slapo-accesslog to make reqMod optional (ITS#9569

Cyrus SASL:
No changes

OpenSSL:
OpenSSL 1.1.1l:
SM2 Decryption Buffer Overflow (CVE-2021-3711)
==============================================

Severity: High

In order to decrypt SM2 encrypted data an application is expected to call the
API function EVP_PKEY_decrypt(). Typically an application will call this
function twice. The first time, on entry, the “out” parameter can be NULL and,
on exit, the “outlen” parameter is populated with the buffer size required to
hold the decrypted plaintext. The application can then allocate a sufficiently
sized buffer and call EVP_PKEY_decrypt() again, but this time passing a non-NULL
value for the “out” parameter.

A bug in the implementation of the SM2 decryption code means that the
calculation of the buffer size required to hold the plaintext returned by the
first call to EVP_PKEY_decrypt() can be smaller than the actual size required by
the second call. This can lead to a buffer overflow when EVP_PKEY_decrypt() is
called by the application a second time with a buffer that is too small.

A malicious attacker who is able present SM2 content for decryption to an
application could cause attacker chosen data to overflow the buffer by up to a
maximum of 62 bytes altering the contents of other data held after the
buffer, possibly changing application behaviour or causing the application to
crash. The location of the buffer is application dependent but is typically
heap allocated.

OpenSSL versions 1.1.1k and below are affected by this issue. Users of these
versions should upgrade to OpenSSL 1.1.1l.

Read buffer overruns processing ASN.1 strings (CVE-2021-3712)
=============================================================

Severity: Moderate

ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING
structure which contains a buffer holding the string data and a field holding
the buffer length. This contrasts with normal C strings which are repesented as
a buffer for the string data which is terminated with a NUL (0) byte.

Although not a strict requirement, ASN.1 strings that are parsed using OpenSSL’s
own “d2i” functions (and other similar parsing functions) as well as any string
whose value has been set with the ASN1_STRING_set() function will additionally
NUL terminate the byte array in the ASN1_STRING structure.

However, it is possible for applications to directly construct valid ASN1_STRING
structures which do not NUL terminate the byte array by directly setting the
“data” and “length” fields in the ASN1_STRING array. This can also happen by
using the ASN1_STRING_set0() function.

Numerous OpenSSL functions that print ASN.1 data have been found to assume that
the ASN1_STRING byte array will be NUL terminated, even though this is not
guaranteed for strings that have been directly constructed. Where an application
requests an ASN.1 structure to be printed, and where that ASN.1 structure
contains ASN1_STRINGs that have been directly constructed by the application
without NUL terminating the “data” field, then a read buffer overrun can occur.

The same thing can also occur during name constraints processing of certificates
(for example if a certificate has been directly constructed by the application
instead of loading it via the OpenSSL parsing functions, and the certificate
contains non NUL terminated ASN1_STRING structures). It can also occur in the
X509_get1_email(), X509_REQ_get1_email() and X509_get1_ocsp() functions.

If a malicious actor can cause an application to directly construct an
ASN1_STRING and then process it through one of the affected OpenSSL functions
then this issue could be hit. This might result in a crash (causing a Denial of
Service attack). It could also result in the disclosure of private memory
contents (such as private keys, or sensitive plaintext).

Heimdal Kerberos:
No changes

GPerfTools:
No changes

Libtool:
No changes

Libsodium:
No changes

Status of this release:

This is a production release and is made available for general use. We have tested it in our labs and in the field and we believe it is suitable for use in production  environments. However, as is always the case with any software, please test it in your own environment to make sure it meets your requirements, maintain backups of critical data, and make appropriate provisions for unexpected outages.

Bug reports, comments, and suggestions can be submitted to support@symas.com. We look forward to hearing from you!