Openldap Openldap Openldap can notify you when security vulnerabilities are reported in Openldap Openldap. You can add multiple products that you use with Openldap to create your own personal software stack watcher.

By the Year

In 2020 there have been 1 vulnerability in Openldap Openldap with an average score of 7.5 out of ten. Last year Openldap had 2 security vulnerabilities published. Right now, Openldap is on track to have less security vulerabilities in 2020 than it did last year. However, the average CVE base score of the vulnerabilities in 2020 is greater by 1.30.

Year Vulnerabilities Average Score
2020 1 7.50
2019 2 6.20
2018 0 0.00

It may take a day or so for new Openldap vulnerabilities to show up. Additionally vulnerabilities may be tagged under a different product or component name.

Latest Openldap Openldap Security Vulnerabilities

In filter.c in slapd in OpenLDAP before 2.4.50

CVE-2020-12243 7.5 - High - April 28, 2020

In filter.c in slapd in OpenLDAP before 2.4.50, LDAP search filters with nested boolean expressions can result in denial of service (daemon crash).

Uncontrolled Resource Consumption ('Resource Exhaustion')

An issue was discovered in the server in OpenLDAP before 2.4.48

CVE-2019-13057 4.9 - Medium - July 26, 2019

An issue was discovered in the server in OpenLDAP before 2.4.48. When the server administrator delegates rootDN (database admin) privileges for certain databases but wants to maintain isolation (e.g., for multi-tenant deployments), slapd does not properly stop a rootDN from requesting authorization as an identity from another database during a SASL bind or with a proxyAuthz (RFC 4370) control. (It is not a common configuration to deploy a system where the server administrator and a DB administrator enjoy different levels of trust.)


An issue was discovered in OpenLDAP 2.x before 2.4.48

CVE-2019-13565 7.5 - High - July 26, 2019

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.