CVE-2019-13565
An issue was discovered in OpenLDAP 2.x before 2.4.48.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
No affected packages have been listed by the sources.
References 16
lists.debian.org
lists.opensuse.org
seclists.org
lists.apache.org
- thread.html/r1b103833cb5bc8466e24ff0ecc5e75b45a705334ab6a444e64e840a0@<issues.bookkeeper.apache.org>
- thread.html/rf4c02775860db415b4955778a131c2795223f61cb8c6a450893651e4@<issues.bookkeeper.apache.org>
- thread.html/r58af02e294bd07f487e2c64ffc0a29b837db5600e33b6e698b9d696b@<issues.bookkeeper.apache.org>