A denial of service vulnerability was found in 389-ds-base ldap server. This issue may allow an authenticated user to…
Summary
Vulnerability reported (CVE-2024-2199). Risk of unauthorized operations or information disclosure. Exploitable via userPassword.
Original description
The description as published by the source.
A denial of service vulnerability was found in 389-ds-base ldap server. This issue may allow an authenticated user to cause a server crash while modifying userPassword using malformed input.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2024-2199 has been found.
Attackers can target a specific entry point like userPassword over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2024-2199" on the vendor's site.
CVE-2024-2199 — CWE-20 / CVSS v3 5.7
Attack vector: adjacent-network / no user interaction
Attack surface: userPassword
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) has been reported. Attackers reach the vulnerable code path via userPassword.
Check the vendor advisory for the affected versions. Attack surface: userPassword.
Severity: Medium (CVSS 5.7/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで影響コンポーネントを特定する。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2024-2199 389-ds-base Fixed in: 1.4.4.11-2+deb11u1
- Ubuntu UBUNTU-CVE-2024-2199 389-ds-base
References
- advisory access.redhat.com
- advisory access.redhat.com
- advisory access.redhat.com
- advisory access.redhat.com
- advisory access.redhat.com
- advisory access.redhat.com
- advisory access.redhat.com
- advisory access.redhat.com
- advisory access.redhat.com
- advisory access.redhat.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- report bugzilla.redhat.com
- web port389.org
- web lists.debian.org
- web access.redhat.com