Summary
It was discovered that 389 Directory Server presented to users, during
authentication, an error message which could be used to discover if a
certain LDAP DN existed or not. A remote unauthenticated attacker could
possibly use this to check the existence of an entry in a LDAP database
and expose sensitive information. This issue affected only Ubuntu 20.04
ESM. (CVE-2020-35518)
It was discovered that 389 Directory Server was incorrectly validating
data used to access memory addresses. An authenticated attacker using a
Syncrepl client could use this issue with a specially crafted query to
cause 389 Directory Server to crash, resulting in a denial of service.
(CVE-2021-3514)
Fixed packages 3
| Release | Package | Fixed in |
|---|---|---|
| Ubuntu · Pro 16.04 LTS Pro:16.04:LTS | 389-ds-base | 1.3.4.9-1ubuntu0.1~esm1 |
| Ubuntu · Pro 18.04 LTS Pro:18.04:LTS | 389-ds-base | 1.3.7.10-1ubuntu1+esm1 |
| Ubuntu · Pro 20.04 LTS Pro:20.04:LTS | 389-ds-base | 1.4.3.6-2ubuntu0.1~esm1 |
Vulnerabilities 2
-
Unscored —
When binding against a DN during authentication, the reply from 389-ds-base will be different whether the DN exists or …
-
Unscored —
When using a sync_repl client in 389-ds-base, an authenticated attacker can cause a NULL pointer dereference using a sp…