Netscape LDAP SSHA Hash

What is Netscape LDAP SSHA?

The **Netscape LDAP SSHA** (Secure/Salted SHA) format is a cryptographic hash scheme designed as an extension to the original SHA-1 algorithm to mitigate plaintext password storage vulnerabilities in early LDAP (Lightweight Directory Access Protocol) implementations, particularly within Netscape Directory Server (now Mozilla Directory Server). Introduced in the late 1990s as part of RFC 2251bis and later standardized in IETF drafts, SSHA encodes passwords by first applying a salt (a random or deterministic value) to the input before hashing it with SHA-1, then encoding the resulting hash in a base64 format prefixed with `{SSHA}` to distinguish it from other formats. The structure adheres to the LDAP password syntax (e.g., `{SSHA}randomsaltbase64hash`), where the salt is concatenated with the password before hashing, and the output is designed for compatibility with legacy LDAP clients while providing basic protection against rainbow table attacks. Its primary use-case was securing password storage in directory services, though it was later superseded by stronger algorithms like SHA-256 or bcrypt due to its inherent cryptographic weaknesses.

The SSHA format is fundamentally vulnerable to cracking due to its reliance on SHA-1, which is now considered insecure for password hashing due to its 160-bit output space and susceptibility to collision attacks. The salt, while mitigating rainbow table attacks, is often weak (e.g., fixed-length or predictable in early implementations), and the lack of iterative hashing (unlike bcrypt or PBKDF2) allows modern hardware to compute hashes at high speeds—GPUs and FPGAs can brute-force SSHA hashes at rates exceeding millions per second. Additionally, the base64 encoding does not alter the underlying hash strength, and the absence of key stretching or computational overhead makes it trivial for attackers to perform offline dictionary or brute-force attacks. The algorithm’s design predates modern cryptographic best practices, rendering it unsuitable for contemporary security requirements.

Identifying Netscape LDAP SSHA 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 Netscape LDAP SSHA, security researchers analyze the hash against a strict regular expression (regex) signature (shown above) to find structural matches.

How to Crack Netscape LDAP SSHA

If you need to recover the plaintext password for a Netscape LDAP SSHA 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.