CVE-2019-3883: High severity red hat 389 directory server vulnerability
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.
Other sources
In 389-ds-base, 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.
— Red Hat
Affected Software
Event History
Frequently Asked Questions
What is CVE-2019-3883?
CVE-2019-3883 is a vulnerability in 389-ds-base up to version 1.4.1.2 that allows un-encrypted requests to bypass the timeout for worker threads.
What is the severity of CVE-2019-3883?
CVE-2019-3883 has a severity of 7.5 (high).
How does CVE-2019-3883 affect 389-ds-base?
CVE-2019-3883 affects 389-ds-base up to version 1.4.1.2.
Are encrypted requests affected by CVE-2019-3883?
No, encrypted requests using SSL/TLS are not affected by CVE-2019-3883.
How can I fix CVE-2019-3883?
To fix CVE-2019-3883, upgrade 389-ds-base to version 1.4.1.4 (or at least version 1.4.0.24 for older systems).