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.
References
Configurations
History
21 Nov 2024, 04:42
Type | Values Removed | Values Added |
---|---|---|
References | () https://access.redhat.com/errata/RHSA-2019:1896 - Third Party Advisory | |
References | () https://access.redhat.com/errata/RHSA-2019:3401 - Third Party Advisory | |
References | () https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-3883 - Issue Tracking, Third Party Advisory | |
References | () https://lists.debian.org/debian-lts-announce/2019/05/msg00008.html - Mailing List, Third Party Advisory | |
References | () https://lists.debian.org/debian-lts-announce/2023/04/msg00026.html - | |
References | () https://pagure.io/389-ds-base/issue/50329 - Issue Tracking, Third Party Advisory | |
References | () https://pagure.io/389-ds-base/pull-request/50331 - Third Party Advisory |
Information
Published : 2019-04-17 14:29
Updated : 2024-11-21 04:42
NVD link : CVE-2019-3883
Mitre link : CVE-2019-3883
CVE.ORG link : CVE-2019-3883
JSON object : View
Products Affected
debian
- debian_linux
fedoraproject
- 389_directory_server
redhat
- enterprise_linux
CWE
CWE-772
Missing Release of Resource after Effective Lifetime