CVE-2019-10171
First published: Fri Aug 02 2019(Updated: )
It was found that the fix for CVE-2018-14648 in 389-ds-base, versions 1.4.0.x before 1.4.0.17, was incorrectly applied in RHEL 7.5. An attacker would still be able to provoke excessive CPU consumption leading to a denial of service.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Red Hat 389 Directory Server | >=1.4.0.0<1.4.0.17 | |
| Red Hat Enterprise Linux Server | =7.5 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2019-10171?
CVE-2019-10171 has a medium severity level due to its potential to cause denial of service through excessive CPU consumption.
How do I fix CVE-2019-10171?
To fix CVE-2019-10171, upgrade 389-ds-base to version 1.4.0.17 or later on affected systems.
What systems are affected by CVE-2019-10171?
CVE-2019-10171 affects Red Hat Enterprise Linux Server EUS version 7.5 and 389 Directory Server versions before 1.4.0.17.
Can CVE-2019-10171 result in a denial of service?
Yes, an attacker can exploit CVE-2019-10171 to cause excessive CPU consumption leading to a denial of service condition.
Was CVE-2019-10171 a result of a previous vulnerability?
Yes, CVE-2019-10171 stems from a fix for CVE-2018-14648 that was incorrectly applied in certain versions.
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/references
- agent/author
- agent/severity
- agent/weakness
- agent/description
- agent/event
- agent/first-publish-date
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/fedoraproject
- canonical/red hat 389 directory server
- version/red hat 389 directory server/1.4.0.0
- vendor/redhat
- canonical/red hat enterprise linux server
- version/red hat enterprise linux server/7.5