A flaw was found in 389 Directory Server. The LDIF parser reads past the end of a heap buffer when processing attribute types with trailing semicolons during database import, causing an out-of-bounds read detectable under memory instrumentation.
Validate LDIF files for malformed attribute types before importing. Reject any LDIF entry containing attribute types with trailing semicolons (e.g., userCertificate;binary;). Pre-import validation: grep -nE '^[a-zA-Z][a-zA-Z0-9-];[^:];:' input.ldif && echo "REJECT: trailing semicolon in attribute type". This does not protect against the replication changelog path (corrupted stored data), but that path requires pre-existing database corruption, not external input.