# CVE-2019-10171: Denial of service in 389-ds-base

> An attacker can cause excessive CPU consumption leading to denial of service in the 389-ds-base LDAP server due to an incomplete security fix.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Aug 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9cc6-43cm-mf7x, RHSA-2019:1789

## What is CVE-2019-10171?

CVE-2019-10171 is a high-severity denial of service vulnerability in Redhat Enterprise Linux Server Eus, published on 2 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2019-10171?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `389-ds-base` | Red Hat:rhel_eus:7.5::computenode | All versions | 0:1.3.7.5-30.el7_5 |
| `389-ds-base-debuginfo` | Red Hat:rhel_eus:7.5::computenode | All versions | 0:1.3.7.5-30.el7_5 |
| `389-ds-base-devel` | Red Hat:rhel_eus:7.5::computenode | All versions | 0:1.3.7.5-30.el7_5 |
| `389-ds-base-libs` | Red Hat:rhel_eus:7.5::computenode | All versions | 0:1.3.7.5-30.el7_5 |
| `389-ds-base-snmp` | Red Hat:rhel_eus:7.5::computenode | All versions | 0:1.3.7.5-30.el7_5 |
| `389-ds-base` | Red Hat:rhel_eus:7.5::server | All versions | 0:1.3.7.5-30.el7_5 |
| `389-ds-base-debuginfo` | Red Hat:rhel_eus:7.5::server | All versions | 0:1.3.7.5-30.el7_5 |
| `389-ds-base-devel` | Red Hat:rhel_eus:7.5::server | All versions | 0:1.3.7.5-30.el7_5 |
| `389-ds-base-libs` | Red Hat:rhel_eus:7.5::server | All versions | 0:1.3.7.5-30.el7_5 |
| `389-ds-base-snmp` | Red Hat:rhel_eus:7.5::server | All versions | 0:1.3.7.5-30.el7_5 |

Products: Fedoraproject 389 Directory Server, Redhat Enterprise Linux Server Eus.

## How do I fix CVE-2019-10171?

Apply the vendor's patch.

## Is CVE-2019-10171 being exploited?

There is no known exploitation of CVE-2019-10171 in the wild and no public exploit code.

## Other vulnerabilities in Redhat Enterprise Linux Server Eus

- [CVE-2017-7551](https://insights.sbomify.com/CVE-2017-7551/): Information disclosure in 389-ds-base (critical 9.8)
- [CVE-2017-15135](https://insights.sbomify.com/CVE-2017-15135/): Auth bypass in 389-ds-base (high 8.1)
- [CVE-2018-14638](https://insights.sbomify.com/CVE-2018-14638/): Denial of service in 389-ds-base (high 7.5)
- [CVE-2018-1054](https://insights.sbomify.com/CVE-2018-1054/): Denial of service in 389-ds-base (high 7.5)
- [CVE-2017-15134](https://insights.sbomify.com/CVE-2017-15134/): Memory corruption in 389-ds-base (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10171 and fix it if it is affected.

What it is: CVE-2019-10171 is a high-severity denial of service vulnerability in Redhat Enterprise Linux Server Eus, published on 2 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-10171 in the wild and no public exploit code.

Affected product: Redhat Enterprise Linux Server Eus. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-10171/ (Markdown: https://insights.sbomify.com/CVE-2019-10171/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-10171
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-10171
- OSV: https://osv.dev/vulnerability/CVE-2019-10171

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-10171/
Summaries are generated and may contain mistakes; the official description above is the record.