Bug 1693612 (CVE-2019-3883) - CVE-2019-3883 389-ds-base: DoS via hanging secured connections
Summary: CVE-2019-3883 389-ds-base: DoS via hanging secured connections
Alias: CVE-2019-3883
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1668457 1699043 1719720
Blocks: 1690835
TreeView+ depends on / blocked
Reported: 2019-03-28 10:06 UTC by Cedric Buissart
Modified: 2020-12-07 20:32 UTC (History)
13 users (show)

Fixed In Version: 389-ds-base, 389-ds-base
Doc Type: If docs needed, set a value
Doc Text:
It was found that encrypted connections did not honor the 'ioblocktimeout' parameter to end blocking requests. As a result, an unauthenticated attacker could repeatedly start a sufficient number of encrypted connections to block all workers, resulting in a denial of service.
Clone Of:
Last Closed: 2019-07-29 19:18:33 UTC

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:1896 0 None None None 2019-07-29 15:15:51 UTC
Red Hat Product Errata RHSA-2019:3401 0 None None None 2019-11-05 20:46:02 UTC

Description Cedric Buissart 2019-03-28 10:06:27 UTC
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.

Comment 5 Salvatore Bonaccorso 2019-04-13 07:43:33 UTC

Is there any further references for this issue? Upstream issue or fixing commits? Thanks already for any hints!


Comment 6 William Brown 2019-04-15 00:49:44 UTC
Upstream does not appear to have been contacted about this issue. Perhaps the developers of 389 at redhat have? We have had some issues in the past with communication of security issues though.


I will be investigating this soon.

Comment 7 thierry bordaz 2019-04-15 08:16:03 UTC
Created attachment 1555159 [details]
Make sure secure connection enforce the ioblocktimeout

Comment 8 Cedric Buissart 2019-04-16 08:21:34 UTC

There is a proposed patch uploaded via comment 7.

Comment 10 errata-xmlrpc 2019-07-29 15:15:49 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7

Via RHSA-2019:1896 https://access.redhat.com/errata/RHSA-2019:1896

Comment 11 Product Security DevOps Team 2019-07-29 19:18:33 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):


Comment 12 errata-xmlrpc 2019-11-05 20:46:01 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2019:3401 https://access.redhat.com/errata/RHSA-2019:3401

Note You need to log in before you can comment on or make changes to this bug.