An issue exists in OpenLDAP 2.x prior to 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.
Vulnerable Product | Search on Vulmon | Subscribe to Product |
---|---|---|
openldap openldap |
||
canonical ubuntu linux 16.04 |
||
canonical ubuntu linux 12.04 |
||
canonical ubuntu linux 18.04 |
||
canonical ubuntu linux 19.04 |
||
canonical ubuntu linux 14.04 |
||
debian debian linux 8.0 |
||
opensuse leap 15.0 |
||
opensuse leap 15.1 |
||
f5 traffix signaling delivery controller 5.1.0 |
||
f5 traffix signaling delivery controller 5.0.0 |
||
apple mac os x 10.13.6 |
||
apple mac os x |
||
apple mac os x 10.14.6 |
||
oracle solaris 11 |
||
oracle zfs storage appliance kit 8.8 |
||
oracle blockchain platform |