CVE-2024-8445VulnerabilityPublished 5 Sep 2024Updated 6 Nov 2025

CVE-2024-8445: 389-ds-base · Improper Input Validation

Affects 389-ds-baseSource CVE Database V5

Mentioned vulnerabilities

CVE-2024-2199

Not known to be exploited · CVSS 5.7 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.7Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Sep 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Red Hatredhat/389-ds-base`pkg:rpm/redhat/389-ds-base`Other threats	Affected =3.1.1	Fixed in–

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

AI-suggested

To mitigate CVE-2024-8445, organizations should upgrade 389-ds-base to a version where this vulnerability is fully patched once available. Until a patch is released, administrators should restrict access to the LDAP server to trusted users only and monitor for unusual modification attempts on the userPassword attribute. Implement strict access controls and audit logging to detect and respond to suspicious activities promptly. Network segmentation can limit exposure by isolating the LDAP server from untrusted networks. Additionally, consider deploying application-layer protections such as input validation proxies or Web Application Firewalls (WAFs) that can detect and block malformed LDAP modification requests. Regularly review and update authentication policies to minimize the number of users with modification privileges. Finally, maintain robust incident response plans to quickly recover from potential denial-of-service events.

Description

The 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.

Impact

The primary impact of CVE-2024-8445 is denial of service, which can disrupt directory services that are foundational for identity management, authentication, and authorization in many organizations. A successful exploit could cause the 389-ds-base server to crash, leading to downtime and potential cascading failures in dependent systems. This can affect user access to applications and services, delay business operations, and increase operational costs due to incident response and recovery efforts. Although confidentiality and integrity are not directly impacted, the availability loss can indirectly affect security posture by forcing fallback to less secure or manual processes. Organizations relying heavily on 389-ds-base for critical infrastructure, especially those with large user bases or complex access controls, may experience significant operational disruption. The requirement for authentication limits the risk to insiders or compromised accounts, but the ease of exploitation and low privileges needed raise concerns about insider threats or lateral movement scenarios.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Feb 2026, 04:04 UTC

Technical details

References

Community reviews

Related threats