← Back to rule catalog
Rule R-WEAK-HASH
active

Weak signature hashes are already non-compliant

Immediate failure rule for SHA-1, SHA1, MD5, and MD4 signature usage.

Applies to
*
Cases
1
Evaluation order
40
Tags
hash, integrity, current-failure
Overlay-specific scope
pci-dss-4, nis2, dora, gdpr
Engine description
SHA-1 and MD5 class hashes are disallowed today for security-relevant use.

Match cases

Case 1 critical · replace-now
When
  • signatureHash is one of SHA-1, SHA1, MD5, MD4
Finding title template
{{asset.signatureHash}} signature in use — already non-compliant
Current crypto template
{{asset.signatureHash}} signature
Severity / status
critical · already-non-compliant
Effort / deadline
low · 2020-12-31
Recommended replacement
Replace with SHA-256 or SHA-3. For signed assertions, reissue the signing certificate if the hash was baked into the signature.
Rationale
SHA-1 and MD5 are disallowed under NIST SP 800-131A Rev 3 and excluded from BSI TR-02102. Practical collision attacks on SHA-1 are public; MD5 is broken for any security-relevant use.
Citations
  • NIST_SP_800_131A · Transitioning the Use of Cryptographic Algorithms and Key Lengths
  • BSI_TR_02102_1 · Cryptographic Mechanisms: Recommendations and Key Lengths

This rule is a direct current-state prohibition and should remain extremely conservative.