dbcve.org
389 Directory ServerOperating system · Redhat

CVE-2024-1062

MEDIUM · 5.5 CVSS v3.1 Published 2024-02-12
Fix available
A fix is available. Upgrade to 2.2.0 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
A heap overflow flaw was found in 389-ds-base. This issue leads to a denial of service when writing a value larger than 256 chars in log_entry_attr.

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 confidence

A heap overflow vulnerability exists in 389-ds-base (389 Directory Server) where writing a value larger than 256 characters to the log_entry_attr configuration parameter causes a heap buffer overflow. This can be triggered by an authenticated user with privileges to modify the logging configuration, leading to denial of service.

MitigationUpgrade to a patched version of 389-ds-base that addresses this vulnerability. Additionally, implement input validation to enforce the 256-character limit on log_entry_attr values until the patch is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
389 Directory ServerOperating system
Affected:< 2.2.0
Directory ServerApplication
Affected:all versions= 11.7= 11.8= 12.0
FedoraOperating system
Affected:= 39= 40= 41
Enterprise LinuxOperating system
Affected:= 8.0
Enterprise Linux EusOperating system
Affected:= 8.6= 8.8= 9.2
Enterprise Linux For Arm 64 EusOperating system
Affected:= 8.6= 8.8= 9.2
Enterprise Linux For Ibm Z SystemsOperating system
Affected:= 9.2
Enterprise Linux For Ibm Z Systems EusOperating system
Affected:= 8.8

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed 389-ds-base version
    Run 'rpm -q 389-ds-base' on RHEL/Fedora systems, or check the package version using your system's package manager. On the server, you can also query the cn=DirectoryServer,cn=ServerGroup,cn=configuration object via ldapsearch.
    Affected if The installed version is lower than 2.2.0, or matches one of the affected Red Hat or Fedora versions listed in the CVE (8.0, 8.6, 8.8, 9.2, 11.7, 11.8, 12.0 for RHEL; 39, 40, 41 for Fedora).
  2. Locate the log_entry_attr configuration
    Search the LDAP configuration for the log_entry_attr attribute. Run an ldapsearch query on cn=log,cn=config (or cn=accesslog,cn=config for access logging) or examine the dse.ldif configuration file in the instance directory (typically /etc/dirsrv/slapd-INSTANCENAME/dse.ldif).
    Affected if The log_entry_attr attribute is present in your configuration.
  3. Measure the log_entry_attr value length
    If log_entry_attr is found, retrieve its value and count the characters. In LDAP, run: ldapsearch -LLL -D 'cn=directory manager' -W -b 'cn=log,cn=config' logEntryAttr. In dse.ldif, locate the 'logEntryAttr' or 'log_entry_attr' line and count characters after the colon.
    Affected if The value assigned to log_entry_attr exceeds 256 characters in length.
  4. Verify write access to logging configuration
    Check which users or groups have write access to the cn=log subtree. Review LDAP ACIs (Access Control Instructions) on cn=log,cn=config or check the dse.ldif for 'modifiersName' entries to identify who can modify logging settings.
    Affected if Authenticated users other than directory administrators have write access to logging configuration.

You are affected if you run a vulnerable 389-ds-base version below 2.2.0 AND have a log_entry_attr configuration value that exceeds 256 characters AND that configuration is modifiable by non-admin users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 2.2.0 or later
Fixed in 2.2.0
Interim mitigation

Upgrade to a patched version of 389-ds-base that addresses this vulnerability. Additionally, implement input validation to enforce the 256-character limit on log_entry_attr values until the patch is applied.

Recommended fix Moderate confidence

389 Directory Server version 2.2.0 or later; or apply the latest Red Hat Security Advisory (RHSA) for this CVE

  1. Identify the current version of 389-ds-base installed using: rpm -q 389-ds-base or dnf list installed 389-ds-base
  2. For 389 Directory Server: Upgrade to version 2.2.0 or later. On RHEL/RHEL-derived systems, run: dnf update 389-ds-base
  3. For Fedora systems: Run: dnf update 389-ds-base to get the patched version available for your Fedora release
  4. Verify the upgrade was successful by checking the new version: rpm -q 389-ds-base
  5. Restart the directory server service after upgrade: systemctl restart dirsrv@* or according to your deployment configuration
  6. Test that the directory server functions normally and the vulnerability is resolved by attempting to write a value larger than 256 chars to log_entry_attr
Caveat Standard 389-ds-base upgrade - review release notes for any configuration changes between your current version and 2.2.0

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in 389 Directory Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1062 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-1062 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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