CVE-2019-3883
moderate-risk
Published 2019-04-17
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.
Do I need to act?
-
0.80% chance of exploitation
EPSS score — low exploit probability
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
7
CVSS 7.5/10
High
NETWORK
/ LOW complexity
Affected Products (3)
Affected Vendors
References (14)
Third Party Advisory
https://access.redhat.com/errata/RHSA-2019:1896
Third Party Advisory
https://access.redhat.com/errata/RHSA-2019:3401
Issue Tracking
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-3883
Issue Tracking
https://pagure.io/389-ds-base/issue/50329
Third Party Advisory
https://pagure.io/389-ds-base/pull-request/50331
Third Party Advisory
https://access.redhat.com/errata/RHSA-2019:1896
Third Party Advisory
https://access.redhat.com/errata/RHSA-2019:3401
Issue Tracking
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-3883
Issue Tracking
https://pagure.io/389-ds-base/issue/50329
Third Party Advisory
https://pagure.io/389-ds-base/pull-request/50331
38
/ 100
moderate-risk
Severity
26/34 · High
Exploitability
3/34 · Minimal
Exposure
9/34 · Low