Cryptographic failures: the category no request reveals
Cryptographic failures expose data through missing cryptography, cryptography too weak for the job, or leaked keys. The category is A04 in the OWASP Top 10:2025. A request filter reaches almost none of it: what goes wrong is how data is stored, transmitted and hashed, and none of that is visible in a request.
Quick facts
- Category
- A04:2025 Cryptographic Failures, down from second place in 2021
- Mapped weaknesses
- 32 CWEs, among them CWE-319 cleartext transmission, CWE-327 broken algorithms and CWE-916 weak password hashing
- Where it lives
- Transport settings, storage, key management and password hashing
- Related site
- Bridge SSL covers certificates and transport encryption in depth
- Does a WAF stop it?
- No. A request does not show how the data behind it is encrypted, hashed or keyed
Figures are from the A04:2025 page of the OWASP Top 10.
What the category covers
OWASP describes the category as the lack of cryptography, cryptography too weak for the job, leaked keys, and the errors around them.
- Data sent without encryption. Or without the extra application-level protection some data needs.
- Old or weak algorithms and protocols. Left on by default or kept in legacy code.
- Poor key management. Default, weak or reused keys, no rotation, keys committed to repositories.
- Encryption not enforced. For example, because the security headers that require HTTPS are missing.
- Certificates not validated. The server certificate or its chain of trust is accepted without checking.
- Weak password storage. Fast or unsalted hashes, or passwords used directly as keys.
- Weak randomness and deprecated hashes. Generators not built for cryptography; MD5 or SHA-1 where a modern hash is needed.
- Downgrade and side channels. An algorithm that can be negotiated down, or error messages that leak information, such as a padding oracle.
From sensitive data exposure to cryptographic failures
The category has changed name and place. In 2017 it was A3 Sensitive Data Exposure, which OWASP later called a broad symptom rather than a root cause. In 2021 it became A02 Cryptographic Failures, naming the cause: data exposed because cryptography was missing, weak or misused. In the 2025 edition it sits at A04.
The rename is useful when reading older reports and tools. A finding labelled sensitive data exposure in a scanner built for 2017 usually belongs to this category today, and the advice has stayed the same: protect data in transit and at rest, with current algorithms and well-kept keys.
Why a request shows none of it
A request filter reads requests on their way to the application. Most of this category concerns things that happen elsewhere: data at rest in a database, a hash computed when a password is saved, a key in a repository, a certificate check made when the application calls another service.
OWASP's two scenarios make the point. In the first, a site that does not enforce TLS lets an attacker on the same network downgrade a visitor's connection and steal the session cookie; the attack happens between the visitor and the site, before any filter sees a request. In the second, a password table stored with fast, unsalted hashes is exposed through a separate flaw and cracked offline.
Neither attack sends the site a request that looks like an attack.
The closest category that does leave a trace is authentication failures, which shows as volume; in the integrity category, insecure deserialization is the related case of trusting data that was never checked.
What fixes it
OWASP's list is long; the core of it fits in five lines.
- Know which data is sensitive. Classify it, keep less of it, and discard it early.
- Encrypt it in transit and at rest. TLS 1.2 or later with forward secrecy, HTTPS enforced with HSTS, and sensitive data encrypted where it is stored.
- Use current, well-established implementations. Authenticated encryption, proper modes and initialisation vectors, and no MD5, SHA-1 or other deprecated functions.
- Hash passwords slowly. With a salted, adaptive function that has a work factor, such as Argon2, scrypt or PBKDF2.
- Manage keys. Generated with secure randomness, rotated, kept out of repositories, and the most sensitive ones held in a hardware or cloud security module.
OWASP also asks that responses carrying sensitive data are not cached, including by CDNs, and that high-risk systems are prepared for post-quantum cryptography by the end of 2030.
Storing passwords correctly
Passwords are not encrypted, they are hashed, with an algorithm designed to be slow and to use a unique salt for each password. The OWASP Password Storage Cheat Sheet recommends Argon2id first, then scrypt, bcrypt, or PBKDF2 where compliance requires it, with settings that make each guess expensive.
Fast hashes such as MD5 or SHA-256 on their own are the failure: they were built to be quick, so a stolen database can be tested against billions of guesses per second. Moving to a slow hash does not need every user to reset; each stored hash can be upgraded the next time its owner signs in.
Where the edge does touch this
Transport encryption is the one part of the category that sits at the edge of a site. Certificates, protocol versions and HTTPS enforcement are decided where the connection terminates, which is why they belong to the certificate layer of a CDN. That is a different component from request filtering, and enabling one does not configure the other. From outside, a site's HTTPS-related response headers can be inspected with the header checks listed there.
Questions
Can a WAF prevent cryptographic failures?
No. Cryptographic failures concern how data is transmitted, stored, hashed and keyed. None of that appears in a request, so a request filter has nothing to inspect.
Is missing HTTPS a cryptographic failure?
Yes. OWASP lists data transmitted without encryption, and encryption that is not enforced, for example through missing HSTS, under A04:2025.
Which password hashing does OWASP recommend?
A salted, slow, adaptive function with a work factor, such as Argon2, yescrypt, scrypt or PBKDF2-HMAC-SHA-512, per the A04:2025 guidance.