CWE-328 Use of Weak Hash: Why MD5 and SHA-1 Fail and What to Use
Weak hashes allow preimage, second preimage and collision attacks. CWE-328 explained, with a clear path to adaptive hashing for passwords.
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
Weak hashes allow preimage, second preimage and collision attacks. CWE-328 explained, with a clear path to adaptive hashing for passwords.
MD5, SHA-1, DES and homemade ciphers still turn up in production. CWE-327 explains why they are risky and how to migrate to algorithms that hold up.
An encryption scheme can be sound in theory and still too weak for the data it protects. CWE-326 explained, with the steps that keep key sizes and schemes current.
Skipping one required step in a cryptographic algorithm quietly weakens the whole thing. A short guide to CWE-325, its impact and how to avoid it.
Old keys give attackers more time to crack or steal them. CWE-324 covers products that keep using cryptographic keys or passwords after they should have been replaced.
A nonce is meant to be used once. CWE-323 covers code that reuses a nonce with the same key, opening the door to replay and tampering.
Encrypting a channel is not the same as knowing who is on the other end. CWE-322 covers key exchanges that skip identity checks and invite impersonation.
A key written into code cannot be changed and is shared by every copy of the product. See how CWE-321 appears in real devices and how to replace embedded keys.
On some Windows systems three dots act like two parent hops, and filters that expect only two dots miss it. How CWE-32 works and how to fix it.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.