An encryption key is derived from a secret with a single fast, unsalted hash ($HASH) and the digest is fed straight into a symmetric cipher to encrypt data. Ciphertext produced this way can be brute-forced fully offline at GPU speed (no per-ciphertext KDF work and no salt, so precomputed tables and cross-backup key reuse apply), which exposes every password-
Rule Explorer
Search the public rule index by CVE, GHSA, CWE, language, framework, author, or rule slug. Filter by language, framework, severity, confidence, license, and validation status.
- Public rules
- 6965
- Downloads
- 12.9M
- Verified
- 6965
- Authors
- 2
An authentication credential is derived from an external identity identifier (e.g. md5($data['id'])) and used to verify or provision a local account. The identifier is often public or guessable, so anyone can reproduce the credential and take over the account through the ordinary password login form. Provision federated accounts with a CSPRNG password, verif
Unrecognized flat KDF configuration keys (such as 'argon2_time_cost' or 'sha512_iterations') are assigned to hash_config. In crypt_core, these flat keys are ignored while defeating default template fallbacks, collapsing password key derivation to single unstretched SHA-256 (CWE-916).
A key derivation function accepts an iteration parameter but uses wc_HKDF instead of a password-based key derivation function like wc_PBKDF2. HKDF does not support computational work factor scaling, severely weakening offline password security.