REDHAT-BUG-2513036: Medium severity 389 Directory Server vulnerability
A flaw was found in 389 Directory Server. The LDAP extended-operation handlers that start (multisupplierextopcleanruv) and abort (multisupplierextopabortcleanruv) the CleanAllRUV replication-maintenance task in ldap/servers/plugins/replication/replextop.c perform no check on the connection's bind DN or authentication state, unlike the analogous multisupplierextopStartNSDS50ReplicationRequest handler in the same file, which explicitly verifies the connection is an authorized replication updatedn via replicaisupdatedn(). Under the default nsslapd-allow-anonymous-access configuration, a fully anonymous network client that can reach a supplier's LDAP listener and knows the target suffix and replica ID can start or abort CleanAllRUV; if anonymous access has been restricted, any client that has completed a successful bind (regardless of privilege level) can do the same, since the handlers themselves perform no further authorization check. This lets the client cause unauthorized removal of a replica ID from replication metadata, purge related changelog records, and interrupt administrator-initiated cleanup operations, potentially leaving replication inconsistent or unavailable. Reported by Andrew Rukin (Arenadata), who verified the issue against 389-ds-base-3.3.0-5.fc45.x8664 with both a single supplier and two replicating suppliers, and confirmed the abort handler likewise lacks the check by source review. Independently reproduced live in an isolated sandbox against the same NVR: the anonymous start request was accepted and genuinely executed (RUV entry removed, changelog purged), a well-formed request to the sibling, protected StartNSDS50ReplicationRequest handler was correctly rejected under the same unauthenticated precondition, and cross-supplier propagation was confirmed (a second supplier independently completed the identical cleanup via its replication agreement with the targeted supplier, without ever receiving a direct request from the client).
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Compensating control
Restrict nsslapd-allow-anonymous-access (disable anonymous access) so that anonymous clients cannot reach the supplier’s LDAP listener to start or abort CleanAllRUV.
- Compensating control
If restricting anonymous access, note that any client with a successful bind (regardless of privilege) can start/abort CleanAllRUV per the extop handler behavior described; therefore also limit LDAP listener access (e.g., via network ACL/firewall) to trusted replication administrators/agents.
Event History
Frequently Asked Questions
What is the severity of REDHAT-BUG-2513036?
The severity of REDHAT-BUG-2513036 is medium, rated at 4.
How do I fix REDHAT-BUG-2513036?
To fix REDHAT-BUG-2513036, apply the latest patches or updates provided by Red Hat for 389 Directory Server.
What vulnerability does REDHAT-BUG-2513036 address?
REDHAT-BUG-2513036 addresses a flaw in the LDAP extended-operation handlers that lack checks on connection privileges.
When was REDHAT-BUG-2513036 published?
REDHAT-BUG-2513036 was published on August 10, 2026.
Which software is affected by REDHAT-BUG-2513036?
REDHAT-BUG-2513036 affects the 389 Directory Server software.