Red Hat Directory Server 12.4 E4S for RHEL 9 vulnerabilities
11 known vulnerabilities in Red Hat Directory Server 12.4 E4S for RHEL 9 from Red Hat. 11 are rated high or critical. Each entry lists the affected versions and the release that fixes it, where the vendor has published one.
Latest first
- 8.4 High severity
Red Hat Directory Server 11.5 E4S for RHEL 8: Improper Neutralization of Special Elements used in an OS Command
A flaw was found in 389-ds-base. The Cockpit 389 Console's LDAP editor constructs an ldapsearch command by embedding an LDAP entry's distinguished name (DN) into a shell command string without proper escaping. An LDAP user with delegated privileges to create o
- 9.8 Critical severity
Red Hat Directory Server 11.5 E4S for RHEL 8: Improper Authentication
A flaw was found in 389 Directory Server. During SASL PLAIN authentication, a stale identity carried in a Cyrus SASL auxiliary property from a prior failed bind attempt can be installed on a connection following a subsequent, unrelated successful bind, regardl
- 7.5 High severity
Red Hat Directory Server 11.5 E4S for RHEL 8: NULL Pointer Dereference
A flaw was found in 389 Directory Server. A missing NULL pointer check in the paged results handling of op_shared_search allows an unauthenticated remote attacker to crash the LDAP server by sending a crafted sequence of search requests using the USE_ONE_BACKE
- 7.5 High severity
Red Hat Directory Server 11.5 E4S for RHEL 8: Integer Underflow (Wrap or Wraparound)
A heap buffer overflow flaw was found in the SASL I/O layer of 389 Directory Server (389-ds-base). In sasl_io_start_packet(), the wrapped-record length read from the wire is validated only against an upper bound. A small wire length (0, 1, or 2) produces an en
- 7.5 High severity
Red Hat Directory Server 11.5 E4S for RHEL 8: Incorrect Authorization
A flaw was found in 389 Directory Server. The SELFDN ACI bind-rule evaluator incorrectly matches an anonymous LDAP client's empty bind DN against an empty stored attribute value, allowing an unauthenticated client to satisfy access control checks intended to r
- 7.5 High severity
Red Hat Directory Server 11.5 E4S for RHEL 8: Stack-based Buffer Overflow
A stack buffer overflow flaw was found in 389 Directory Server (389-ds-base). The get_ruvelement_from_berval() function in repl5_ruv.c copies digit characters from a network-supplied RUV berval into a fixed 16-byte stack buffer without bounds checking. A remot
- 7.5 High severity
Red Hat Directory Server 11.5 E4S for RHEL 8: Improper Neutralization of Special Elements used in an LDAP Query
A flaw was found in 389 Directory Server. An unauthenticated remote attacker can inject LDAP search filters into the CleanAllRUV replication status-check extended operation. Because the handler performs the search against cn=config with elevated replication pl
- 8.8 High severity
389-ds-base: Heap-based Buffer Overflow
A heap buffer overflow flaw was found in the SASL I/O layer of 389 Directory Server (389-ds-base). After a successful SASL bind with integrity protection (SSF > 0), an authenticated attacker can send a specially crafted oversized LDAP UNBIND packet that is cop
- 7.6 High severity
Red Hat Directory Server 11.5 E4S for RHEL 8: Integer Overflow or Wraparound
An integer overflow flaw was found in the SASL I/O layer of 389 Directory Server (389-ds-base). In sasl_io_start_packet(), adding sizeof(uint32_t) to a crafted SASL packet length prefix of 0xFFFFFFFC causes unsigned wraparound to zero, bypassing the nsslapd-ma
- 7.5 High severity
Red Hat Directory Server 11.5 E4S for RHEL 8: NULL Pointer Dereference
A flaw was found in 389 Directory Server. The dereference control plugin does not check for allocation failure before using a BER structure, allowing an unauthenticated remote attacker to crash the LDAP server when the system is under memory pressure.
- 7.5 High severity
Red Hat Directory Server 11.5 E4S for RHEL 8: Allocation of Resources Without Limits or Throttling
A flaw was found in 389-ds-base. The get_ldapmessage_controls_ext() function in the LDAP server does not enforce an upper bound on the number of controls per LDAP message. A remote, unauthenticated attacker can send a specially crafted LDAP request containing