# CVE-2022-0918: Denial of service in 389-ds-base

> An unauthenticated attacker can crash the 389 Directory Server by sending a single malicious message, causing a denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/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:** 16 Mar 2022
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2022-0918, GHSA-2h5q-vphx-mcwx, RHSA-2022:2210, UBUNTU-CVE-2022-0918, openSUSE-SU-2024:11963-1

## What is CVE-2022-0918?

CVE-2022-0918 is a high-severity denial of service vulnerability in Redhat Enterprise Linux, published on 16 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was discovered in the 389 Directory Server that allows an unauthenticated attacker with network access to the LDAP port to cause a denial of service. The denial of service is triggered by a single message sent over a TCP connection, no bind or other authentication is required. The message triggers a segmentation fault that results in slapd crashing.

## Which versions are affected by CVE-2022-0918?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `389-ds-base` | Red Hat:directory_server:11.5::el8 | All versions | 0:1.4.3.29-3.module+el8dsrv+14615+a86efbbf |
| `389-ds-base-debuginfo` | Red Hat:directory_server:11.5::el8 | All versions | 0:1.4.3.29-3.module+el8dsrv+14615+a86efbbf |
| `389-ds-base-debugsource` | Red Hat:directory_server:11.5::el8 | All versions | 0:1.4.3.29-3.module+el8dsrv+14615+a86efbbf |
| `389-ds-base-devel` | Red Hat:directory_server:11.5::el8 | All versions | 0:1.4.3.29-3.module+el8dsrv+14615+a86efbbf |
| `389-ds-base-legacy-tools` | Red Hat:directory_server:11.5::el8 | All versions | 0:1.4.3.29-3.module+el8dsrv+14615+a86efbbf |
| `389-ds-base-legacy-tools-debuginfo` | Red Hat:directory_server:11.5::el8 | All versions | 0:1.4.3.29-3.module+el8dsrv+14615+a86efbbf |
| `389-ds-base-libs` | Red Hat:directory_server:11.5::el8 | All versions | 0:1.4.3.29-3.module+el8dsrv+14615+a86efbbf |
| `389-ds-base-libs-debuginfo` | Red Hat:directory_server:11.5::el8 | All versions | 0:1.4.3.29-3.module+el8dsrv+14615+a86efbbf |
| `389-ds-base-snmp` | Red Hat:directory_server:11.5::el8 | All versions | 0:1.4.3.29-3.module+el8dsrv+14615+a86efbbf |
| `389-ds-base-snmp-debuginfo` | Red Hat:directory_server:11.5::el8 | All versions | 0:1.4.3.29-3.module+el8dsrv+14615+a86efbbf |
| `cockpit-389-ds` | Red Hat:directory_server:11.5::el8 | All versions | 0:1.4.3.29-3.module+el8dsrv+14615+a86efbbf |
| `python3-lib389` | Red Hat:directory_server:11.5::el8 | All versions | 0:1.4.3.29-3.module+el8dsrv+14615+a86efbbf |
| `389-ds` | openSUSE:Tumbleweed | All versions | 2.1.1~git4.b7f891097-1.1 |

Products: Port389 389-Ds-Base, Redhat Enterprise Linux.

## How do I fix CVE-2022-0918?

Apply the vendor's patch.

## Is CVE-2022-0918 being exploited?

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

Public exploit code:

- CVE-2022-0918 (github_poc): https://github.com/NathanMulbrook/CVE-2022-0918

## Other vulnerabilities in Redhat Enterprise Linux

- [CVE-2021-4091](https://insights.sbomify.com/CVE-2021-4091/): Use after free in 389-ds-base (high 7.5)
- [CVE-2021-3652](https://insights.sbomify.com/CVE-2021-3652/): Auth bypass in 389-ds-base (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-0918 and fix it if it is affected.

What it is: CVE-2022-0918 is a high-severity denial of service vulnerability in Redhat Enterprise Linux, published on 16 Mar 2022. 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-2022-0918 in the wild and no public exploit code.

Affected product: Redhat Enterprise Linux. 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-2022-0918/ (Markdown: https://insights.sbomify.com/CVE-2022-0918/index.md)
```

## Sources

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

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