First published: Mon Aug 20 2018(Updated: )
A vulnerability was discovered in 389-ds-base through versions 1.3.7.10, 1.3.8.8 and 1.4.0.16. The lock controlling the error log was not correctly used when re-opening the log file in log__error_emergency(). An attacker could send a flood of modifications to a very large DN, which would cause slapd to crash.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Red Hat 389 Directory Server | <=1.3.7.10 | |
Red Hat 389 Directory Server | >=1.3.8.0<=1.3.8.8 | |
Red Hat 389 Directory Server | >=1.4.0.0<=1.4.0.16 | |
Red Hat Enterprise Linux Desktop | =7.0 | |
Red Hat Enterprise Linux Server | =7.0 | |
Red Hat Enterprise Linux Server | =7.6 | |
Red Hat Enterprise Linux Server | =7.5 | |
Red Hat Enterprise Linux Server | =7.6 | |
Red Hat Enterprise Linux Server | =7.6 | |
Red Hat Enterprise Linux Workstation | =7.0 | |
Debian | =8.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2018-14624 has a medium severity rating due to the potential for denial of service attacks.
To fix CVE-2018-14624, upgrade to 389-ds-base versions 1.3.7.11, 1.3.8.9, or 1.4.0.17 and apply all necessary patches.
CVE-2018-14624 allows an attacker to flood error logs under specific conditions, possibly leading to service disruption.
Yes, CVE-2018-14624 can affect various Linux distributions that utilize vulnerable versions of the 389 Directory Server.
There are no recommended workarounds for CVE-2018-14624; patching to the secure version is the best approach.