First published: Thu Mar 28 2019(Updated: )
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.
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Fedoraproject 389 Directory Server | <=1.4.1.2 | |
Debian Debian Linux | =8.0 | |
Redhat Enterprise Linux | =6.0 | |
redhat/389-ds-base | <1.4.0.24 | 1.4.0.24 |
redhat/389-ds-base | <1.4.1.4 | 1.4.1.4 |
<=1.4.1.2 | ||
=8.0 | ||
=6.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
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.
CVE-2019-3883 has a severity of 7.5 (high).
CVE-2019-3883 affects 389-ds-base up to version 1.4.1.2.
No, encrypted requests using SSL/TLS are not affected by 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).