# CVE-2024-3657: 389-ds-base: potential denial of service via specially crafted kerberos as-req request

> A specially crafted Kerberos AS-REQ request can cause the 389 Directory Server to fail, resulting in 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:** 28 May 2024
- **Updated:** 25 Feb 2026
- **Also known as:** CLSA-2025-1762867058, DEBIAN-CVE-2024-3657, UBUNTU-CVE-2024-3657

## What is CVE-2024-3657?

CVE-2024-3657 is a high-severity denial of service vulnerability in Red Hat Directory Server 11.5 E4S for RHEL 8, published on 28 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was found in 389-ds-base. A specially-crafted LDAP query can potentially cause a failure on the directory server, leading to a denial of service

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2024-3657?


## How do I fix CVE-2024-3657?

Apply the vendor's patch.

## Is CVE-2024-3657 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-3657 and fix it if it is affected.

What it is: CVE-2024-3657 is a high-severity denial of service vulnerability in Red Hat Directory Server 11.5 E4S for RHEL 8, published on 28 May 2024. 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-2024-3657 in the wild and no public exploit code.

Affected product: Red Hat Directory Server 11.5 E4S for RHEL 8. 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-2024-3657/ (Markdown: https://insights.sbomify.com/CVE-2024-3657/index.md)
```

## Sources

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

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