CVE details
CVE-2019-13565
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.
Affected ports (1)
| Port | Package | Version | Status | Maintainer |
|---|---|---|---|---|
| net/linux-c7-openldap | linux-c7-openldap | 2.4.44_3 | unaddressed | emulation@FreeBSD.org |
Template for a VuXML entry
Range taken from the CVE record, check it before committing. make newentry in security/vuxml creates the vid.
<vuln vid="FIXME (make newentry)">
<topic>FIXME -- FIXME</topic>
<affects>
<package>
<name>linux-c7-openldap</name>
<range><lt>FIXME</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>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.</p>
</body>
</description>
<references>
<cvename>CVE-2019-13565</cvename>
<url>https://nvd.nist.gov/vuln/detail/CVE-2019-13565</url>
</references>
<dates>
<discovery>2019-07-26</discovery>
<entry>2026-10-25</entry>
</dates>
</vuln>