QID 354907

an issue was discovered in openldap 2.x before 2.4.48.
When using sasl authentication and session encryption, and relying on the sasl security layers in slapd access controls, it is possible to obtain access that would otherwise be denied via a simple bind for any identity covered in those acls.
After the first sasl bind is completed, the sasl_ssf value is retained for all new non-sasl connections.
Depending on the acl configuration, this can affect different types of operations (searches, modifications, etc.).
In other words, a successful authorization step completed by one user affects the authorization requirement for a different user. (
( CVE-2019-13565) an integer underflow was discovered in openldap before 2.4.57 leading to slapd crashes in the certificate exact assertion processing, resulting in denial of service (schema_init.c serialnumberandissuercheck). (
( CVE-2020-36221) a flaw was discovered in openldap before 2.4.57 leading to an assertion failure in slapd in the saslauthzto validation, resulting in denial of service. (
( CVE-2020-36222) a flaw was discovered in openldap before 2.4.57 leading to a slapd crash in the values return filter control handling, resulting in denial of service (double free and out-of-bounds read). (
( CVE-2020-36223) a flaw was discovered in openldap before 2.4.57 leading to an invalid pointer free and slapd crash in the saslauthzto processing, resulting in denial of service. (
( CVE-2020-36224) a flaw was discovered in openldap before 2.4.57 leading to a memch->bv_len miscalculation and slapd crash in the saslauthzto processing, resulting in denial of service. (

Note: The preceding description block is extracted directly from the security advisory. Using automation, we have attempted to clean and format it as much as possible without introducing additional issues.

Successful exploitation of this vulnerability could lead to a securitybreach or could affect integrity, availability, and confidentiality.