Skip to main content
CVE-2024-1062VulnerabilityPublished Updated

CVE-2024-1062: 389-ds-base · Heap-based Buffer Overflow

Affects 389-ds-baseSource CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Feb 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Red Hatredhat/389-ds-basepkg:rpm/redhat/389-ds-baseOther threatsAffected
  • =1.4.3.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately verify if they are running 389-ds-base version 1.4.3.0 and plan to upgrade to a patched version once available. In the interim, restrict local access to trusted users only and monitor for unusual application crashes or service disruptions related to 389-ds-base. Implement strict access controls and auditing on systems running this software to detect potential exploitation attempts. Consider deploying application-level protections such as memory safety tools (e.g., AddressSanitizer) in test environments to identify overflow attempts. Additionally, review logging configurations to limit the size of log_entry_attr inputs or sanitize inputs to prevent oversized values. Regularly update and patch systems, and maintain an incident response plan to quickly address any service outages. Engage with vendor advisories for official patches and guidance.

Description

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.

References

Community reviews

Loading reviews…