dbcve.org
Enterprise Linux Server EusOperating system · Redhat

CVE-2019-10171

HIGH · 7.5 CVSS v3.1 Published 2019-08-02
Fix available
A fix is available. Upgrade to 1.4.0.17 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In 389-ds-base versions 1.4.0.x before 1.4.0.17, the fix for CVE-2018-14648 (CPU exhaustion leading to DoS) was incorrectly applied in RHEL 7.5, allowing attackers to still trigger excessive CPU consumption via malformed requests to the directory server.

MitigationUpdate 389-ds-base to version 1.4.0.17 or later, or apply vendor-supplied patches for RHEL 7.5 to remediate the incorrectly applied fix.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Enterprise Linux Server EusOperating system
Affected:= 7.5
389 Directory ServerApplication
Affected:>= 1.4.0.0, < 1.4.0.17

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify 389-ds-base version
    Run 'rpm -q 389-ds-base' to check if the package is installed, then run 'rpm -q --qf "%{VERSION}.%{RELEASE}" 389-ds-base' to get the exact version number
    Affected if Version is 1.4.0.0 through 1.4.0.16 (any version before 1.4.0.17)
  2. Confirm operating system version
    Run 'cat /etc/redhat-release' or 'cat /etc/os-release' to identify if the system is Red Hat Enterprise Linux 7.5
    Affected if System is RHEL 7.5 specifically (the version where the CVE-2018-14648 fix was incorrectly applied)
  3. Verify directory server is running
    Run 'systemctl status dirsrv@*' or check if the DS (directory server) process is active using 'ps aux | grep dirsrv'
    Affected if The 389 Directory Server instance is running and accepting network connections, as the attack requires sending malformed requests to the server

A system is affected if it runs 389-ds-base version 1.4.0.0-1.4.0.16, or is RHEL 7.5 with any 389-ds-base version in the 1.4.0.x range, and the directory server is accessible on the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 1.4.0.17 or later
Fixed in 1.4.0.17
Interim mitigation

Update 389-ds-base to version 1.4.0.17 or later, or apply vendor-supplied patches for RHEL 7.5 to remediate the incorrectly applied fix.

Fix this in Enterprise Linux Server Eus Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-10171 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-10171 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data