CVE-2012-4450: 389 Directory Server 1.2.10 does not properly update the ACL when a DN entry is moved by a modrdn operation...

Security readout for executives and security teams

A flaw in 389 Directory Server 1.2.10 could let an authenticated user with specific permissions move a directory entry in a way that leaves access controls incorrectly applied. That may allow access to a DN entry that ACLs should have restricted. This is not an unauthenticated internet break-in, but it matters where directory permissions protect sensitive identities or data. Exposure is most likely in environments running 389 Directory Server 1.2.10 or downstream packages using the affected 389-ds-base code. Risk depends on whether authenticated users can perform modrdn or move operations on entries protected by ACL boundaries. Prioritize as a directory access-control issue, especially if 389 Directory Server protects identity, employee, customer, or service-account data. It requires authentication and specific permissions, so it is below unauthenticated remote compromise, but patching should not wait in multi-user directory administration environments. Mitigation focus: Check Red Hat and 389 Directory Server guidance for the official fixed package or patch.; Apply vendor-supported 389-ds-base or 389 Directory Server updates where affected.; Review who can move or rename directory entries across protected containers..

Prepared

Jun 27, 2026, 16:25 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.