Password hashed with MD5 or SHA-1
A password is passed to a fast legacy hash. MD5 and SHA-1 are cheap to brute-force and are not suitable password-storage algorithms.
What the check contributes
Rule LANG003runs as part of CodeCordon's deterministic static-analysis pass. When it matches, the finding includes the source file, line number, severity, explanation, and a redacted snippet so the developer can inspect the evidence directly.
Recommended remediation
Use Argon2id, scrypt, bcrypt, or PBKDF2 with a unique salt and an appropriate work factor. Rehash existing credentials after the next successful login.
How to use this result
- 1. Open the reported line. Confirm the match is active application code rather than a fixture, example, or false positive.
- 2. Apply the remediation in context. Preserve the intended behavior while removing the dangerous pattern.
- 3. Scan again. Verify the known pattern no longer appears, then continue with tests and any runtime or human security review appropriate to the application.
Limits of this check
A match is a review signal, not proof of exploitability. No match means only that this specific known pattern was not found in the applicable files. It does not rule out equivalent code, business-logic flaws, runtime vulnerabilities, or novel attack paths.