In 389-ds-base up to version 1.4.1.2, requests are handled by workers threads. Each sockets will be waited by the worker for at most 'ioblocktimeout' seconds. However this timeout applies only for un-encrypted requests. Connections using SSL/TLS are not taking this timeout into account during reads, and may hang longer.An unauthenticated attacker could repeatedly create hanging LDAP requests to hang all the workers, resulting in a Denial of Service.
The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed.
| Link | Tags |
|---|---|
| https://lists.debian.org/debian-lts-announce/2019/05/msg00008.html | third party advisory mailing list |
| https://access.redhat.com/errata/RHSA-2019:1896 | third party advisory vendor advisory |
| https://access.redhat.com/errata/RHSA-2019:3401 | third party advisory vendor advisory |
| https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-3883 | third party advisory issue tracking |
| https://pagure.io/389-ds-base/issue/50329 | third party advisory issue tracking |
| https://pagure.io/389-ds-base/pull-request/50331 | third party advisory |
| https://lists.debian.org/debian-lts-announce/2023/04/msg00026.html | mailing list |