CVE-2024-8445
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 · uneditedThe fix for CVE-2024-2199 in 389-ds-base was insufficient to cover all scenarios. In certain product versions, an authenticated user may cause a server crash while modifying `userPassword` using malformed input.
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 · moderate confidenceCVE-2024-8445 is a follow-up vulnerability to CVE-2024-2199 in 389-ds-base (389 Directory Server). The original fix for input validation during userPassword modification was incomplete, allowing an authenticated user to crash the server by providing malformed input when modifying their password. This is a denial-of-service vulnerability requiring authentication but no elevated privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm 389 Directory Server is installedRun 'rpm -qa | grep -E "389-ds-base|ds389"' or check for directory server processes via 'ps aux | grep ns-slapd'Affected if The package or process is found, indicating 389-ds-base is present
-
Determine installed version of 389-ds-baseRun 'rpm -q 389-ds-base' or 'dsctl --version' if available, then compare the version number to the fixed release that addresses CVE-2024-8445Affected if The installed version is older than the patched version for CVE-2024-8445 (contact vendor for specific version numbers)
-
Verify the server is running and accepting authenticated connectionsRun 'ldapsearch -x -D "cn=Directory Manager" -W -b "cn=config" olnVersion' using appropriate admin credentialsAffected if The server responds to authenticated queries, meaning password modification operations can be attempted
-
Confirm userPassword modification is enabled for standard usersCheck the access control configuration via 'ldapsearch -x -D "cn=Directory Manager" -W -b "cn=default naming context,cn=ldbm database,cn=plugins,cn=config" aci' or review ACL settings in dse.ldifAffected if Authenticated users have write access to their own userPassword attribute (no restricted by ACI)
-
Check for recent server crashes related to password operationsReview server error logs in /var/log/dirsrv/slapd-*/* or run 'journalctl -u dirsrv@* -g "password" --since "recent"'Affected if Crashes or assertion failures appear in logs following password modification attempts
A user is affected if they run an unpatched version of 389-ds-base where authenticated users can modify their own passwords and the server may crash from malformed input.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor-supplied patches for CVE-2024-8445 when available. Until then, restrict access to password modification operations to only trusted authenticated users and monitor for server crashes related to password changes.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-8445 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-8445 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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