LDAP(SSHA-512) Hash

Technical details, regex signatures, and cracking commands for the LDAP(SSHA-512) algorithm.

Regex Identification Signature:
^{SSHA512}[a-z0-9\/+]{96}$
Hashcat Command (Mode: 1711):
John the Ripper Command:
← Back to Hash Identifier

What is LDAP(SSHA-512)?

The **LDAP(SSHA-512)** hash format is a variant of the Secure SHA-1 (SSHA) algorithm specifically designed for storing password hashes in Lightweight Directory Access Protocol (LDAP) directories, such as OpenLDAP or Active Directory. Its structure combines a salted SHA-512 hash with a proprietary LDAP-specific prefix (`{SSHA}`) to distinguish it from other hash formats. The format begins with the `{SSHA}` tag, followed by a base64-encoded salt (typically a 32-byte random value), a colon (`:`), and the base64-encoded hash of the concatenated password and salt. This design was introduced to mitigate the known weaknesses of SHA-1 by leveraging the increased security of SHA-512 while maintaining compatibility with LDAP’s extensible authentication mechanisms. The primary use-case for SSHA-512 lies in securing password storage in directory services where backward compatibility with SSHA-1 was required, though it is now considered obsolete due to cryptographic advancements.

Despite its use of SHA-512, **LDAP(SSHA-512)** remains vulnerable to cracking due to several architectural flaws. First, its salt implementation is often poorly randomized or reused across multiple passwords, reducing resistance to rainbow table attacks. Second, the base64 encoding and fixed-length salt (when improperly generated) can leak entropy, allowing attackers to precompute or brute-force hashes more efficiently. Third, modern GPU/ASIC-based cracking tools (e.g., Hashcat or John the Ripper) can exploit the algorithm’s parallelizable nature, achieving high throughput even against SHA-512 variants. Additionally, the absence of key stretching mechanisms (e.g., PBKDF2, Argon2) means that SSHA-512 offers negligible resistance to brute-force attacks compared to modern password hashing schemes, rendering it unsuitable for contemporary security standards.

Identifying LDAP(SSHA-512) Hashes

Identifying a hash blindly is often difficult because multiple algorithms can output strings of the exact same length. For example, a standard 32-character hexadecimal string could be MD5, NTLM, MD4, or LM. To definitively identify LDAP(SSHA-512), security researchers analyze the hash against a strict regular expression (regex) signature (shown above) to find structural matches.

How to Crack LDAP(SSHA-512)

If you need to recover the plaintext password for a LDAP(SSHA-512) hash during a penetration test or forensics investigation, you must supply the correct module ID to your cracking software. Use the exact commands provided at the top of this page to target the hash successfully.